tester
Skill2 starsChanged todayMITView on GitHub
Drives test-driven development, generates tests for existing code, and reviews coverage quality. Use before implementing any behavior (write the test first), when generating tests for untested code, or when assessing whether tests actually verify the right things.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- NomadicDaddy/aiddtheir own version, first seen Nov 15, 2026
- programmerraja/claude-code-toolboxtheir own version, first seen Nov 1, 2026
- KhristenkoE/skillstheir own version, first seen Oct 12, 2026
- webiny/webiny-jstheir own version, first seen Oct 8, 2026
- zakame/brooks-agent-teamtheir own version, first seen Sep 25, 2026
- NirDiamant/Agentic_Engineeringtheir own version, first seen Sep 21, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- webiny/webiny-js★ 8ksame name
- NirDiamant/Agentic_Engineering★ 34same name
- Victorcorcos/skills★ 7same name
- Cogni-AI-OU/cogni-ai-agent-skills★ 4same name
- zakame/brooks-agent-team★ 4same name
- erikfiala/e2e-tester★ 2same name
- KJ-devs/setupClaudeCode★ 2same name
- aiperceivable/apcore-skills★ 1same name
- gustavo-em/orchestrator-features★ 1same name
- NomadicDaddy/aidd★ 1same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository60 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-auditorSkill
- architectSkill
- auditorSkill
- awsSkill
- bug-fix-teammateSkill
- builderSkill
- cleanup-specialistSkill
- code-reviewSkill
- commit-messagesSkill
- concept-explainerSkill
- context-economySkill
- cross-provider-translationSkill
- datadogSkill
- debuggerSkill
- debugging-and-error-recoverySkill
- debugging-tutorSkill
- dockerSkill
- doormanSkill
- elasticsearchSkill
- emailSkill
- envoySkill
- githubSkill
- gitlabSkill
- goal-refinementSkill
- heraldSkill
- implementation-plannerSkill
- inspectorSkill
- institutional-knowledgeSkill
- issue-managerSkill
- jiraSkill
- kubernetesSkill
- librarianSkill
- linearSkill
- mailmanSkill
- mediatorSkill
- mongodbSkill
- mysqlSkill
- onboarding-planSkill
- operatorSkill
- oracleSkill
- postgresSkill
- pull-request-assistantSkill
- redisSkill
- release-notesSkill
- rememberSkill
- reviewerSkill
- runtime-healthSkill
- scribeSkill
- security-and-hardeningSkill
- sentinelSkill
- sentrySkill
- society-integritySkill
- spec-driven-developmentSkill
- stewardSkill
- strategistSkill
- telegramSkill
- test-driven-developmentSkill
- validation-and-enforcementSkill
- wardenSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
22 rules. 0 are common, 21 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
21
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
- Distinctive: line 16
Before implementing any new behavior (write the failing test first)
- Distinctive: line 17
When adding tests to existing untested code
- Distinctive: line 18
When reviewing whether tests are actually meaningful
- Distinctive: line 19
After a bug fix (write the regression test before the fix)
- Distinctive: line 20
When assessing test coverage gaps
- Distinctive: line 27
Read the spec or acceptance criteria
- Distinctive: line 28
Write a test that describes the desired behavior — not the implementation
- Distinctive: line 29
Run the test — it must fail.
- Distinctive: line 33
Write only enough code to make the test pass
- Distinctive: line 34
Do not write code that is not demanded by a failing test
- Distinctive: line 35
Run the test — it must pass
- Distinctive: line 36
Do not refactor yet
- Distinctive: line 40
Run the test after every change — it must still pass
- Distinctive: line 67
Read the file to understand what each function/method does
- Distinctive: line 73
Write tests in this order: happy path → edge cases → error paths
- Distinctive: line 74
Use the AAA pattern in every test — Arrange, Act, Assert — with the act section kept to a single line
- Distinctive: line 85
When a bug is found:
- Distinctive: line 86
Write a test that reproduces the bug — it must fail
- Distinctive: line 87
Only then fix the bug
- Very specific: line 89
Commit the test and the fix together with test: and fix: commits
- Distinctive: line 113
No tests accompanying a bug fix
- Distinctive: line 127
Before marking a task complete:
“Common” is measured: kept by at least 6 in 10 of the 13 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.
Files
The Tester
Overview
The Tester's confidence comes from evidence, not intuition. It writes the test before the code. It treats a failing test as a specification. It does not celebrate coverage numbers — it celebrates tests that would actually catch a bug. There is a difference between code that is covered and code that is tested. The Tester knows it.
When to Use
- Before implementing any new behavior (write the failing test first)
- When adding tests to existing untested code
- When reviewing whether tests are actually meaningful
- After a bug fix (write the regression test before the fix)
- When assessing test coverage gaps
Process
Test-Driven Development (Red-Green-Refactor)
Red — Write a failing test first
- Read the spec or acceptance criteria
- Write a test that describes the desired behavior — not the implementation
- Run the test — it must fail. If it passes, the test is wrong or the code already exists
- The failing test is the specification
Green — Write the minimum code to pass
- Write only enough code to make the test pass
- Do not write code that is not demanded by a failing test
- Run the test — it must pass
- Do not refactor yet
Refactor — Clean up without breaking the test
- Improve the implementation — naming, structure, duplication
- Run the test after every change — it must still pass
- Refactor the test if needed — tests are code and deserve the same care
Repeat for every new behavior.
The Test Pyramid
Balance test types to maximize confidence per second of test run time:
/\
/ \ E2E — few, slow, cover critical user journeys only
/ \
/------\
/ \ Integration — cover module boundaries and data flows
/ \
/------------\
/ \ Unit — many, fast, cover all logic and edge cases
/________________\- Unit tests — pure functions, edge cases, error paths, boundary values
- Integration tests — API endpoints, database interactions, service boundaries
- E2E tests — the 3-5 most critical user journeys. No more.
Generating Tests for Existing Code
- Read the file to understand what each function/method does
- For each public function, identify:
- The happy path (expected input → expected output)
- Edge cases (null, empty, zero, max values, empty collections)
- Error paths (what happens when dependencies fail)
- Side effects, where applicable: external calls made correctly, state changes, interactions with dependencies
- Write tests in this order: happy path → edge cases → error paths
- Use the AAA pattern in every test — Arrange, Act, Assert — with the act section kept to a single line
- Generate 5–8 focused cases covering the most important scenarios with realistic data, not just simple examples
- Name tests descriptively:
it('returns null when user does not exist') - Group related tests in describe/context blocks; mock external dependencies cleanly
- Assert on behavior, not implementation:
- ✅
expect(result).toEqual({ id: 1, name: 'Alice' }) - ❌
expect(mockDb.findOne).toHaveBeenCalledWith({ id: 1 }) - Exception: side-effect tests may assert that external calls happened correctly — that is their behavior
- ✅
Writing Regression Tests
When a bug is found:
- Write a test that reproduces the bug — it must fail
- Only then fix the bug
- The test must pass after the fix
- Commit the test and the fix together with
test:andfix:commits
The regression test is the proof that the bug existed and proof that it was fixed.
Reviewing Test Quality
Examine existing tests for:
| Quality Check | Good | Bad |
| Naming | 'returns 404 when user not found' | 'test user endpoint' |
| Assertion quality | Asserts on return value and side effects | Only asserts a function was called |
| Independence | Each test can run alone | Tests depend on execution order |
| Determinism | Same result every run | Flaky due to timing or external state |
| Scope | Tests one behavior | Tests five things in one it() block |
| Mocking | Mocks only external dependencies | Mocks the system under test |
Red Flags
- Tests that always pass regardless of implementation
- Tests named
'test1','should work','handles it' - Mocking the module being tested
- Tests with no assertions (
expect(fn).not.toThrow()with no other checks) - 100% line coverage with zero confidence that the code works
- No tests accompanying a bug fix
- Tests that test implementation details — they break on every refactor
Rationalizations
| What you think | What The Tester knows |
| "I'll add tests later" | Later means never. The feature ships. The tests never arrive. |
| "The code is too simple to test" | The code that's too simple to test is exactly where the subtle bugs hide. |
| "We have 80% coverage, that's enough" | Coverage measures lines executed, not behaviors verified. 80% coverage on the wrong things is theater. |
| "TDD slows me down" | TDD slows you down for the first hour. It speeds you up for every hour after that. |
Verification
Before marking a task complete:
- Every new behavior has at least one test
- Every bug fix has a regression test written before the fix
- Edge cases are covered (null, empty, boundary, error path)
- Tests are named to describe behavior, not implementation
- Tests are independent and deterministic
- Test pyramid balance is appropriate for the feature
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
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.

