Files
everything-claude-code/commands/test-coverage.md
Affaan Mustafa 45959c326e Initial release: Complete Claude Code configuration collection
Battle-tested configs from 10+ months of daily Claude Code usage.
Won Anthropic x Forum Ventures hackathon building zenith.chat.

Includes:
- 9 specialized agents (planner, architect, tdd-guide, code-reviewer, etc.)
- 9 slash commands (tdd, plan, e2e, code-review, etc.)
- 8 rule files (security, coding-style, testing, git-workflow, etc.)
- 7 skills (coding-standards, backend-patterns, frontend-patterns, etc.)
- Hooks configuration (PreToolUse, PostToolUse, Stop)
- MCP server configurations (15 servers)
- Plugin/marketplace documentation
- Example configs (project CLAUDE.md, user CLAUDE.md, statusline)

Read the full guide: https://x.com/affaanmustafa/status/2012378465664745795
2026-01-17 17:49:33 -08:00

663 B

Test Coverage

Analyze test coverage and generate missing tests:

  1. Run tests with coverage: npm test --coverage or pnpm test --coverage

  2. Analyze coverage report (coverage/coverage-summary.json)

  3. Identify files below 80% coverage threshold

  4. For each under-covered file:

    • Analyze untested code paths
    • Generate unit tests for functions
    • Generate integration tests for APIs
    • Generate E2E tests for critical flows
  5. Verify new tests pass

  6. Show before/after coverage metrics

  7. Ensure project reaches 80%+ overall coverage

Focus on:

  • Happy path scenarios
  • Error handling
  • Edge cases (null, undefined, empty)
  • Boundary conditions