agentleFS
Sign inStart free
PantaniPantani/ableton-mind/.claude/skills/test-coverage-expansion/SKILL.md

test-coverage-expansion

Skill9 starsChanged 5 months agoMITView on GitHub

Add or plan missing tests for ableton-mind. Use for untested code, regression tests, coverage gaps, commands without tests, TS tools, Python bridge handlers, CLI scripts, recipes, knowledge, distribution checks and audit-driven fixes.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Use this skill when audit findings need tests or when code lacks nearby coverage.

    line 8
  2. Distinctive:

    Add focused failing tests before fixes when feasible.

    line 14
  3. Distinctive:

    Keep default tests offline and deterministic.

    line 15
  4. Distinctive:

    Prefer existing Vitest and Python unittest patterns.

    line 16
  5. Distinctive:

    Run focused tests first, then broader suite when the change surface justifies it.

    line 17
  6. Very specific:

    Write _workspace/quality-audit/test-coverage-{N}.md with:

    line 30
  7. Distinctive:

    Test added or proposed.

    line 33

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

Test Coverage Expansion

Use this skill when audit findings need tests or when code lacks nearby coverage.

Workflow

  1. Map changed or risky implementation files to existing tests.
  2. Identify coverage gaps that protect public behavior, not trivia.
  3. Add focused failing tests before fixes when feasible.
  4. Keep default tests offline and deterministic. Use fakes for Ableton Live and Push behavior.
  5. Prefer existing Vitest and Python unittest patterns.
  6. Run focused tests first, then broader suite when the change surface justifies it.

Coverage Priorities

  1. MCP tool schemas, validation errors and verify/diff behavior.
  2. JSON-RPC bridge handler shapes and error handling.
  3. CLI doctor and install failure modes.
  4. Distribution package contents and manifest/version sync.
  5. Recipe and knowledge consistency.
  6. Regression tests for every BLOCKER or MAJOR audit fix.

Report Format

Write _workspace/quality-audit/test-coverage-{N}.md with:

  • Gap.
  • Existing tests checked.
  • Test added or proposed.
  • Command run.
  • Remaining risk.

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