菜单
Turn a test failure into a structured bug report with repro steps, severity, and expected vs actual. Use when the user runs /bug-from-failure or asks to file a bug from a failing test.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/kint4/autoframe --skill bug-from-failure命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Map API endpoints against existing API tests to show what is tested and what is missing. Use when the user runs /api-coverage or asks which endpoints are covered.
Map spec files against requirements or features to show what is covered, missing, and redundant. Use when the user runs /coverage-map or asks what is tested.
Explain any file in the suite in plain language, teaching the pattern behind the code. Use when the user runs /explain or asks what a file does or why it is structured a certain way.
| name | bug-from-failure |
| description | Turn a test failure into a structured bug report with repro steps, severity, and expected vs actual. Use when the user runs /bug-from-failure or asks to file a bug from a failing test. |
Type: Functional Description: Turns a test failure into a structured, shareable bug report with repro steps, severity, environment, and expected vs actual behavior.
Any of:
A structured bug report in markdown:
### Title
[concise summary]
**Severity:** Critical / High / Medium / Low
**Environment:** [browser, base URL, env]
**Feature / Area:** [feature]
**Steps to Reproduce**
1. ...
**Expected Result**
...
**Actual Result**
...
**Evidence**
[log excerpt / screenshot / trace reference]
**Notes**
[suspected cause, related tests]
/flake-check.playwright.config.ts / .env variables (never paste secret values)..env./flake-check instead of filing a bug.