find-missing-tests
Analyze codebase and identify missing test cases, then create GitHub issues for each gap
Best use case
find-missing-tests is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Analyze codebase and identify missing test cases, then create GitHub issues for each gap
Teams using find-missing-tests should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/find-missing-tests/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How find-missing-tests Compares
| Feature / Agent | find-missing-tests | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Analyze codebase and identify missing test cases, then create GitHub issues for each gap
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Analyze codebase and identify missing test cases, then create GitHub issues for each gap: $ARGUMENTS
Follow these steps:
<!-- recall:begin -->
## Step 0: Prior-art check (RECOMMENDED)
Before identifying test gaps, recall prior learnings from the global knowledge base so we don't re-learn or re-decide something already captured:
```bash
uv run "{{HOME_TOOL_DIR}}/skills/recall/scripts/recall.py" \
"<QUERY>" \
--limit 5 --format markdown
```
**Query construction for `/find-missing-tests`**: target module/package name + `"testing"` (e.g. `"payment webhook handler testing"`).
**What to do with results:**
- If a returned learning names a constraint, anti-pattern, or prior decision directly relevant to the task — surface it to the user BEFORE proceeding with this skill's main flow.
- If nothing relevant returns — proceed silently, no need to mention the check.
- Never block on recall failure. Empty output / non-zero exit is expected when the KB is absent or the subprocess errors — treat it as "no prior art found", not as an error.
<!-- recall:end -->
1. **Analyze the codebase**:
- If $ARGUMENTS specifies files/directories, focus on those areas
- Otherwise, scan the entire codebase for test coverage gaps
- Look for functions, classes, and modules without corresponding tests
- Identify edge cases and error conditions that aren't tested
2. **Review existing test structure**:
- Understand the current testing framework and patterns
- Identify test file naming conventions
- Note any existing test utilities or helpers
- Check for integration and end-to-end test coverage
3. **Identify specific missing test cases**:
- **Unit tests**: Functions and methods without test coverage
- **Integration tests**: Component interactions not tested
- **Edge cases**: Boundary conditions, error handling, null/empty inputs
- **Regression tests**: Previously fixed bugs without test coverage
- **Performance tests**: Critical paths without performance validation
4. **Create detailed GitHub issues** for each missing test with:
- Clear title: `[TEST] Add {type} tests for {component/function}`
- Specific test cases to implement
- Expected test file location following project conventions
- Acceptance criteria defining what constitutes complete coverage
- Priority level based on code criticality
5. **Generate GitHub issues**:
- Use `gh issue create` for each identified test gap
- Add appropriate labels: `testing`, `bug`, `enhancement`
- Include code snippets showing what needs testing
- Reference related code files and line numbers
6. **Create a summary report**:
- Save findings as `test-coverage-analysis.md`
- Include overall coverage assessment
- Prioritize issues by criticality and risk
Remember: Be specific about what should be tested - don't create vague "add more tests" issues.Related Skills
workflow
Guide through structured delivery workflow with plan, implement, validate phases
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
validate
Verify implementation against specifications
ui-ux-pro-max
UI/UX design intelligence. 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, Astro, Nuxt, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Jetpack Compose). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
tui-style-guide
TUI style guide for consistent terminal interface design
token-usage
Show Claude Code token usage across sessions — daily, weekly, per-project, and per-session breakdowns. Parses {{HOME_TOOL_DIR}}/projects/**/*.jsonl for consumption data. Use when the user asks about token usage, costs, how many tokens were used, session statistics, or wants a usage report.
tmux-status
Show status of all tmux sessions including dev environments, spawned agents, and running processes
tmux-monitor
Monitor and report status of all tmux sessions including dev environments, spawned agents, and running processes. Uses tmuxwatch for enhanced visibility.
tmux-message
Reliable peer-to-peer message delivery to other Claude Code instances via tmux send-keys. Use as a fallback when claude-peers MCP send_message fails to surface in the receiver's inbox (delivered server-side but receiver never picks it up — observed behaviour). Also use when sending a directive to a known Claude Code TUI session by tmux session name or fuzzy hint, or when injecting a multi-line directive into a peer's prompt and submitting it. Trigger phrases — "claude-peers fallback", "tmux send-keys", "send to peer via tmux", "inject directive", "deliver to nanoclaw/hermes peer", "peer message". Tmux-only — won't reach peers running outside tmux.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.
test-ainb
Run tests for the ainb (agents-in-a-box) Rust workspace via a 5-layer strategy — unit, insta snapshot, mock-plugin compositing, real-plugin spawn, vhs recording. Wraps cargo + insta + vhs into one CLI. Use when Stevie says "/test-ainb", "test ainb", "run ainb tests", "snapshot <component>", "regenerate vhs tapes", or any phrasing about validating ainb test layers. The skill autodetects which ainb-tui worktree the cwd sits in and dispatches to scripts/run.sh.
sync-learnings
Sync user-level agent config changes back to toolkit repository (works for Claude, Codex, Copilot)