Skip to content
Skills Library
Programming · Testing

write-tests

/write-tests

Use when the user asks to write, add or extend tests for some code (unit tests, regression test for a bug, coverage of a new feature).

Repository
Maxedcode ↗
Licence
Apache-2.0
Last repository change
12.11.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 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
1
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

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use when the user asks to write, add or extend tests for some code (unit tests, regression test for a bug, coverage of a new feature).

Original author description

Use when the user asks to write, add or extend tests for some code (unit tests, regression test for a bug, coverage of a new feature).

How it works

SKILL.md has no level-two headings · 21 lines, 218 words

SKILL.md preview
---
name: write-tests
description: Use when the user asks to write, add or extend tests for some code (unit tests, regression test for a bug, coverage of a new feature).
---
# Write tests

What to test: $ARGUMENTS

1. Find how the project tests: existing test folders (`tests/`, `test_*.py`, `*_test.py`, `*.spec.ts`),
   the runner (pytest/unittest config, run_all_tests.py, package.json scripts, Makefile). Read one existing
   test file near the target and copy its style: framework, fixtures, naming, imports, helpers.
   No tests yet: Python - unittest or pytest (whichever is installed), one `tests/test_<module>.py`.
2. Read the code under test. List the cases before writing:
   - the normal path with typical input;
   - edges: empty, None, zero, one item, very large, unicode/Cyrillic, Windows paths with spaces;
   - error paths: invalid input must raise or return the documented error;
   - for a bug: a test that fails on the old code and passes on the fixed code.
3. Write focused tests: one behaviour per test, clear names (`test_<what>_<when>`), exact assertions on
   values, not just "no exception". Mock only external things (network, model API, clock, subprocess);
   use temp dirs for files. No sleeps, no dependence on test order or on the user's machine state.
4. Run only the new tests, then the whole related suite. A new test that fails exposes either a test
   mistake (fix the test) or a real bug (report it, do not change the code under test unless asked).

Report: the test file(s), the cases covered, the run command and its result.

Versions

RepositoryScoreLicence
This page · maxed4you/Maxedcode86Apache-2.0
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 2e19f1c3d813 (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".
  • 100test-unit
    Write unit and integration tests for a named module or change. Use when "write unit tests" or "add tests for this function". Coverage plan → plan-test-coverage. Mutation score → test-mutation. Browser check → test-playwright.
  • 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".
  • 100unit-testing
    Writes and updates unit tests for new or changed code in the project's existing framework and style, covering happy, error and boundary paths, then runs them with coverage and fixes failures. Use when implementing a feature or bug fix that needs tests, when asked to add or…
  • 100unit-tests
    Write or review unit tests through exported behavior. Use for new tests, bug-fix regression tests, coverage, replacing brittle implementation checks, or a test that went red because behaviour changed on purpose.
  • 100playwright-test-writer
    Write or extend Playwright end-to-end tests for a web page or feature. Use when the user asks to add, write, improve or fix Playwright, e2e or browser tests.

Feedback and reports

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