build-regression-pack
Skill0 starsChanged 17 days agoMITView on GitHub
Name the tests that must run for this release train, from evidence. Use when the user asks for a regression pack, release test set, or /build-regression-pack. Do not invent tests that do not exist. Do not claim they passed unless this session ran them.
In this repository66 other files it gives its agents.
- AGENTS.mdAGENTS.md
- a11y-passSkill
- assess-changeSkill
- charter-exploratorySkill
- classify-dataSkill
- commitSkill
- cut-releaseSkill
- data-changeSkill
- debugSkill
- design-experimentSkill
- diff-environmentsSkill
- draft-steercoSkill
- engineering-barSkill
- explain-codeSkill
- explore-codebaseSkill
- fix-ciSkill
- handoffSkill
- implement-changeSkill
- incident-triageSkill
- lean-reviewSkill
- map-dependenciesSkill
- map-design-handoffSkill
- map-processSkill
- open-prSkill
- performanceSkill
- plan-data-migrationSkill
- plan-incrementSkill
- plan-rollbackSkill
- plan-uatSkill
- prioritize-backlogSkill
- production-passSkill
- ready-to-mergeSkill
- record-decisionSkill
- refactor-safelySkill
- revert-changeSkill
- review-architectureSkill
- review-changeSkill
- review-pipelineSkill
- security-passSkill
- shape-workSkill
- ship-notesSkill
- spec-analyticsSkill
- spec-observabilitySkill
- start-projectSkill
- synthesize-discoverySkill
- triage-blockersSkill
- triage-defectSkill
- update-raidSkill
- verify-uiSkill
- write-api-examplesSkill
- write-architectureSkill
- write-designSkill
- write-dev-tasksSkill
- write-docsSkill
- write-integration-contractSkill
- write-nfrSkill
- write-opportunitySkill
- write-prdSkill
- write-requirementsSkill
- write-runbookSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Do not invent tests. Do not claim pass without command output.
- Distinctive: line 41
Read AGENTS.md if present.
- Distinctive: line 42
Read the commit range or the user-named features.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Build regression pack
List what must run for this train. This is not write-tests and not ready-to-merge for a single diff.
Do not invent tests. Do not claim pass without command output.
Is this the right skill?
| Signal | Do this instead |
| New cases for a feature | write-test-plan / write-tests |
| One change merge-ready | ready-to-merge |
| UAT | plan-uat |
Required inputs
- Release range or train name
- Existing tests in the repo and/or
docs/qa/plan-*.md AGENTS.mdtest command
Human decisions (do not invent)
- What may be skipped this train (waiver)
Procedure
- Read
AGENTS.mdif present. List test commands it records. - Read the commit range or the user-named features. Map to existing test files or plan ids.
- Find the home:
docs/qa/regression-<slug>.md. - Open references/regression-template.md. Copy every heading. Write
n/awhen unused. - Each item: how to run (from
AGENTS.mdor a real file path), why it is in (feature / risk). Missing coverage →gap, not a fake test name. - Result column stays
not rununless this session ran the command. - When asked to execute the existing list, use a separate verifier handoff: run every required item against the exact release revision in the recorded environment and attach output and exit status. Missing, failed, unknown, or not-run items and uncovered risks block release unless the authorized human records a waiver using
context/decision-rights.md. A completed test list alone is not release evidence.
Output
- Path:
docs/qa/regression-<slug>.md - Template:
references/regression-template.md
Quality bar
- Every run item is a real path or
AGENTS.mdcommand - Gaps are listed, not papered over
- No pass without this session’s output
- Release handoff distinguishes the planned list from executed results and names the exact revision
- Unused headings are
n/a
Done
- Path
- Item count + gap count
- Next skill: run via
verifier;write-testsfor gaps;cut-releaseafter go/no-go
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.