qa-report-humanizer
适合把模糊模板化输出变成可行动的工程级报告。
可能改写事实或引入不实细节，需人工复核。
将 QA 报告、缺陷与状态更新中的机器化表达去除并重写为可执行的工程语言。
把机器化、模板化的 QA 报告、缺陷描述和状态更新改写成工程师能马上理解和执行的语言，保留事实不乱编数据。用在需要把 AI 风格或呆板报告变成人话、修正严重度夸大或让交付方能看懂时。特点是既能去掉“机器人感”，又保证不凭空增加数字或错误，让问题可复现可追踪。
▸ 展开 SKILL.md 英文原文
Remove AI-generated patterns from QA reports, bug reports, test summaries, status updates, and quality communications. Detects and rewrites robotic test-result language, template-sounding status updates, inflated severity descriptions, and generic stakeholder reports — without inventing facts. Makes QA writing sound like a real engineer wrote it. Use when: "humanize report," "rewrite QA summary," "fix test report," "make this sound human," "clean up status update." Not for: general prose, blog, or marketing-copy cleanup — use the global humanizer skill. Not for: classifying or routing CI failures — use ai-bug-triage. Related: ai-bug-triage, qa-metrics, qa-dashboard, quality-postmortem.
帮我安装这个 skill：https://raw.githubusercontent.com/petrkindlmann/qa-skills/main/skills/qa-report-humanizer/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/petrkindlmann/qa-skills/main/skills/qa-report-humanizer/SKILL.md"<objective> A polished QA report that says nothing is worse than a rough one that says what broke. "A critical defect was identified in the authentication module" passes every grammar check and tells the reader nothing. This skill rewrites QA reports, bug reports, test summaries, and status updates so a real engineer can act on them — and guarantees the rewrite invents no numbers, errors, or severities that were not in the source. </objective> ## Discovery Questions Check `.agents/qa-project-context.md` first — it carries the team's tone, the tracker, and severity conventions; skip anything answered there. Then clarify only what changes the rewrite: - **Who reads this — an engineer, an ex