agentleFS
Sign inStart free
onegunsamuraionegunsamurai/OpenLearning/.claude/skills/test-audit/SKILL.md

test-audit

Skill1 starsChanged 8 months agoMITView on GitHub

Audit test coverage and quality across both stacks

80 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use chips, redo and 10 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

  • clawdbotSkill

    pr-simplify

    Simplify your own change to its smallest complete fix. Use before opening a PR, before pushing large repairs to one, or when asked to shrink a PR or clean up slop.

    Also in 3 projects that use this

  • spitoglouSkill

    technical-documentation

    Create and improve technical documentation including architecture designs, PRDs, API docs, code explanations, and visual diagrams. Use when asked to document systems, explain codebases, create design documents, write PRDs, generate Mermaid/PlantUML diagrams, review architecture, write user stories, or create pull request descriptions. Triggers include "document this", "create a design doc", "explain this code", "write a PRD", "create a diagram", "architecture overview", "user story for", "PR description".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 77 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Edge cases: Look for missing tests around empty inputs, error responses, boundary values.

    line 27
  2. Distinctive:

    Error paths: Verify tests exist for exception/error branches, not just happy paths.

    line 28

“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 Coverage & Quality Audit

Analyze the test suite for coverage gaps, weak assertions, and missing edge cases.

Steps

1. Map Source → Test Files

Backend:

  • For each file in backend/app/routes/, backend/app/agents/, backend/app/models/, backend/app/services/ — find the corresponding test file in backend/tests/.
  • Flag any source file with no corresponding test file.

Frontend:

  • For each file in frontend/src/ (components, hooks, stores, lib) — find co-located *.test.ts(x) files.
  • Flag any source file with non-trivial logic but no test file.

2. Assess Test Quality

For each test file, check:

  • Assertion strength: Tests that only check toBeTruthy() or status codes without verifying response bodies are weak.
  • Over-mocking: Tests with more than 3 mock/vi.mock/patch calls may be testing mocks, not code.
  • Edge cases: Look for missing tests around empty inputs, error responses, boundary values.
  • Error paths: Verify tests exist for exception/error branches, not just happy paths.
  • Async handling: Backend tests should use async def + await; frontend tests should properly await async operations.

3. Run Test Suites

cd backend && pytest tests/ -v 2>&1
cd frontend && npm test 2>&1

Report pass/fail counts and any failures.

Output Format

Source FileTest FileStatusIssues
routes/assess.pytests/test_assess.pyCoveredWeak assertions on line 42
agents/calibrator.py—MissingNo test file exists

Then provide prioritized recommendations:

  1. Critical: Untested files with complex logic
  2. High: Tests with weak assertions or excessive mocking
  3. Medium: Missing edge case coverage

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