with one click
roach-pi
roach-pi contains 7 collected skills from tmdgusya, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Use when a user's request is vague, ambiguous, or underspecified. Runs recon-first clarification — codebase exploration before questions, then one bundled question round with defensible defaults — and outputs a Goal Contract for the durable /goal runtime. Triggers on "I want to...", "I need...", "let's build...", "can you help me...", "we should...", or any request where the full scope isn't immediately clear.
Primary execution workflow for durable /goal runtime. Use when a Goal Contract is active or when the user asks to execute, continue, verify, or complete a goal.
Review changed code for reuse opportunities, quality issues, and inefficiencies using three parallel review agents, then fix any issues found. Triggers when the user says "agentic-simplify", "clean up the code", "review the changes", or after goal implementation when code quality verification is needed.
Use when encountering any bug, test failure, or unexpected behavior. Enforces a strict reproduce-first, root-cause-first, failing-test-first debugging workflow before fixing.
Interactive idea development through guided Q&A dialogue. This skill helps users clarify and develop their ideas by asking targeted questions, expanding on possibilities, and producing a structured markdown document capturing the essence of their thinking. Triggers: "brainstorm", "idea", "organize ideas", "I want to organize my thoughts", "whatever comes to mind"
Behavioral guardrails to prevent common LLM coding mistakes — enforces surgical changes, assumption verification, and scope discipline before and during implementation. Use when implementing features, modifying code, or when you notice yourself about to make changes without reading the existing code first.
Rob Pike's 5 Rules of Programming — a decision framework that prevents premature optimization and enforces measurement-driven development. Use when the user says "optimize", "slow", "performance", "bottleneck", "speed up", "make faster", "too slow", or any request to improve code speed/efficiency. Also use when you notice yourself about to suggest a performance optimization without measurement data. This is a thinking discipline, not a tooling workflow.