Tdd sentinel
Forge portable coding-agent skills with linting, activation tests, render adapters, and local-first packaging.From the repository description
npx -y skills add rogerchappel/skillforge --skill tdd-sentinelAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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
0.7 KB, 149 tokens by cl100k_base, as published. Nobody here has run it
TDD Sentinel
When to use
Use this when a task benefits from a test-first loop: parsers, bug fixes, behavior changes, and regressions that should stay fixed.
Workflow
- Name the behavior that should change.
- Add or update the smallest failing test or fixture.
- Run that focused test and confirm it fails for the expected reason.
- Implement the smallest change that makes it pass.
- Run the focused test, then the relevant broader check.
- Summarize the behavior, verification, and any tradeoff.
Safety
- Ask before external writes such as publishing, deployment, or messages.
- Do not hide failing tests; report them as blockers with the smallest reproduction.
What ships with it: 2 files
1.2 KB alongside SKILL.md
fixtures/
- activation.json422 B
- skill.yaml839 B
Gives 0 of the 12 instructions most tdd skills give in 149 tokens
Counted across 439 of the 443 authors here whose files we hold, read 2026-08-07
- Write minimal code to pass the testin 304 of 439, across 222 files
- Write a failing test firstin 174 of 439, across 111 files
- Refactor code only after tests passin 172 of 439, across 102 files
- Watch the test fail before writing codein 145 of 439, across 97 files
- Test one behavior per testin 108 of 439, across 46 files
- Refactor code while keeping tests greenin 100 of 439, across 88 files
- Delete code written before testsin 99 of 439, across 55 files
- Run tests after each refactor stepin 88 of 439, across 57 files
- Confirm the test fails for the right reasonin 66 of 439, across 62 files
- Use real code instead of mocks unless unavoidablein 60 of 439, across 17 files
- Reproduce bugs with a test before fixingin 53 of 439, across 36 files
- Write tests before implementationin 51 of 439, across 43 files
Said here and by no other author read
- name the behavior that should change
- add or update the smallest failing test
- run the focused test then broader checks
- ask before external writes
- summarize the behavior and verification
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.