Bug Reproduction Brief【免费下载链接】awesome-copilotCommunity-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot.项目地址: https://gitcode.com/GitHub_Trending/aw/awesome-copilotTarget and commit:Environment:Expected:Actual:Minimal steps:Minimal fixture:Reproduced: yes / no / intermittentEvidence:Unknowns:Safe next hypothesis to test:其中各字段的含义与填写要点 | 字段 | 说明 | | --- | --- | | Target and commit | 目标仓库与精确提交号保证可回放 | | Environment | 第 2 步中检查确认的环境事实 | | Expected / Actual | 第 3 步的两条可观察陈述 | | Minimal steps | 第 4 步化简后的最小复现步骤 | | Minimal fixture | 仍能触发失败的最小输入/夹具 | | Reproduced | 三态yes / no / intermittent如实标记 | | Evidence | 命令输出、日志、截图等证据已脱敏 | | Unknowns | 尚未确认的信息诚实留白 | | Safe next hypothesis to test | 下一个可安全验证的假设供后续诊断工作流接手 | ## 五、安全边界复现过程中的红线 技能单独列出了五条安全边界属于不可逾越的红线 1. **不得仅为复现 Bug 而修改生产数据**Do not change production data merely to reproduce a bug 2. **不得发布密钥、客户记录或私有源码**Do not publish secrets, customer records, or private source 3. **不得仅凭相关性断言根因**Do not claim a root cause from correlation alone——相关性不等于因果 4. **优先使用只读或可逆的探索手段**Use read-only or reversible discovery first 5. **在获得经过验证的复现后停止**诊断与修复是独立的工作流Stop after a verified reproduction; diagnosis and repair are separate workflows。 ## 六、实战示例如何触发该技能 技能内置了一个可直接使用的示例 prompt text Use the Bug Reproduction Brief skill on the failing checkout test. Do not fix it yet. Reduce it to the smallest safe failing fixture and report the exact command evidence, expected result, actual result, and remaining unknowns.【免费下载链接】awesome-copilotCommunity-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot.项目地址: https://gitcode.com/GitHub_Trending/aw/awesome-copilot创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考