Skip to content
Skills Library
Programming · Testing

write-tests

/write-tests

Use when deciding whether to add or change software tests.

Repository
skills ↗
Licence
MIT
Last repository change
12.11.2026

Assessment and security

82/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability21 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when deciding whether to add or change software tests.

Original author description

Use when deciding whether to add or change software tests.

How it works

SKILL.md has no level-two headings · 18 lines, 324 words

SKILL.md preview
---
name: write-tests
description: "Use when deciding whether to add or change software tests."
---

# Write tests

Default to no new test. Identify the consequential runtime behavior or real regression at risk and what existing tests or automated checks already cover. Types, schemas, static analysis and stronger gates may be enough. If there is no distinct gap, verify with existing checks or a direct run instead.

A user-facing journey is the exception. A change that adds or alters one gets an end-to-end test of that journey, written as the steps a user takes and checked by what the user sees.

For each test worth adding:

1. Identify the observable behavior and a plausible defect it catches that existing checks miss. Prefer a real regression or an important boundary, failure, or state transition over speculative cases.
2. Exercise the narrowest realistic public boundary that reveals the defect. Assert outcomes a caller can observe, not private calls, mock choreography, incidental text, or implementation shape. Use real collaborators when practical; replace external or costly dependencies only as needed for reliability.
3. Add the smallest set of distinct cases covering the gap. Extend an existing test when appropriate; avoid duplicate cases, trivial getters, framework behavior, and tests that restate types or production code. Keep fixtures and setup proportionate, and avoid one-off test abstractions.
4. Run the relevant test and checks. Where practical, demonstrate that the test fails for the defect it claims to catch, then restore the correct code and confirm it passes. Otherwise explain what was verified and the limitation.

While working in a test, improve the relevant tests around it when justified: update or remove obsolete or duplicate cases, or rewrite the touched section if that produces a clearer, smaller set. Check what distinct behavior each existing test covers before changing it, and preserve coverage that still matters. Keep cleanup related to the task and verify the resulting tests; a whole-suite pruning is burn-tests, not routine cleanup.

Honor explicit requests for tests, TDD, or a regression test and project-required gates.
Files in this package (2)
  • SKILL.md 2 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · Q9Labs/skills82MIT
onsi/biloba100MIT
runwield/runwield100MIT
dzhng/jevgrep100MIT
lukedj78/dev-flow100MIT
dzhng/skills100MIT
rowansci/rowan-python100MIT
yaohuangguan/agent-playbook100MIT
microsoft/semantic-link-labs100MIT

Database snapshot: 13.11.2026 · package version ed7d04b3e697 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100v1-write-tests
    Use when writing unit tests for code changes or new functionality. Triggers on "write tests", "add tests", "test this code".
  • 84generate-tests
    Generate comprehensive tests for code. Use when user says "write tests for this function", "add unit tests to this file", "generate integration tests for the API", "I need test coverage for this module", or "create e2e tests for the checkout flow".
  • 90write-rust-tests
    Write Rust tests to verify correctness of Rust code. Use this when you want to write Rust tests.
  • 100mobiai-write-tests
    Use when the user asks to write tests for mobile code, or after applying a fix that needs regression tests.
  • 100write-skill
    Author or update compact agent skills under skills/<name>/SKILL.md. Use when asked to write, add, or change a skill; not to audit a skill library.
  • 100hollowtest
    Write tests that actually fail when the code is wrong, and never make a red test green by weakening it. Use whenever you write, change, fix, or review tests (Jest, Vitest, Mocha, node:test, Playwright, Testing Library), when asked to "add tests", "increase coverage", or "make…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.