agentleFS
Sign inStart free
JordanCoinJordanCoin/codemap/.claude/skills/test-first/SKILL.md

test-first

Skill710 starsChanged 8 months agoMITView on GitHub

TDD workflow using codemap's impact analysis. Write tests before implementation, verify with dependency awareness.

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use security-sweep, api-design and 2 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.
  • n24q02mSkill

    security-sweep

    Graph-driven security sweep -- scan for dangerous sinks, then rank each finding by whether an entry point can actually reach it, and triage the rest into suppressions.

    Also in 3 projects that use this

  • MicrosoftSkill

    api-design

    Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API.

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 4 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 1

    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:

    Check hub impact: if you touched a hub file, run importer tests too

    line 14

“Common” is measured: kept by at least 6 in 10 of the 20 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-First Development with Code Intelligence

The cycle

  1. Write a failing test for the behavior you want
  2. Run the test to confirm it fails for the right reason
  3. Implement the minimum code to make it pass
  4. Run all tests (not just the new one)
  5. Check hub impact: if you touched a hub file, run importer tests too

Using codemap for test planning

  • codemap --importers <file>: which files depend on what you're testing?
  • codemap --deps .: understand the dependency chain before writing mocks
  • Working set shows what you've already touched: test those files

What to test when editing hub files

Hub files affect many dependents. Test:

  1. The hub file's own tests
  2. Direct importers' tests
  3. Integration tests that cross the hub boundary

Test file conventions

LanguageConvention
Go*_test.go in same package
TypeScript*.test.ts or *.spec.ts
Pythontest_*.py or *_test.py
Rust#[cfg(test)] module or tests/ dir

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