What To Test
- 17 installs
- 81 repo stars
- Updated July 21, 2026
- mattpocock/ai-hero-cli
Decide what to test in the ai-hero CLI and how to structure tests without chasing coverage for its own sake.
About
What-to-test is a Testing & QA agent skill for solo builders shipping the ai-hero CLI. It encodes a behavior-first testing philosophy: if a user would notice something broken, it deserves a test, and all commands count as user-facing even when labeled internal. The skill steers agents away from testing implementation details or integration boundaries that belong behind mocks, and documents when to use v8 ignore for git, shell, filesystem, and presentation code. You install it when writing new tests, improving coverage gaps, or reviewing whether existing tests actually protect workflows. The exported runX() convention pairs with mocked external services so error paths users hit stay covered without brittle end-to-end git calls. It matters because small CLI teams ship fast and regressions in daily commands erode trust faster than a low coverage badge.
- Tests user-facing behavior—including every CLI command, including internal ones Matt uses daily
- Four-step pattern: export runX(), mock GitService/PromptService, hit real user error paths, v8 ignore presentation wirin
- Explicit do-not-test list: real git/shell/fs boundaries, mocked service layers, DI entry points, boilerplate branches
- Coverage is a guide to find untested user-facing behavior—not a goal to inflate numbers
What To Test by the numbers
- 17 all-time installs (skills.sh)
- Ranked #1,467 of 2,184 Testing & QA skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 26, 2026 (Skillselion catalog sync)
npx skills add https://github.com/mattpocock/ai-hero-cli --skill what-to-testAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 17 |
|---|---|
| repo stars | ★ 81 |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 21, 2026 |
| Repository | mattpocock/ai-hero-cli ↗ |
What it does
Decide what to test in the ai-hero CLI and how to structure tests without chasing coverage for its own sake.
Files
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
1. Export a runX() function from command files for testability 2. Mock external services (GitService, PromptService) 3. Test error paths users will actually hit 4. Use v8 ignore for CLI formatting/presentation code
Related skills
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.510k185k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.176k260kQaRun conversational QA sessions that turn user-reported bugs into well-written, domain-aware GitHub issues without manual ticket writing.164k185kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.151k185k
Webapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.121k164k
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.96.3k12.2kFAQ
Is What To Test safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.