Scan a focused codebase area and generate targeted documents in .planning/codebase/.
npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-scan-trucol270
Please help me install this Agent Skill. Skill: gsd-scan Source: https://github.com/TruCol270/salty-pickle/tree/main/.claude-skills/gsd-scan Command: npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-scan-trucol270
Quickly assess a codebase by focusing on a single area to surface actionable insights without running full-scale scans.
Run a focused codebase scan for a single area and emit targeted documents in .planning/codebase/.
High-intent search queries and answers about installing and using this skill.
To scan a focused area of your codebase, use the optional --focus parameter to limit analysis to a specific module and quickly surface risk signals without running a full-scale scan.
The best way to generate targeted documents for sprint planning is to run a lightweight scan on a module to identify hotspots, which automatically emits concise reports under the .planning/codebase/ directory.
Yes, you can run a codebase scan without external dependencies because this lightweight workflow operates independently to perform mapper-style scans and generate targeted documents in your project.
Yes, focused codebase scanning is explicitly applicable to medium-sized codebases that require rapid risk assessment and module-level insights using a lightweight workflow.
You should use a focused scan instead of a full codebase scan when you need to speed up feedback during sprint planning by quickly surfacing actionable insights for a single area without full-scale analysis.
stacklokReview RFCs for completeness, architectural alignment, and security.
warpcodeBreak down project concepts into epics and plan sprints by capacity.
snqbIdentify high-churn files in Git repositories using churn and complexity signals.
rkz91Scan focused codebase areas and generate planning documents in .planning/codebase/.
