SkillsAdd

smithery/pevans

Write unit tests

Enable an agent to write unit tests

Installation

$ npx skills add smithery/pevans --skill write-unit-tests
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
azure-aigateway Shared topics
microsoft/azure-skills

Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: sem…

566.3K installs
azure-compute Shared topics
microsoft/azure-skills

Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compar…

510K installs
supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
prisma-cli Shared topics
prisma/skills

Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, complete, studio, …

267K installs
supabase Shared topics
supabase/agent-skills

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge F…

263K installs

Also in this package

Other skills from smithery/pevans.

npx skills add smithery/pevans
Debug a disk problem 0

Browse all from smithery/pevans

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 660 B
  • docs SUMMARY.md 59 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Write unit tests

Best practices

  • Unit tests should go into tests named for the functions being tested.

- If you have a function Foo, you should have a test function named TestFoo. - Methods with receivers should include the name of the receiver's type. A method like func (f *Foo) Bar() {...} should have a test named TestFooBar.

  • Tests should only test the behavior of the function. Don't exhaustively test

every possible input.

  • Each behavior you test should have a test case. If you have more than two

test cases, use table-driven tests.