Loading...
Loading...
Found 84 Skills
Your pathfinder for navigating unknown codebases. Investigates with precision, implements surgically, and never assumes — if it doesn't know, it says so. Maintains a .notebook/ knowledge base that grows across sessions, turning every discovery into lasting intelligence. Summons available skills, MCPs, and docs when the mission demands. Use when fixing bugs, implementing features, refactoring, investigating flows, or any development task in unfamiliar territory. Triggers on "fix this", "implement this", "how does this work", "investigate this flow", "help me with this code". Do NOT use for greenfield scaffolding, CI/CD, or infrastructure provisioning.
Phase 2 of the issue process — Read the issue report + read the code, identify the true root cause and assess repair risks, and finally provide users with 2-3 repair solution options for them to decide. **Do NOT start modifying code in this phase** — present the conclusions to the user after analysis, and only proceed to Phase 3 after the user confirms the solution. Prerequisite: cs-issue-report has been completed. Trigger scenarios: The user says "Analyze this bug", "Find the root cause", "Locate the issue", and {slug}-report.md already exists in the issue directory.
Use when saving or retrieving important patterns, decisions, and learnings across sessions. Triggers on keywords like "remember", "save pattern", "recall", "memory", "persist", "knowledge base", "learnings".
Apply when writing, modifying, or reviewing code. Behavioral guidelines to reduce common LLM coding mistakes. Triggers on implementation tasks, code changes, refactoring, bug fixes, or feature development.
Iterative debugging workflow with confidence scoring and strategic log injection. Five phases: investigate, inject logs, propose fix, verify, cleanup. Use when: debugging unexpected behavior, silent errors, intermittent failures, or issues requiring runtime data. Triggers on "debug", "fix bug", "investigate", "trace issue", "add debug logs", "cleanup debug logs".
Use when implementing any feature or bugfix, before writing implementation code
This skill should be used when fixing bugs, implementing features, debugging issues, or making code changes. Ensures understanding of code flow before implementation by: (1) Tracing execution path with specific file:line references, (2) Creating lightweight text diagrams showing class.method() flows, (3) Verifying understanding with user. Prevents wasted effort from assumptions or guessing. Triggers when users request: bug fixes, feature implementations, refactoring, TDD cycles, debugging, code analysis.
Used when implementing any feature or bug fix before writing production code
Use when a program crashes, a test fails, or code produces wrong results and reading the source isn't enough to see why. Lets you pause execution at any line and inspect the actual runtime state, variable values, types, call stacks, to find what went wrong.
Investigate, fix, postmortem, prevent. Full incident lifecycle from bug report to systemic prevention. Use when: production down, critical bug, incident response, post-incident review. Composes: /investigate, /fix, /postmortem, /codify-learning.
Use when encountering bugs, test failures, or error logs that need root cause analysis and fix generation
Fix a bug with systematic debugging, TDD, and PR workflow