agentleFS
Sign inStart free
DjarvurDjarvur/go-ultimate/skills/test-audit/SKILL.md

test-audit

Skill31 starsChanged 13 days agoMITView on GitHub

Writing/changing/reviewing/sweeping tests: reject duplicate or implementation-coupled proof; remove test-only production seams.

80 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use chips, redo and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • udecodeSkill

    chips

    Run the project's suggested-task ledger, the chips. /chips alone brings this session's open tasks up to date: it applies what the ledger helper says, settles stale and split tasks, cards what can start and reports the board, and /chips all also takes the ship-list tasks and the ones no live session owns, and merges duplicate tasks across the board. Use for /chips, /chips offer, start or drop, \"what chips are open\", \"suggest a task for X\", \"update the chips\", \"clean up the chips\", \"which chips are stale\", \"is this chip still worth doing\", \"merge duplicate chips\", at the last hand-back of a run that offered a task, and whenever pstack would file a tracked issue, a follow-up, a reflect Backlog item or an out-of-band PR.

    Also in 3 projects that use this

  • Scylla23Skill

    redo

    Re-run the last routed task one model tier up (haiku → sonnet → opus → fable). User-invoked escalation when the previous result missed. Pass --dry-run to preview without running.

    Also in 3 projects that use this

  • Aetheria-Labs1Skill

    plan-page

    Plan one storefront page from strategy through final copy, section order, proof, offers, template direction, responsive layout, and production asset requirements. Stops at an approved execution-ready specification.

    Also in 3 projects that use this

  • SocialKit-APISkill

    video-transcripts

    Extract transcripts from social videos through SocialKit across YouTube, TikTok, Instagram, Facebook, X/Twitter, LinkedIn, and direct video file URLs. Use when the user asks to transcribe, get captions or subtitles, pull the spoken text, or read what a video says, including one video or many at once. Returns full text plus timestamped segments. Not for posting, private accounts, or unrelated website scraping.

    Also in 3 projects that use this

  • lorissun2025Skill

    project-docs

    Software development project documentation management and progress tracking. Use when: (1) Initializing a new software project and need to create all required documentation (MRD, PRD, Technical Plan, Roadmap), (2) Updating project roadmap after completing tasks, (3) Getting a summary of current project progress, (4) Resuming work on a project after a break and need to understand what's next, (5) Checking if required project documents exist and are complete

    Also in 3 projects that use this

  • swyxioSkill

    autoreview

    Perform a structured final code review of a local diff, commit, branch, or pull request. Use only when the user explicitly asks for autoreview, a second review, or a final review before commit, merge, or release, or when repository instructions require one. Do not trigger automatically for ordinary non-trivial edits.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 77 edited versions we read keep these.

  • 5

    Distinctive

    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:

    Before adding test, answer:

    line 14
  2. Distinctive:

    Keep the change proportional: one good regression beats a suite of shape checks.

    line 21
  3. Distinctive:

    Keep independent API, SDK, protocol, config, migration, storage, security, platform, default, prompt-byte, generated-language, package, …

    line 43
  4. Very specific:

    Before audit edit: read candidate evidence and workflow.

    line 52
  5. Distinctive:

    Delete obsolete production seams with tests.

    line 54
  6. Distinctive:

    Run the owner's test suite plus its siblings after each batch.

    line 55

“Common” is measured: kept by at least 6 in 10 of the 77 edited versions of this file we could read. “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

Test Audit

  • Authoring gates every new/changed test.
  • Audits: remove low-value proof in coherent owner batches; never chase deletion counts.
  • Whole-subsystem campaign: read CAMPAIGN.md first.

Authoring gate

Before adding test, answer:

  1. Protected observable behavior, invariant, or independent contract?
  2. Credible regression that makes it fail?
  3. Why existing proof misses it? Each contract: one primary owner at strongest boundary. Another layer needs distinct transport/lifecycle risk. Extend tables/shared fixtures; consolidate repeated setup.
  • Keep the change proportional: one good regression beats a suite of shape checks.
  • Export, flag, wrapper, injection hook with no production caller needed? Move proof to real boundary instead.
  • Regressions must fail pre-fix for intended reason, pass after repair; report unavailable baseline proof.
  • One owner regression covers bug; never replay at every crossed layer.
  • Behavior-preserving refactors should not break test.

Junk patterns

  • Reject self-comparisons, copied inventories, source greps, implementation/call-shape assertions, duplicate contracts, test-only seams, subject-generated expected values, mocks supplying asserted behavior.
  • Fixtures must not fabricate owner receipts/order or claim persistence path never writes.
  • Negative controls must fail at intended guard; names must match exercised behavior.
  • Auditing candidates: use full checklist.

Retention bar

  • Keep independent API, SDK, protocol, config, migration, storage, security, platform, default, prompt-byte, generated-language, package, release, architecture, observable-ordering contracts. Static/slow ≠ disposable.
  • Source inspection must survive identifier-only refactors and guard independent user-facing contract.
  • Baseline failures may be bugs to repair, not tests to delete.

Audit and validation

  • Before audit edit: read candidate evidence and workflow; inspect full owners/callers/history; record remaining proof before deletion.
  • Delete obsolete production seams with tests; never optimize for deletion counts.
  • Run the owner's test suite plus its siblings after each batch; re-run any check the deleted tests fed. Behavior-preserving refactors must stay green.
  • Report causes, retained contracts, proof/cost, production versus test LOC, follow-ups. Commit/push/land only with task authority.

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