agentleFS
Sign inStart free
connext-solutionsconnext-solutions/flowctl/.claude/skills/seeded-bug/SKILL.md

seeded-bug

Skill1 starsChanged 5 days agoApache-2.0View on GitHub

Use when adding an assertion kind, changing the verifier, or proving flowctl catches a class of defect. Adds a switchable defect to fixture-app and an accuracy test showing a correct run reports it as failed.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If it is still caught without the assertion, another assertion catches it: pick a sharper defect.

    line 23
  2. Very specific:

    Run bun run test:accuracy: the clean app passes, every mode fails.

    line 24
  3. Distinctive:

    Never weaken, rename or delete an existing mode to make a test pass.

    line 26

≈ “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.

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

Add a seeded bug

flowctl's "accurate" goal is measured here: every assertion kind should catch at least one defect that no other assertion catches, and the clean app must pass. Every kind is covered today, including url (redirectWrong) and value (formNotReset); the coverage list is in packages/fixture-app/AGENTS.md.

  1. Name the defect a real app could ship (wrong status, nothing saved, wrong record changed, toast on failure, missing validation, visible to the wrong role…). Pick the assertion that should be the only thing catching it.
  2. Add the mode to BUG_MODES in packages/fixture-app/src/server.ts with a JSDoc @remarks line. Implement it as a branch on bug === '<mode>' (server) or window.BUG (page script in pages.ts).
  3. Cover it with a flow. Extend a sample flow in packages/fixture-app/flows/ or add one (tag fixture). The assertion is written from the intended behaviour, never from what the buggy app shows.
  4. Map it in CAUGHT_BY (packages/core/test/seeded-bugs.accuracy.test.ts), or in the exploration accuracy test if it is about exploration.
  5. Prove the assertion is load-bearing: temporarily delete that one assertion and run bun run test:accuracy — the new mode must now be reported passed (missed). Restore it; it must be failed. If it is still caught without the assertion, another assertion catches it: pick a sharper defect.
  6. Run bun run test:accuracy: the clean app passes, every mode fails. Add the row to packages/fixture-app/README.md.

Never weaken, rename or delete an existing mode to make a test pass.

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.

Check your setup, free