Repository navigation
docs: clarify where to edit skills - #40
Merged
Merged
Conversation
Direct agents working from generated skills to the authoring package so flattening does not overwrite their edits.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Agents starting inside
skills/need a clear route to the editable source. Without it, direct edits to generated files are lost on the next flatten.Clarify in
AGENTS.mdthat agents must edit the matchingauthoring/package and runjust flatten-skills, regardless of their current directory.Made with GPT-6-Sol in T3 Code (Codex harness).