docs: recommend agr upgrade for iterating on in-repo skills#529
Merged
Conversation
The in-repo skills guidance steered users to `agr add ./path --overwrite` to re-sync a locally-edited skill. `agr upgrade <name>` is purpose-built for this: it reinstalls a fresh on-disk copy of the local skill into every configured tool and refreshes agr.lock, in a shorter name-based command. Update both the SKILL.md Iterate note and references/in-repo-skills.md to lead with `agr upgrade`, keeping `add --overwrite` as the path-based escape hatch for re-adds and clarifying that `agr sync` won't pick up edits. Closes #528 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
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.
What
Updates the
agr-cliskill's in-repo iteration guidance to recommendagr upgrade <name>instead ofagr add ./path --overwritewhen re-syncing a locally-edited skill.Why
agr upgrade --helpdescribes it as: "Re-install dependencies (latest upstream commit for remotes, fresh copy for local) and refresh agr.lock." For a vendored/in-repo skill that's exactly the iterate loop — and it's shorter, name-based, and refreshesagr.lock, whereasagr add ./path --overwriteis path-based and doesn't foreground lockfile hygiene.Changes
skills/agr-cli/SKILL.md— Iterate note now leads withagr upgrade my-skill;add --overwritekept as the path-based escape hatch for re-adds.skills/agr-cli/references/in-repo-skills.md— same, plus clarifies thatagr syncwon't pick up edits to an already-installed skill.Docs-only;
mkdocs build --strictpasses.Closes #528
🤖 Generated with Claude Code