qp-regress SKILL.md skillA
qp-regress from chrono-meta/forge-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add chrono-meta/forge-harness/qp-regress@git:20260905.5d5657bPins git:20260905.5d5657b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- chrono-meta/forge-harness
- Path
plugins/fh-qp/skills/qp-regress/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260905.5d5657b, committed Sep 5, 2026
- Size
- 3,065 bytes
- Repository stars
- 31
- License
- MIT
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", "회귀 확인해줘", "지난 런이랑 비교해줘".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 ``` …
Read the whole file at its exact version.
How to install
mdr add chrono-meta/forge-harness/qp-regress@sha256:97527adae225592fThe line at the top of this page pins the label git:20260905.5d5657b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_v7anjlszoguxtv2f)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 5, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3065 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
chrono-meta/forge-harness · 31 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_v7anjlszoguxtv2f GET https://markdownregistry.com/api/v1/resolve?ref=chrono-meta/forge-harness/qp-regress GET https://markdownregistry.com/api/v1/blob/97527adae225592f5a68a45483cd5f7b20e6253719b8e238faabb8026e4e0db5
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.