跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
营销与销售

qa-report-humanizer

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.

kindlmann · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add petrkindlmann/qa-skills --skill qa-report-humanizer

技能说明


name: qa-report-humanizer description: >- 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. license: MIT metadata: author: kindlmann version: "2.1" category: process

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 exec, or a customer? An engineer wants the failing selector and the repro; an exec wants ship/no-ship and open blockers; a customer wants impact and timeline. The register and what you cut differ for each.
  • What channel — Slack, PR comment, or a formal report? Slack gets 2-3 lines and a link; a PR comment gets the specific code/selector fix; a report gets structure. Length and formatting follow the channel.
  • Is any information deliberately excluded from this audience? Otherwise keep every supplied count, percentage, severity, identifier, result, and material qualification. These are locked by default; do not ask permission to preserve them. Name relevant missing evidence instead of inventing it (see Core Principle 5).

Core Principles

  1. Specific beats comprehensive. "Login fails when the email has a plus sign" beats "Various authentication edge cases were identified." The reader fixes the first and learns nothing from the second. Name the behavior, the trigger, and the scope when supplied. When they are absent, identify the missing details without inventing a better story.

  2. Say what happened, not what category it falls into. "Authentication module" is a bucket; "login with plus-sign emails" is a bug. Categories let the writer sound thorough while hiding that they don't know the specifics. Use concrete details from the source; a vague source may need a short statement of what is still unknown.

  3. If the reader can't tell what broke or what to do, the report failed. Write for the person who has to fix it at 4pm on a Friday. Lead with what's broken or risky, then what they should do about it. Skip the parts nobody reads.

  4. Preserve facts and uncertainty. The rewrite changes the prose, never the data. Keep exact numbers, severities, error strings, test names, commit IDs, and timestamps attached to the same result and environment. Do not round percentages or infer failure counts from a rounded pass rate. Preserve "suspected," "not reproduced," "not run," and "not approved": these describe evidence, not filler. A prior build's passing run does not establish the current candidate's status. A recommendation is not approval.

  5. Never invent the specifics you're asked to add. "Make it specific" tempts the model to manufacture an exact percentage, an incident count, or a repro it never saw. Do not. If the source is vague and the number isn't verifiable, the honest rewrite names the gap ("user impact not measured") instead of writing "8% of users." A fabricated metric is a worse failure than a vague one.

QA-specific AI patterns to detect and fix

Each rewrite below uses only facts in its draft. A missing detail remains missing.

1. The template opener

Draft: "Test execution was completed successfully for Sprint 47. A total of 342 test cases were executed across 5 test suites, achieving a 97.4% pass rate."

Rewrite: "Sprint 47: 342 tests run across 5 suites; reported pass rate 97.4%. The draft does not give the failure count, affected suites, or whether failures are new or known."

The rounded rate cannot establish an exact failure breakdown. Do not invent checkout failures or flaky tests to make the report more useful.

2. Inflated severity language

Draft: "A critical defect was identified in the authentication module that could potentially impact the user experience across multiple touchpoints."

Rewrite: "A critical authentication defect was reported. The broken behavior, reproduction steps, and affected users are not specified."

Keep the reported severity without independently confirming it. Plus-sign emails and an affected-user percentage belong here only when the source supplies them.

3. The pass-rate obsession

Draft: "The overall pass rate increased from 94.2% to 97.1%, demonstrating significant improvement and showcasing the team's commitment to quality."

Rewrite: "Pass rate increased from 94.2% to 97.1%. The cause of the change and which tests changed are not given."

Keep exact percentages. Do not attribute the change to repairs, flakiness, or fewer product defects without evidence. If causes are supplied, lead with them.

4. Generic risk language

Draft: "Several high-risk areas have been identified that require careful monitoring. The team recommends continued vigilance and proactive testing."

Rewrite: "The draft reports high-risk areas

阅读完整来源 ↗