Loading...
Loading...
Found 53 Skills
Find dead code and cleanup candidates such as unused exports, unreachable branches, orphaned files, stale feature flags, dead registrations, and compatibility layers with no live callers. Use when auditing refactors, bundle-size cleanup, architecture simplification, pre-release cleanup, reviewing requests to find unused code or decide what can be deleted, or when deciding whether code can be safely removed or auto-fixed.
Use when content must be translated between audiences with different expertise, context, or goals while preserving accuracy but adapting presentation. Invoke when technical content needs business framing (engineering decisions → executive summary), strategic vision needs tactical translation (board presentation → team OKRs), expert knowledge needs simplification (academic paper → blog post, medical diagnosis → patient explanation), formal content needs casual tone (annual report → social media post), long-form needs summarization (50-page doc → 1-page brief), internal content needs external framing (roadmap → public updates, bug tracking → known issues), cross-cultural adaptation (US idioms → international clarity, Gen Z → Boomer messaging), medium shifts (written report → presentation script, detailed spec → action checklist), or when user mentions "explain to", "reframe for", "translate this for [audience]", "make this more [accessible/formal/technical]", "adapt for [executives/engineers/customers]", "simplify without losing accuracy", or "same content, different audience". Apply to technical communication (code → business value), organizational translation (strategy → execution), education (expert → novice), customer communication (internal → external), cross-cultural messaging, and anywhere same core message needs different presentation for different stakeholders while maintaining correctness.
Evaluate finished work for defects, risk, and simplification before it ships
This skill should be used when the user asks to "polish code", "simplify and review", "clean up and review code", "full code polish", "simplify then review", "refactor and review", "simplify and fix", "clean up and fix", or wants a combined simplification and review workflow on recently changed code.
Review a diff for clarity and safe simplifications, then optionally apply low-risk fixes.
Converts Opus-quality skills into deterministic Haiku-executable workflows via trace-driven distillation and cross-model validation. Triggers on: "distill this skill", "make this skill work on Haiku", "cross-model optimization", "optimize skill for cost". NOT for code simplification, use code-refiner.
Hunts complexity in the current diff and APPLIES the simplifications directly to the working tree, then verifies the build. Five angles: reuse (duplicate logic, hand-rolled stdlib, platform features), quality (React/TypeScript hygiene, over-memoisation, exhaustive-deps, `any`, `CLAUDE.md`/`AGENTS.md` violations), efficiency (unnecessary work, missed concurrency, hot-path bloat), altitude (bandaid fixes special-cased onto shared code), and test discipline (repro test per bug fix, useless tests deleted, new tests only when they prevent a named failure). Hand it a `pr-reviewer` report and it applies those confirmed findings too. Use when the user says "tidy this up", "simplify", "clean up this diff", "polish my changes", "make this simpler", "apply the review findings", or "any reuse opportunities?". For a read-only report instead, use `pr-reviewer`; for the PR's title, description, or commits, use `pr-creator`.
Use when running a scheduled mechanical maintenance pass over a repo — dead code removal, useless-test pruning, layering-violation fixes, duplicate unification, logic bugfixing, logic simplification, or excess-abstraction flattening. Invoked as `/cadence:maintenance-routine <archetype>`, typically from a scheduler (cron, a CI schedule, or an agent workbench's time trigger). One archetype per invocation; opens PRs and never merges. NOT for reviewing a PR (use pr-review), NOT for ad-hoc refactoring the user asked for directly.
Ruby refactoring guidelines from community best practices. This skill should be used when refactoring, reviewing, or restructuring Ruby code to improve design, readability, and maintainability. Triggers on tasks involving code smells, method extraction, conditional simplification, coupling reduction, design patterns, or Ruby idiom adoption.
Code simplification for clarity and maintainability. Use PROACTIVELY after code is written or modified to refine recently changed files.
Use this agent when you need a final review pass to ensure code changes are as simple and minimal as possible. This agent should be invoked after implementation is complete but before finalizing changes, to identify opportunities for simplification, remove unnecessary complexity, and ensure adherence to YAGNI principles. Examples: <example>Context: The user has just implemented a new feature and wants to ensure it's as simple as possible. user: "I've finished implementing the user authentication system" assistant: "Great! Let me review the implementation for simplicity and minimalism using the code-simplicity-reviewer agent" <commentary>Since implementation is complete, use the code-simplicity-reviewer agent to identify simplification opportunities.</commentary></example> <example>Context: The user has written complex business logic and wants to simplify it. user: "I think this order processing logic might be overly complex" assistant: "I'll use the code-simplicity-reviewer agent to analyze the complexity...
Review changes for test gaps, simplification, naming consistency, reuse opportunities, and TODO quality