spec-loop-write-readable-tests
Plan test coverage and choose behavioral names when designing, writing, changing, or reviewing automated tests. Use for naming alone, even before implementation, and for drafting or revising a Spec Loop Test specification. Keep each test's setup, action, and expected result easy to see. General testing guidance works with or without Spec Loop.
76%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/spec-loop-write-readable-tests/SKILL.mdWrite readable tests
Follow approved scope and project rules. This skill does not grant editing permission or change workflow routes, phases, or approvals.
Required guidance
Read each applicable reference fully:
- test-design-and-writing.md: when planning test coverage or designing, naming, identifying, writing, changing, or reviewing automated tests. It defines coverage, case purposes, names and identities, and readable test bodies. It works with or without Spec Loop.
- spec-loop-task-verification.md:
when drafting, revising, or reconstructing a Spec Loop
Test specification. It defines only task-recording and readiness rules. Do not load it for standalone test work.
Return to the invoking workflow afterward. Its scope, phase, approval, and completion rules still apply.
- Repository
dpolivaev/spec-loop
- Revision
b41398f
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.