Loading...
Loading...
Found 14 Skills
Decision guide for delegating to caveman-style subagents. Tells the main thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the work inline or using vanilla `Explore`. Subagent output is caveman-compressed so the tool-result injected back into main context is ~60% smaller — main context lasts longer across long sessions. Trigger: "delegate to subagent", "use cavecrew", "spawn investigator/builder/reviewer", "save context", "compressed agent output".
Triage a bug or issue by exploring the codebase to find root cause, then create a GitHub issue with a TDD-based fix plan. Use when user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem.
(NS) Root-cause diagnosis from errors, logs, stack traces, failing tests, or CI — entry priority 4 when the user wants diagnosis WITHOUT implement ("why does X break?"). Use proactively on unclear test/CI failures if they have not asked to fix yet. Do NOT use for implement/fix (ns-coder), version scope (ns-spec-driven), GitLab ISSUE_URL execution, or pre-merge review (ns-reviewer).
Deep codebase exploration. Triggers: research, explore, investigate, understand, deep dive, current state.
Investigates and analyzes an idea or codebase area before committing to changes. Pure research, no writes. Trigger: /sdd-explore <topic>, explore, investigate codebase, research feature, analyze before changing.
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.
Evidence-based investigative code review using deductive reasoning to determine what actually happened versus what was claimed. Use when verifying implementation claims, investigating bugs, validating fixes, or conducting root cause analysis. Elementary approach to finding truth through systematic observation.
Use when the user asks to investigate, audit, trace, or explain how a feature, issue, module, workflow, API, config, or behavior works across one or more codebase projects.
Research the codebase to answer questions. Search for relevant files, gather context, and provide clear answers.
Find out why something in a running web app does not work, when the console is empty and the code looks correct. Reads the click, the request, the store and the console together and returns the file:line to open. Use when a button does nothing, a form will not submit, data will not load, a page renders blank or stale, a modal will not close, or the user says "it's broken" and the code review says it is fine.
Decision guide for delegating to hui-style subagents. Tells the main thread WHEN to spawn `huicrew-investigator` (locate code), `huicrew-builder` (1-2 file edit), or `huicrew-reviewer` (diff review) instead of doing the work inline or using vanilla `Explore`. Subagent output is hui-compressed so the tool-result injected back into main context is ~60% smaller — main context lasts longer across long sessions. Trigger: "delegate to subagent", "use huicrew", "spawn investigator/builder/reviewer", "save context", "compressed agent output".
Investigate and diagnose issues without necessarily fixing them