From pr-review
Scans codebases for dead code, complexity, duplication, and pattern inconsistencies, then selectively fixes issues to produce cleaner code.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pr-review:curating-codeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Analyze a codebase (or targeted path) for vibe-coding cruft using four parallel specialist agents. Consolidates findings into a prioritized report, lets you select which issues to address, and implements the fixes.
Analyze a codebase (or targeted path) for vibe-coding cruft using four parallel specialist agents. Consolidates findings into a prioritized report, lets you select which issues to address, and implements the fixes.
/curating-code # Sweep the entire codebase
/curating-code src/ # Curate a specific directory
/curating-code lib/auth.ts # Curate a specific file
Scope & Detect → [Dead Code Hunter | Complexity Reducer | Duplication Consolidator | Consistency Enforcer] → Consolidate → Report → Select → Implement
| Agent | Finding Prefix | Focus |
|---|---|---|
| Dead Code Hunter | DC- | Unused functions, unreachable branches, orphaned files, stale imports |
| Complexity Reducer | CX- | Over-abstraction, deep nesting, convoluted control flow, god functions |
| Duplication Consolidator | DU- | Near-identical blocks, copy-paste patterns, consolidation opportunities |
| Consistency Enforcer | CN- | Divergent patterns, mixed conventions, conflicting approaches |
Read and follow the orchestrator instructions exactly:
Orchestrator file: agents/curation-orchestrator.md (relative to this plugin's root)
The orchestrator will:
IMPORTANT: Read the orchestrator file using the path ${CLAUDE_PLUGIN_ROOT}/agents/curation-orchestrator.md and follow it exactly.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.
npx claudepluginhub dbinky/dbinky-skill-set --plugin spec-to-design