Menú
Systematically debug issues using graph-powered code navigation
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Detect code-improvement catalog violations in recent PR files and guide small stacked commits/branches.
Mentor for Exercism exercises: hints while solving, code review and improvement suggestions when asked. Use when solving Exercism challenges, mentions exercism-mode or exercism-mentor, or asks for help on https://exercism.org/tracks/typescript or any Exercism track.
Review pull requests using the tools available in the current environment. Works with GitHub or Bitbucket, MCP tools or CLI tools, and local git diffs. Produces actionable review findings, optional human-inspection callouts, and optional PR comments including both an overall review comment and inline file/line comments when posting is requested.
Create a concise, visual technical HTML walkthrough for a pull request by combining PR code changes with Specs/OpenSpec/design artifacts. Use when the user asks to explain what changed in a PR, generate a PR walkthrough, produce architecture/design documentation for a PR, summarize a spec-backed implementation, or create visual delta docs with Mermaid diagrams. Prefer this skill over a normal PR review when the user wants understanding, onboarding, or design explanation rather than defect findings.
Launch parallel agent sessions in the current cmux workspace from a list of input items. Use when the user wants to script cmux, keep the current pane on the left, create a right-side vertical stack with one pane per item, run Codex, Claude Code, Cursor Agent, or Rovo Dev over a list, trigger a custom skill or prompt for each item, or monitor parallel agent runs in cmux. If the user has not clearly specified an agent, ask which agent to use before spawning panes.
Break a feature definition markdown file into independently-grabbable OpenSpec changes organized by feature capability, then scaffold each one via OpenSpec Propose. Use when the user wants to convert a feature file into OpenSpec changes, create spec-driven change proposals from a feature definition, or split a medium/small feature into sequenced OpenSpec work items. Assume the feature file is passed as input; if it is not provided, ask the user for the feature file before proceeding.
| name | incident-debugging-code-knowledge |
| description | Systematically debug issues using graph-powered code navigation |
Use the knowledge graph to systematically trace and debug issues.
semantic_search_nodes to find code related to the issue.query_graph with callers_of and callees_of to trace call chains.get_flow to see full execution paths through suspected areas.detect_changes to check if recent changes caused the issue.get_impact_radius on suspected files to see what else is affected.get_minimal_context(task="<your task>") before any other graph tool.detail_level="minimal" on all calls. Only escalate to "standard" when minimal is insufficient.