docs: teach the rep skill the new flags and gitignoring .rep/ - #13
Merged
Conversation
The skill predates --map-file, --last, rep show, --from-git-renames, and rep.toml, so agents following it still built giant --map argument lists and read .rep/plans/*.json by hand. It now covers: bulk mappings via --map-file, deriving mappings from staged git mv renames (with the derive -> commit -> re-plan recipe and the underivable caveat), rep show as the supported plan inspection, apply/residual --last, and repo-wide excludes in rep.toml. It also now requires ensuring .rep/ is gitignored before the first plan: the artifacts are machine-managed state that must not be committed, and untracked they pollute git status. Practice what we preach — this repo's own .gitignore gains .rep/ too. Co-Authored-By: Claude Fable 5 <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
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.
Why
The
/repskill predates #8–#12, so agents following it still assemble giant--mapargument lists and read.rep/plans/*.jsonby hand. Separately,.rep/was showing up as untracked noise ingit status(it blockedgw syncduring the stack merges) because nothing ensured it was gitignored.What
--map-file(file or stdin) instead of long--maplists.--from-git-renamesfor the git-mv-first workflow, including the derive → commit → re-plan recipe and thederived.underivablecaveat.rep show(--files --skipped --preview) as the supported plan inspection — explicitly deprecating direct.rep/plans/<id>/*.jsonreads.apply --last/residual --lastas the default id-free path.rep.toml(+--no-config,excluded_by_config)..rep/is gitignored, with a one-liner:git check-ignore -q .rep || echo '.rep/' >> .gitignore..gitignoregains.rep/.mise run rep:verifygreen (docs-only for code purposes).🤖 Generated with Claude Code