Identify repository files touched by a GitHub issue for blast radius assessment.
npx skills add https://github.com/declanshanaghy/fenrir-ledger --skill touch-sweep
Please help me install this Agent Skill. Skill: touch-sweep Source: https://github.com/declanshanaghy/fenrir-ledger/tree/main/.claude/skills/touch-sweep Command: npx skills add https://github.com/declanshanaghy/fenrir-ledger --skill touch-sweep
Finds every file and location affected by a GitHub issue change, enabling precise scoping, blast-radius assessment, and impact analysis.
Provide the issue number and optional --dry-run, then run touch-sweep to generate the blast-radius report.
High-intent search queries and answers about installing and using this skill.
Blast-radius analysis for a GitHub issue involves reading the issue, building a deterministic search strategy, and reporting matches with absolute file paths. It systematically identifies touched files across code, tests, documentation, and CI workflows to support scoping.
You can assess impact by running a sweep that builds a deterministic search strategy based on the issue. It produces a complete inventory of affected repository locations with absolute file paths and counts across code, configuration, and infrastructure.
Yes, you can execute a dry run by passing the optional --dry-run flag with your issue number. This allows you to preview the deterministic search strategy before executing the full blast-radius analysis.
Using a deterministic search strategy that reads the GitHub issue and reports matches with absolute file paths is the best way to find affected files. It produces a complete blast-radius inventory across code, tests, and infrastructure.
Blast-radius analysis works across infrastructure and CI workflows in addition to source code. It systematically identifies all touched files across code, tests, documentation, configuration, CI workflows, and infrastructure to define the full blast radius.
Deterministic search steps ensure consistent, reproducible results when scoping a GitHub issue. The analysis reads the issue, constructs a deterministic search strategy, and reports matches with absolute file paths and counts for reliable impact assessment.
lutzcc1Analyze GitHub issues to generate structured implementation plans with tasks and milestones.
bettercallzaalMap code change dependencies and downstream effects to assess blast radius.
Objective-ArtsRun read-only Qodana static analysis to detect code issues.
NOMARJAudit project dependencies for supply-chain threats and classify findings by severity.
