Loading...
Loading...
Found 818 Skills
Removes AI writing artifacts from documentation and code. Use when editing LLM-generated prose, reviewing READMEs, polishing docs before publishing, or cleaning up AI-generated code. Use for emdash cleanup, formulaic phrase removal, tone calibration, over-commented code, verbose naming, and AI code smell detection.
Review PR comments, discuss improvements, and reply with resolution status
Adaptive test-driven development cycle. Detects harness capabilities and routes to guided (manual phase control) or automated (orchestrated) mode. Invoke with /tdd for automated or /tdd red|domain|green|commit for guided.
Three-stage code review protocol: spec compliance, code quality, and domain integrity. Activate when reviewing code, preparing PRs, assessing implementation quality, or checking that code matches requirements. Triggers on: "review this code", "prepare PR", "check implementation", "code quality", "does this match the spec".
Domain modeling principles: parse-don't-validate, make invalid states unrepresentable, primitive obsession detection, semantic types, and domain veto authority. Activate when designing types, reviewing code for domain integrity, or when domain review is needed in a TDD cycle.
Systematic 4-phase debugging: understand the failure, form hypotheses, test one change at a time, fix with confidence. Activate when tests fail unexpectedly, errors occur, behavior is wrong, or something that worked before is now broken. Triggers on: "debug", "why is this failing", "test failure", "unexpected error", "bug", "broken".
Systematically analyze codebase structure, complexity, dependencies, and architectural patterns to understand project organization
Use this when the user asks to refactor, clean up, optimize, or improve code quality.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Perform a refactor pass focused on simplicity after recent changes. Use when the user asks for a refactor/cleanup pass, simplification, or dead-code removal and expects build/tests to verify behavior.
Use this skill when posting the final summary comment after all inline comments are posted. Apply as the LAST step of code review after all findings are classified and inline comments are complete. Detects context (GitHub sticky comment, new comment, or local file) and routes output accordingly.
Use when writing, reviewing, or refactoring Java code to enforce baseline conventions for imports, nullability, immutability, exceptions, resource handling, naming, and concurrency.