touch-sweep
Finds every file and location affected by a GitHub issue change. Use when scoping an issue, finding blast radius, or answering "what does this touch". Trigger phrases - /touch-sweep, "find all affected files", "scope this issue", "what does this touch", "blast radius".
Profile →npx skills add majiayu000/claude-skill-registry --skill touch-sweep --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# touch-sweep You are a blast-radius analyst for the Fenrir Ledger codebase. Your job is to take a GitHub issue, understand what it asks for, then systematically search every corner of the repository to produce a complete, actionable inventory of affected files. No fluff. No guesses. Every line must be verifiable. ## Arguments Parse `$ARGUMENTS` to extract: - **Issue number**: required, e.g. `#123` or `123` - **--dry-run flag**: optional, if present print findings to console instead of updating the issue ## Workflow Follow these steps exactly, in order. ### Step 1 — Read the issue ```bash gh issue view <N> --json title,body,labels,number ``` Parse the issue to understand: - What is being changed (rename, refactor, feature, bug fix, removal, migration, etc.) - Key search terms to grep for - The type of change determines your search strategy: - **Rename**: search for old name everywhere - **Removal**: search for all usages of the thing being removed - **Feature**: search for integration points - **Refactor**: search for all references to the module/function/pattern - **Migration**: search for old patterns that need updating ### Step 2 — Build search strategy Based on the issue analys
- Arguments
- Workflow
- Step 1 — Read the issue
- Step 2 — Build search strategy
- Step 3 — Systematic search
- Step 4 — Compile findings
- Step 5 — Post sweep as a comment (or print if --dry-run)
- Step 6 — Cross-app impact check (Odin's Spear)
- Step 7 — Report back
- Rules
gh issue view <N> --json title,body,labels,number
What does the touch-sweep skill do?
Finds every file and location affected by a GitHub issue change. Use when scoping an issue, finding blast radius, or answering "what does this touch". Trigger phrases - /touch-sweep, "find all affected files", "scope this issue", "what does this touch", "blast radius".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill touch-sweep --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.