Test first
Guides test-driven development. Use when about to write code, implement a feature, fix a bug, refactor, add an endpoint, create a component, modify business logic, or change any production code. Also use when the user says "add tests", "write tests", "test this", "cover this", "is this tested", or any variation of testing-related work. Checks if the project uses TDD before enforcing test-first. Detects the test framework automatically. Does not apply to non-code tasks like documentation or configuration.From its SKILL.md
npx -y skills add haytamAroui/AZ-CLAUDE --skill test-firstAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, as published. Nobody here has run it
Test-First
<instructions>Check before enforcing
TDD is opt-in. Check BOTH signals:
- CLAUDE.md has a TDD rule — look for "tdd", "test first", "test-first", "failing test"
- Test files exist —
*.test.*,*.spec.*,test_*.py
Both present → TDD protocol active. Either missing → suggest TDD, don't block.
TDD Protocol (when active)
- Write the failing test
- Run it — confirm it fails for the right reason
- Write minimal code to pass
- Run again — confirm green
- Refactor only after green
Framework detection
Check the project's existing framework before writing any test:
package.json→ Jest, Vitest, Mochapyproject.toml/requirements.txt→ pytestCargo.toml→ cargo testgo.mod→ go test
Use what's already there. Never introduce a new framework without asking.
</instructions>