agentleFS
Konadu-Akwasi-AkuokoKonadu-Akwasi-Akuoko/katto/.claude/skills/emitter-snapshot-change/SKILL.md

emitter-snapshot-change

Skill2 starsChanged 5 months agoMITView on GitHub

Use when changing any snapshot-frozen emitter in katto-engine — FCPXML, SRT/VTT, or ffmpeg filtergraph text — or when an insta snapshot test fails after an engine change.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Distinctive:

    Decide: bug or contract change?: If the snapshot diff is *unexpected*, the code change is wrong — fix the code, don't accept the snapshot.

    line 12
  2. Distinctive:

    Real-import check: If the FCPXML structure changed (not just values), note in the PR that the manual FCP/Resolve import checkpoint must …

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Change a snapshot-frozen emitter

Emitter output is contract, not implementation detail: FCP rejects out-of-order FCPXML elements with cryptic errors, and filtergraph text must stay byte-identical for determinism. Snapshots are how the contract is frozen.

Checklist (todo per item)

  1. Decide: bug or contract change? If the snapshot diff is unexpected, the code change is wrong — fix the code, don't accept the snapshot. Only intentional output changes proceed.
  2. Failing test first. For new emitter behavior (e.g. a new element, the rescue track), add the fixture + named snapshot assertion before implementing: assert_snapshot!("<scenario_name>", output).
  3. Run cargo insta test — inspect every pending snapshot.
  4. Review with cargo insta review — accept only diffs you can explain line-by-line. An unexplained attribute reorder is a regression, not noise.
  5. Invariants intact. FCPXML: every offset/duration/start/frameDuration is rational <num>/<den>s (never a decimal), rescue-track fixture still emits removed segments on the disabled/muted track, element order unchanged unless that was the point. Filtergraphs: floats at 6 decimals, trim/atrim + concat shape.
  6. Commit .snap files in the same commit as the code change, reason in the body. Never commit .snap.new (gitignored and hook-blocked anyway).
  7. Real-import check. If the FCPXML structure changed (not just values), note in the PR that the manual FCP/Resolve import checkpoint must re-run before release.
  8. Gate. just check.

Red flags

  • Accepting a snapshot to "make CI green" without explaining the diff.
  • Editing a .snap file by hand.
  • Converting a rational time to a decimal to simplify a diff.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.