code first responder
- Repo stars 0
- Author repo nano-core
- Domain
- AI
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @0-CYBERDYNE-SYSTEMS-0 · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Code First Responder
## When to use this skill
- Use when the user request matches this skill's domain and capabilities.
- Use when this workflow or toolchain is explicitly requested.
## When not to use this skill
- Do not use when another skill is a better direct match for the task.
- Do not use when the request is outside this skill's scope.
## When to load this skill
- Incoming task references failing tests, stack traces, or recent merges.
- User explicitly wants a "quick triage", "first look", or "rough fix plan".
- Another skill (e.g., Rapid Research) flagged new code issues that need confirmation.
## Guardrails
1. Never edit files before the failure is reproduced locally.
2. Capture the exact command + exit code inside the debug report template.
3. Prefer minimal diffs; defer major refactors to a follow-up task.
4. If the failure cannot be reproduced quickly, escalate with the captured evidence and leave the repo untouched.
## Five-step micro-playbook
1. **Snapshot context**
- Record branch, latest commit hash, and dirty files.
- Paste the failure summary into `templates/debug_report_template.md`.
2. **Reproduce fast**
- Run the narrowest test or script possible.
- Store the exact CLI command and snippet of output.
3. **Isolate scope**
- Identify the component or file set causing the issue.
- Outline suspected root causes without editing yet.
4. **Propose fix plan**
- List concrete actions (edit file X, update test Y, run command Z).
- Mark each action as `must`, `optional`, or `blocked`.
5. **Optional patch**
- If the fix is obvious (<30 lines), apply it and run validation.
- Update the debug report with the diff summary and test status.
## Output checklist
Refer to `templates/fix_checklist.md` and ensure every box is addressed:
- Failure reproduced?
- Minimal scope understood?
- Plan or patch documented?
- Validation command + result captured?
- Handover note written?
## Response snippet to send back to the user
```
## Debug Status
- Branch/commit: ...
- Failure reproduced: yes/no (command)
- Root-cause hypothesis: ...
- Next actions: ...
## Attachments
- debug_report_template.md (updated)
```
## Companion tools
- `run_command` for fast tests.
- `read_file` + `search_code` for targeted inspection.
- `write_file` for updating the templates and final report.
Sections and files
Listed in source order.
sections -> When to use this skill → When not to use this skill → When to load this skill → Guardrails → Five-step micro-playbook → Output checklist
terms -> Snapshot context · Reproduce fast · Isolate scope · Propose fix plan · Optional patch
files/cmd -> templates/debug_report_template.md · must · optional · blocked · templates/fix_checklist.md · run_command · read_file · search_code
body sha256 -> 370b510a1e68
When to use this skill
Use when the user request matches this skill's domain and capabilities. Use when this workflow or toolchain is explicitly requested.
When not to use this skill
Do not use when another skill is a better direct match for the task. Do not use when the request is outside this skill's scope.
When to load this skill
Incoming task references failing tests, stack traces, or recent merges. User explicitly wants a "quick triage", "first look", or "rough fix plan". Another skill (e.g., Rapid Research) flagged new code issues that need confirmation.
Guardrails
Never edit files before the failure is reproduced locally. Capture the exact command + exit code inside the debug report template. Prefer minimal diffs; defer major refactors to a follow-up task. If the failure cannot be reproduced quickly, escalate with the captured evidence and leave the repo untouched.
Five-step micro-playbook
Snapshot context Record branch, latest commit hash, and dirty files. Paste the failure summary into
templates/debug_report_template.md. Reproduce fast Run the narrowest test or script possible.