Write tests
Skill rogerchappel/skilldeck/fixtures/valid-pack/skills/write-tests
Local-first skill pack manager and verifier for agent instructions.
npx -y skills add rogerchappel/skilldeck --skill write-testsAssembled 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.
What its author says it does
Copied from the file, not written here
Generate focused tests for deterministic local software changes.
SKILL.md
1.1 KB, 159 tokens by cl100k_base, as published. Nobody here has run it
Write Tests
When To Use
Use this skill when a user asks for new tests, bug reproduction coverage, or fixture-backed regression checks.
Inputs
Use the target source file, existing test style, package scripts, and fixture data already present in the repo.
Side Effects
Limit edits to tests, fixtures, and tiny support helpers unless the user asks for implementation changes.
Approval
Ask before installing dependencies, changing snapshots broadly, or running commands that write outside the repository.
Examples
- Add regression tests for this parser bug.
- Cover the CLI error path with fixtures.
Validation
Add fixtures first, cover edge cases, and keep tests runnable offline. Run the narrow test command before wider validation. Verify by running the affected test command and recording the result.
Gives 0 of the 12 instructions most docs writing skills give in 159 tokens
Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-06
- announce the skill at startin 54 of 1637, across 21 files
- convert legacy doc files before editingin 45 of 1637, across 7 files
- predict questions readers might askin 42 of 1637, across 3 files
- Generate clarifying questions for initial contextin 42 of 1637, across 3 files
- Create document scaffold with placeholder textin 42 of 1637, across 3 files
- Brainstorm content options for each sectionin 42 of 1637, across 3 files
- Test document with fresh context-less instancein 42 of 1637, across 3 files
- ask interview questions one at a timein 42 of 1637, across 26 files
- include exact file paths in every taskin 42 of 1637, across 15 files
- Apply surgical edits during refinementin 41 of 1637, across 2 files
- Offer structured workflow or freeformin 40 of 1637, across 1 file
- Ask for document meta-contextin 40 of 1637, across 1 file
Said here and by no other author read
- add fixtures first
- keep tests runnable offline
- record the validation result
- limit edits to tests fixtures and helpers
- ask before installing dependencies
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.