Generating Unit Tests

What it does

When your agent uses it

• Creating test coverage for functions
• With phrases like generate unit tests
• Create tests for
• Add test coverage

Example prompts

• “generate unit tests”
• “create tests for”
• “add test coverage”
• “/generating-unit-tests”

Requirements

• Python 3
• Compatibility (from SKILL.md): Designed for Claude Code
• Pre-approved tools (allowed-tools): Read, Write, Edit, Grep, Glob, Bash(test:unit-*)

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

1. 1Scan the codebase with Glob to locate source files that lack corresponding test files (e.g., src/utils/parser.ts without…
2. 2Read each untested source file and extract
3. 3For each function, generate test cases in these categories
4. 4Create mock declarations for all external dependencies
5. 5Write the test file following project conventions
6. 6Run the generated tests to verify they pass, then check coverage to confirm the target function is fully exercised.
7. 7Report coverage gaps and suggest additional test cases for uncovered branches.

What it can do on your machine

Read from SKILL.md and the folder at commit 80f86df. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Read
  • Write
  • Edit
  • Grep
  • Glob
  • Bash(test:unit-*)

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Ships 1 file in scripts/, which the agent can run.

  Shell commands in SKILL.md call:

  • npm
  • go

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Links to these hosts (documentation or services it may open):

  • jestjs.io
  • vitest.dev
  • docs.pytest.org
  • junit.org
  • pkg.go.dev

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

• Compatibility

  Designed for Claude Code

  From compatibility in the SKILL.md frontmatter.

Context cost

Generating Unit Tests loads about 1.4k tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 77 tokens; SKILL.md has 491 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~77

When it runs · the whole SKILL.md, loaded when a task matches

~1.4k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit 80f86df, republished under its MIT licence (© jeremylongshore). 491 words, ~1,428 tokens.

name

generating-unit-tests

description

Test automatically generate comprehensive unit tests from source code covering happy paths, edge cases, and error conditions. Use when creating test coverage for functions, classes, or modules. Trigger with phrases like "generate unit tests", "create tests for", or "add test coverage".

allowed-tools

Read, Write, Edit, Grep, Glob, Bash(test:unit-*)

compatibility

Designed for Claude Code

version

1.21.0

author

Jeremy Longshore <jeremy@intentsolutions.io>

license

MIT

tags

testing, unit-tests

import { slugify } from '../src/utils/slugify';

describe('slugify', () => {
  it('converts spaces to hyphens', () => {
    expect(slugify('hello world')).toBe('hello-world');
  });
  it('lowercases all characters', () => {
    expect(slugify('Hello World')).toBe('hello-world');
  });
  it('removes special characters', () => {
    expect(slugify('hello@world!')).toBe('helloworld');
  });
  it('handles empty string', () => {
    expect(slugify('')).toBe('');
  });
  it('trims leading and trailing whitespace', () => {
    expect(slugify('  spaced  ')).toBe('spaced');
  });
});

import pytest
from myapp.validators import validate_email

class TestValidateEmail:
    def test_accepts_valid_email(self):
        assert validate_email("user@example.com") is True

    def test_rejects_missing_at_sign(self):
        assert validate_email("userexample.com") is False

    def test_rejects_empty_string(self):
        assert validate_email("") is False

    def test_rejects_none(self):
        with pytest.raises(TypeError):
            validate_email(None)

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references, assets) in skills/.curated/generating-unit-tests of jeremylongshore/tons-of-skills-marketplace.

• SKILL.md
• assets/README.md
• references/README.md
• scripts/README.md

Open the folder on GitHubat commit 80f86df