plugins/dp-cto/skills/adhoc-sweep/SKILL.md
Use when you want to clean up drift, dead code, stale comments, or naming violations — 'sweep this', 'clean up', 'find dead code', 'check for drift'. Standalone entropy scan without an active epic.
npx skillsauth add raisedadead/dotplugins adhoc-sweepInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Standalone entropy scan. Dispatches the sweeper agent outside the epic lifecycle. Works in any project without tracker state or an active dp-cto epic.
Determine what to sweep:
Present a category menu via AskUserQuestion:
If the user provided a category in their args (e.g., /dp-cto:adhoc-sweep dead-code), skip the menu.
Run the optional stringer JSONL collectors before dispatching the sweeper. The collectors are fixed: deadcode,docstale,githygiene. Output is piped directly into dp-engine create-graph --stdin (deterministic SHA-256 IDs make re-imports idempotent).
Bash:
if command -v stringer >/dev/null 2>&1; then
stringer scan --collectors deadcode,docstale,githygiene -q | dp-engine create-graph --stdin
else
printf 'stringer not installed — skipping JSONL collectors. Install: brew install davetashner/tap/stringer (or per project)\n'
fi
Stringer is OPTIONAL — when absent, skip silently and continue. Do not block on install.
Spawn sweeper agent via Agent tool with subagent_type: "dp-cto:sweeper".
Include in the prompt:
Parse the sweeper receipt. Present findings grouped by severity, then summarize:
## Sweep Results
- **Fixed:** {N} items (CRITICAL + WARNING)
- **Reported:** {N} items (SUGGESTION)
- **Files scanned:** {N}
For each SUGGESTION, ask: "File this to the cabinet for future work? (yes / skip)"
If yes, use /dp-cab:file to capture the finding.
development
Use when the user shares a URL, names a resource from SOURCES.md, shares operational feedback, says 'adopt', 'learn from', 'what can we steal from', 'compare with', 'self-develop', or 'how do we get better'.
tools
Use when you need to set up or rebuild the dp-lsp Docker image after installing the plugin — 'set up LSP', 'build the image', 'install language servers'.
development
Use when you want to write tests first, enforce test-driven development, or add test coverage — 'write tests for this', 'TDD this feature', 'add test coverage'. Strict RED-GREEN-REFACTOR discipline.
testing
Use when starting major work that needs formal design review — cross-team changes, architectural decisions, or complex features where requirements need discovery before implementation.