npx skills add smithery/mattpocock --skill what-to-test
mattpocock/ai-hero-cli · Archived
what-to-test
Use when writing tests, improving coverage, or deciding what to test in this CLI
Installation
$
npx skills add mattpocock/ai-hero-cli --skill what-to-test
Stronger alternatives
This repository is archived — consider an actively maintained alternative.
what-context-needed
Similar · more installs
github/awesome-copilot
Ask Copilot what files it needs to see before answering a question
9K installs
wait-what
Similar · more installs
mattpocock/skills
Stop. That last message did not land: re-pitch it.
216K installs
what-leaked-about-you
Similar · more installs
useosint/skills
>- Check and interpret data-breach exposure for an email, username, phone or name using Have I …
57.6K installs
whatsapp-automation
Similar · more installs
claude-office-skills/skills
WhatsApp Business automation - customer support, notifications, chatbots, and broadcast messagi…
5.6K installsSimilar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
agent-browser
Same topic
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installs
azure-diagnostics
Same topic
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …
568.9K installs
azure-validate
Same topic
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure…
567.7K installs
azure-aigateway
Same topic
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
Same topic
microsoft/azure-skills
Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compar…
510K installs
supabase-postgres-best-practices
Same topic
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …
391.6K installsMore 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
Also listed on
Alternate registries and mirrors of this skill.
Repository health
Stars
110
License
LICENSE
Default branch
main
Open issues
0
Status
Archived
Skill metadata
Parsed from SKILL.md frontmatter.
Version1.0.0
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,137 B -
docs
SUMMARY.md100 B
History
- First seen on skills.sh
- First recorded snapshot · 22 installs
SKILL.md
What to Test
Philosophy
Test user-facing behavior. If a user would notice it's broken, it needs a test.
All CLI commands must be tested - including commands marked "internal". Internal commands are still user-facing (Matt uses them daily).
What Makes a Good Test
- Tests behavior users depend on
- Validates real workflows, not implementation details
- Catches regressions before users do
Do NOT write tests just to increase coverage numbers. Use coverage as a guide to find untested user-facing behavior.
What NOT to Test
Use / v8 ignore start / for:
- Integration boundaries (actual git calls, shell execution, filesystem)
- Service layers that get mocked in tests
- Entry points and DI wiring
- Boilerplate, unreachable error branches
Testing Pattern
- Export a
runX()function from command files for testability - Mock external services (GitService, PromptService)
- Test error paths users will actually hit
- Use v8 ignore for CLI formatting/presentation code