Code First Responder

AI Community

Repo stars 0
Author repo FarmFriend-Terminal-React

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: 'Guides the agent through a short, repeatable debug loop: capture the Refer to templates/fix_checklist.md and ensure every box i…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “When to load this skill”, “Guardrails”, “Five-step micro-playbook”, “Output checklist”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name Code First Responder directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “When to load this skill / Guardrails / Five-step micro-playbook” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Code First Responder

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.
- Store the exact CLI command and snippet of output.
Isolate scope
- Identify the component or file set causing the issue.
- Outline suspected root causes without editing yet.
Propose fix plan
- List concrete actions (edit file X, update test Y, run command Z).
- Mark each action as must, optional, or blocked.
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.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: 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
Author / version / license: @0-CYBERDYNE-SYSTEMS-0 · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Guided setup
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Shell exec
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview code-first-responder.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# Code First Responder

## 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: ...

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> When to load this skill → Guardrails → Five-step micro-playbook → Output checklist → Response snippet to send back to the user → Debug Status
terms    -> Snapshot context · Reproduce fast · Isolate scope · Propose fix plan · Optional patch
files/cmd -> templates/debugreporttemplate.md · must · optional · blocked · templates/fixchecklist.md · runcommand · readfile · searchcode
body sha256 -> 67f3213f620c

Decide Fit First

Design Intent

How To Use It

Boundaries And Review

Code First Responder

When to load this skill

Guardrails

Five-step micro-playbook

Output checklist

Response snippet to send back to the user

Companion tools

Discussion