代码第一响应者

人工智能 社区

技能解读

当前原文的自动摘译,尚未人工审校。

何时使用该技能

当用户请求与该技能的领域和功能匹配时使用。当明确请求此工作流程或工具链时使用。

什么时候不应该使用这个技能

当其他技能更适合该任务时,请勿使用。当请求超出该技能的范围时请勿使用。

何时加载该技能

传入任务引用失败的测试、堆栈跟踪或最近的合并。用户明确想要“快速分类”、“初步检查”或“粗略修复计划”。另一项技能(例如快速研究)标记了需要确认的新代码问题。

护栏

在本地重现故障之前切勿编辑文件。捕获调试报告模板内的确切命令+退出代码。偏好最小差异;将重大重构推迟到后续任务。如果无法快速重现故障,请使用捕获的证据升级并保持存储库不变。

五步微型剧本

快照上下文记录分支、最新提交哈希和脏文件。将失败摘要粘贴到templates/debug_report_template.md。快速重现 运行尽可能窄的测试或脚本。

流狐档案 运行与权限由流狐静态检查推断,不代表作者声明或实际测试结果。
领域
人工智能
作者声明的智能体
未找到明确声明;不据此推断已兼容或已测试
静态检查
88 / 100 · 启发式扫描,不代表运行安全
运行环境证据
未执行;当前没有隔离运行测试证据
作者 / 版本 / 许可证
@0-CYBERDYNE-SYSTEMS-0 · 未声明许可证
上下文用量评级
低消耗
接入复杂程度
需简单配置
是否需要外部接口密钥
不需要
兼容的系统
未声明(默认跨平台)
运行环境要求
未检出明确要求
检测到的文件与系统行为
  • 只读
  • 允许写入 / 修改
  • 命令执行
网络行为
仅限本地
安装命令数
无(仅作为资料)

需要注意: 未声明工具权限范围;实际权限由运行环境决定。

作者说明文件(原文) SKILL.md

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

讨论

基于 GitHub Discussions。登录 GitHub 即可参与讨论、点赞、订阅更新。