qa-trend

name	qa-trend
description	Compare two QA audit runs and report what improved, what regressed, and what persists. Use when the user asks "did it improve since last time?", "compare audits", "QA trend", or invokes /qa-trend. Requires at least two timestamped runs under qa-reports/runs/.

QA Trend — Audit Comparison

You compare two audit runs and produce a trend report. Default: the two most recent runs. The user may name specific runs or a date range.

Step 1 — Locate runs

• List qa-reports/runs/ (folders named YYYY-MM-DD_HHMM).
• Fewer than 2 runs → tell the user to run /qa-audit again later and stop.
• Read QA-MASTER-REPORT.md from each selected run. If an agent report exists in one run but not the other, note the coverage difference — don't treat missing coverage as "fixed".

Step 2 — Match findings

Match findings between runs by root cause, not by exact title (titles vary between runs). Two findings match when they point at the same location/component AND describe the same problem. Classify each finding:

• FIXED: in the old run, absent in the new one (and the area WAS re-tested).
• NEW: in the new run, absent in the old one.
• PERSISTING: in both. Track severity changes (escalated/downgraded).
• NOT RE-TESTED: old finding in an area the new run didn't cover.

Step 3 — Compute the trend

• Severity totals per run (critical/high/medium/low) and the delta.
• Weighted score per run: critical=10, high=5, medium=2, low=1. Lower is better.
• Trend verdict: IMPROVING (score down ≥20%), STABLE (within ±20%), REGRESSING (score up ≥20%). If coverage differs significantly, say so and qualify the verdict.

Step 4 — Report

Write qa-reports/trend-report.md:

# QA Trend — [old run] → [new run]
**Verdict**: IMPROVING | STABLE | REGRESSING (score: X → Y)
## Severity Delta
| Severity | Before | After | Δ |
## Fixed (celebrate these)
- [severity] [title] — fixed by/why if known
## New
- [severity] [title]
## Persisting (the backlog that matters)
- [severity] [title] — present since [first seen run]
## Not Re-Tested
- [items + why coverage differed]

Also generate qa-reports/trend-report.html reusing the visual style of the qa-audit template (.claude/skills/qa-audit/report-template.html): severity cards showing before → after, sections for Fixed (green), New (red), Persisting (yellow). Self-contained single file.

Step 5 — Final response

• Trend verdict + score delta in one line.
• Top 3 changes (best fix, worst new issue, oldest persisting issue).
• Report paths.