16 skills published by roman01la across 1 repository. Together they weigh 57 238 tokens — that is what loading all of them at once would cost you in context. 1 of them have been repackaged into other people's repositories.
16 skills 57 238 tokens total 1 copies elsewhere
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.
Interview user in-depth to create a detailed spec
Use when executing implementation plans with independent tasks in the current session
Use when starting any conversation - routes work through the correct worker agents before any task action, requiring explicit worker selection and visible compliance
Use when you have a spec or requirements for a multi-step task, before touching code
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
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
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Use when implementing any feature or bugfix, before writing implementation code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes