qp-regress — Claude Code skill: what it does, how to install
Re-runs QA test suites unchanged, calculates screen reach, and tracks status deltas per test case instead of relying on batch totals.
npx skills add chrono-meta/forge-harness --skill qp-regress -a claude-codeWhat qp-regress does
The skill manages the regression step in the QP framework. It consumes a previous run directory qp/run/<ts>/ alongside the baseline test plan in qp/plan/tcs.tsv. Every test case executes again via qp-run strictly without modifications, preserving the integrity of the regression check.
Next, the skill runs plugins/fh-qp/scripts/qp_tools.sh to measure surface_reach. This step verifies whether the test batch actually progressed past the initial view. If a broken deployment or auth wall holds back every test, the run gets flagged as NOT_REACHED, marking all failures as unmeasured rather than genuine code defects.
All artifacts land in qp/regress/<ts>/. The generated delta.tsv evaluates each test case on its own line: flag changed=yes triggers whenever a verdict flips or when validation downgrades from machine checks to judgment. The workflow fails immediately without bash and a properly formatted baseline run directory.
What it helps with
- re-run existing test cases without altering input parameters
- detect whole-batch blockers at the entry view
- compare individual test verdicts against an earlier run
- spot test criteria that shifted from machine checks to judgment
Example prompts for the agent
- Check whether anything regressed since the last run
- Re-run the previous QA pass and compare results
- Compare this execution against the baseline with qp-regress
How to install qp-regress
1Skills CLI (Vercel)
npx skills add chrono-meta/forge-harness --skill qp-regress -a claude-code2Manually: put the files in place
~/.claude/skills/qp-regress/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/qp-regress/
1Skills CLI (Vercel)
npx skills add chrono-meta/forge-harness --skill qp-regress -a codex2Manually: put the files in place
.agents/skills/qp-regress/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add chrono-meta/forge-harness --skill qp-regress -a cursor2Manually: put the files in place
.cursor/skills/qp-regress/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install chrono-meta/forge-harness qp-regress2Manually: put the files in place
.github/skills/qp-regress/SKILL.md1Skills CLI (Vercel)
npx skills add chrono-meta/forge-harness --skill qp-regress -a gemini-cli2Platform CLI
gemini skills install https://github.com/chrono-meta/forge-harness --path plugins/fh-qp/skills/qp-regressManually: put the files in place
.devin/skills/qp-regress/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add chrono-meta/forge-harness --skill qp-regress -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about qp-regress
How to install qp-regress in Claude Code?
Run npx skills add chrono-meta/forge-harness --skill qp-regress -a claude-code in your terminal.
What does qp-regress do?
It re-executes baseline test cases without edits, computes the surface_reach ratio, and generates a per-test difference report in delta.tsv and report.md.
What happens if surface_reach returns NOT_REACHED?
All failures are formally marked as unmeasured in report.md because the run never navigated past the initial screen.
Source text
SKILL.md · MIT
--- name: qp-regress description: Regression stage of QP — re-executes a previous run's test cases unchanged, computes surface_reach (how many TCs left the entry screen, as a ratio over ALL TCs), and reports the per-TC delta against the earlier run so a "no change" claim is per case, not an aggregate. Triggers on "did anything regress since last run", "re-run last week's QA pass", "compare this run with the previous one", "회귀 확인해줘", "지난 런이랑 비교해줘". user-invocable: true allowed-tools: ["Read", "Bash", "Write", "Glob", "Grep"] model: sonnet origin: chamber run fh-qa-generic (2026-09-05) --- # qp-regress — Regression (re-run unchanged → surface_reach → delta) Input: a baseline `qp/run/<ts>/` and the same `qp/plan/tcs.tsv`. Output: `qp/regress/<ts>/`. ## 1. Re-run unchanged Execute the baseline's TCs with `qp-run` **without editing them**. Editing a TC to make it pass is a new run, not a regression — say so if the user asks for it. ## 2. surface_reach — did the batch leave the entry screen? ``` bash plugins/fh-qp/scripts/qp_tools.sh surface-reach qp/run/<new-ts>/evidence.tsv ``` | result | meaning | |---|---| | `REACHED n/n` | every TC observed a screen other than the modal (entry) one | | `PARTIAL k/n` | some did — report **which** did not, by tc_id | | `NOT_REACHED 0/n` | the whole batch sat on one screen (a login wall, a dead env). Every FAIL in that run is **unmeasured**, not a detection — write that sentence in the report | | `UNMEASURED` (rc 10) | no evidence file / empty — not a zero | Denominator is **all TCs**, including ones that never executed; write `surface_reach.txt` with the raw line. ## 3. Per-TC delta — `delta.tsv` ``` tc_id baseline_status new_status changed note ``` One row per TC. `changed=yes` on any status change **or** on a same-status verdict whose `closure` moved from MACHINE to JUDGMENT (the check got weaker). A run where every row is `changed=no` may say "no regression"; a run reported only as "12 PASS both times" may not — the aggregate hides a swap. ## 4. Report — `report.md` First 8 lines: target · engine/adapter/evidence · `#mtm:` state · surface_reach line · counts PASS/FAIL/BLOCKED/AMBIGUOUS new vs baseline · number of `changed=yes` · the sentence for NOT_REACHED if it applies · what was **not** measured (unexecuted TCs, dropped screenshots). ## Done When 1. `surface_reach.txt` holds a `REACHED|PARTIAL|NOT_REACHED|UNMEASURED` line produced by the tool · **[mandatory-pass]**. 2. `delta.tsv` has one row per TC in the baseline · **[measured]** — row count equals distinct tc_ids. 3. A NOT_REACHED run's report contains the "FAILs are unmeasured" sentence · **[measured]** — grep. 4. The delta's `changed` column reflects real behavior change, not selector drift · **[judged — pairing: for each `changed=yes`, the before/after DOM snapshots are attached and a second session confirms the element moved, not the locator]**. ## Independently executable Yes — needs a baseline run dir in the documented shape and bash.
© chrono-meta · MIT · chrono-meta/forge-harness