Testland
testland/qaInstall

golden-file-manager

Action-taking agent that maintains snapshot / golden file health across a project - adds new baselines for previously-uncovered tests, updates baselines after intentional changes (refusing to update if the diff doesn't match the PR's stated intent), prunes orphaned baselines whose tests no longer exist, and applies sanitization rules from the golden-file-conventions catalog. Use as a periodic maintenance pass or after a refactor that touches many snapshot tests.

Install with Claude Code
/plugin install qa-test-data@testland-qa

Agents run in Claude Code. This installs the qa-test-data plugin. First time? Add the marketplace with /plugin marketplace add testland/qa

View source (opens in a new tab)
Agent
Plugin
qa-test-data
Category
Foundations
Version
v1.4.9
Tools
Read, Write, Edit, Grep, Glob, Bash(git diff *), Bash(git log *), Bash(npm test *), Bash(npx vitest *), Bash(npx jest *), Bash(pytest *)
Preloads
golden-file-conventions

A maintenance agent that turns snapshot drift into deterministic add / update / prune actions per the conventions in golden-file-conventions.

When invoked

The agent runs in one of three modes - pick based on the task at hand:

ModeTriggerAction
addTest exists with toMatchSnapshot() but no .snap file yetRun the test once; commit the generated snapshot.
updatePR has snapshot diffs and the title/description suggests intentional changeVerify the diff aligns with intent; run --update-snapshots; commit.
pruneOrphaned .snap files with no matching test (test deleted)Remove the orphan; commit.

The agent refuses to update snapshots that don't match the PR's stated intent - same adversarial logic as visual-diff-classifier. A wrong-but-consistent snapshot is worse than no snapshot.

Mode 1 - Add

Find tests using toMatchSnapshot() / toMatchInlineSnapshot() and cross-reference against __snapshots__/ for gaps. For each:

  1. Run the test once (npm test -- <file>) to capture the snapshot.
  2. Inspect for sanitization hygiene per golden-file-conventions: no timestamps / UUIDs / volatile values, no real PII, no runner-absolute paths.
  3. If sanitization issues: amend the test (custom serializer or expect.any(...)) and re-run.
  4. Commit the snapshot with a descriptive message.

Mode 2 - Update

Read the PR title/body to extract stated intent. Classify each .snap diff:

  • Aligned - diff matches the stated change → include in update.
  • Adjacent - sibling component the PR touches transitively → flag for human confirmation; suggested-update only.
  • Unrelated - component the PR doesn't claim to touch → REFUSE to update; flag as likely regression; escalate to regression-bisector.

If all diffs pass: run npm test -- --update-snapshots and commit with a message referencing the PR's intent.

Mode 3 - Prune

Orphaned snapshots remain after the producing test is deleted. Compare existing .snap entries against current test names (Jest: npx jest --ci --listTests plus a describe/it cross-reference). For each orphan: confirm it's not a rename (git log); remove the entry; delete the file if empty; commit per orphan or batched.

Output format

## Golden-file maintenance - `<project>`

**Mode:** add | update | prune
**Files inspected:** N
**Actions taken:**

| Action     | Count | Files                                                  |
|------------|------:|--------------------------------------------------------|
| Added      |    3  | `src/components/Modal.test.tsx.snap` (new), ...        |
| Updated    |    7  | `src/components/Button.test.tsx.snap`, ...             |
| Pruned     |    2  | `src/components/Removed.test.tsx.snap`                 |
| Refused    |    1  | `src/components/Footer.test.tsx.snap` (see below)     |

### Refused updates

| File                                  | Reason |
|---------------------------------------|--------|
| `src/components/Footer.test.tsx.snap` | Diff in `Footer` component but the PR description says "Refactor Modal" - Footer was not mentioned. Suspected unintended cascade. |

**Recommended next step:** investigate Footer cascade with
[`regression-bisector`](../../qa-flake-triage/agents/regression-bisector.md);
do NOT update the Footer snapshot until the cascade is understood.

### Sanitization hygiene flags

The following added snapshots contain volatile values that will
flake on the next run; the test should be amended:

| File                            | Volatile field         | Suggested fix |
|---------------------------------|------------------------|---------------|
| `src/api/UserCard.test.tsx.snap` | timestamp 1714824000  | `expect.any(Date)` matcher in the test |
| `src/api/Session.test.tsx.snap`  | UUID 7f8a4b...         | `expect.any(String)` with regex check  |

Examples

  • Clean update: PR "Refactor Button to new color tokens" with 12 Button.* snapshot diffs - all Aligned; run --update-snapshots; one commit referencing the PR.
  • Refused cascade: PR "Add tooltip to icon buttons" with 3 diffs (2 IconButton, 1 Footer) - 2 Aligned; 1 Refused (Footer unmentioned). Commit the IconButton updates; flag Footer for review; suggest regression-bisector.
  • Prune sweep: feature removed in a prior PR left 8 orphaned snapshots; agent removes each, deletes 2 empty .snap files, commits one prune commit.

Anti-patterns

Anti-patternFix
Auto-update mode accepting any diffClassify against PR intent; refuse Unrelated diffs.
"Snapshot refresh" PR detached from source changeUpdate in the same PR as the code change.
Sanitization issues in newly-added snapshotsRe-run the test; reject if values vary; use expect.any(...) matchers.
Pruning without checking for renamesCross-reference git log for renames before pruning.

Hand-off targets

References