test-first
Skill2 starsChanged 17 days agoMITView on GitHub
Use when about to fix a bug or add new logic - a function, a branch of behaviour, an input check, a calculation - before writing the implementation code. Not for configuration, documentation, layout or a prototype the user called throwaway.
24 other projects use a version of this.
Adopted by
Most recently taken up by
- TheLunchTrae/claude-code-configstheir own version, first seen Nov 8, 2026
- JordanCoin/codemaptheir own version, first seen Nov 1, 2026
- claude-world/director-mode-litetheir own version, first seen Nov 1, 2026
- NoobyGains/godmodetheir own version, first seen Nov 1, 2026
- bmtrnavsky/disciplined-vibe-codingtheir own version, first seen Nov 1, 2026
- archiforge/agent-crafttheir own version, first seen Oct 20, 2026
Used with
Projects with it also use security-sweep, refactor and 3 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.
n24q02mSkillsecurity-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
GitHubSkillrefactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Also in 4 projects that use this
MicrosoftSkillapi-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
GoogleSkillcode-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
SentrySkillskill-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
Other versions24 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 24
- JordanCoin/codemap★ 710same name
- llopresto87/Cypress★ 119same name
- NoobyGains/godmode★ 118same name
- claude-world/director-mode-lite★ 80same name
- s-hiraoku/synapse-a2a★ 17same name
- bmtrnavsky/disciplined-vibe-coding★ 15same name
- dfedoryshchev/weftworks★ 5same name
- eeshsaxena/agent-skills★ 2same name
- atgreen/hackinator★ 1same name
- DBAAZzz/skills★ 1same name
14 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 repository11 other files it gives its agents.
- clarify-taskSkill
- context-checklistSkill
- debug-root-causeSkill
- diagnose-hooksSkill
- finish-branchSkill
- implementation-pathSkill
- permission-checklistSkill
- planning-checklistSkill
- setup-agent-teamSkill
- start-branchSkill
- tool-checklistSkill
The file
Files
Тест сначала
- Красный. Один тест на одно поведение; имя называет поломку, которую он ловит.
- Проверь красный — обязательно. Запусти: тест падает на проверке и по ожидаемой причине, а не ошибкой импорта или опечаткой. Упал не так — чини тест.
- Зелёный. Минимальный код, после которого тест проходит.
- Весь набор проекта зелёный — не один свой файл.
- Рефакторинг — только при зелёных тестах.
Баг — первым делом тест, который воспроизводит его и падает на текущем коде. Исправление без такого теста не принимается.
Код уже написан до теста — не удаляй. Напиши тест, затем сломай проверяемое поведение (откати исправление): тест обязан покраснеть. Не покраснел — он ничего не проверяет. Верни код.
Хороший тест проверяет поведение, а не текст файла; настоящий код, а не мок; ожидаемое значение не вычисляется тем же кодом.
В отчёте — команда и вывод красного прогона и итог зелёного прогона всего набора.
Оправдания, которые не отменяют красный тест:
| Мысль | Как на деле |
| «Срочно, нет времени» | Красный тест — минута. Неудачная правка без теста стоит отката и второго захода |
| «Правка в одну строку, тут нечего проверять» | Однострочный баг и возвращается одной строкой — тест держит его навсегда |
| «Пользователь сказал без формальностей» | Это про длину ответа, а не про отказ от теста. Пропустить тест можно только по явной просьбе «без тестов» |
Полный текст: ${CLAUDE_PLUGIN_ROOT}/checklists/test-first.md
Если методология установлена копированием — файл лежит в checklists/test-first.md репозитория.
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.