Files
everything-claude-code/.opencode/commands/test-coverage.md
Affaan Mustafa 6d440c036d feat: complete OpenCode plugin support with hooks, tools, and commands
Major OpenCode integration overhaul:

- llms.txt: Comprehensive OpenCode documentation for LLMs (642 lines)
- .opencode/plugins/ecc-hooks.ts: All Claude Code hooks translated to OpenCode's plugin system
- .opencode/tools/*.ts: 3 custom tools (run-tests, check-coverage, security-audit)
- .opencode/commands/*.md: All 24 commands in OpenCode format
- .opencode/package.json: npm package structure for opencode-ecc
- .opencode/index.ts: Main plugin entry point

- Delete incorrect LIMITATIONS.md (hooks ARE supported via plugins)
- Rewrite MIGRATION.md with correct hook event mapping
- Update README.md OpenCode section to show full feature parity

OpenCode has 20+ events vs Claude Code's 3 phases:
- PreToolUse → tool.execute.before
- PostToolUse → tool.execute.after
- Stop → session.idle
- SessionStart → session.created
- SessionEnd → session.deleted
- Plus: file.edited, file.watcher.updated, permission.asked, todo.updated

- 12 agents: Full parity
- 24 commands: Full parity (+1 from original 23)
- 16 skills: Full parity
- Hooks: OpenCode has MORE (20+ events vs 3 phases)
- Custom Tools: 3 native OpenCode tools

The OpenCode configuration can now be:
1. Used directly: cd everything-claude-code && opencode
2. Installed via npm: npm install opencode-ecc
2026-02-05 05:14:33 -08:00

1.6 KiB

description, agent, subtask
description agent subtask
Analyze and improve test coverage tdd-guide true

Test Coverage Command

Analyze test coverage and identify gaps: $ARGUMENTS

Your Task

  1. Run coverage report: npm test -- --coverage
  2. Analyze results - Identify low coverage areas
  3. Prioritize gaps - Critical code first
  4. Generate missing tests - For uncovered code

Coverage Targets

Code Type Target
Standard code 80%
Financial logic 100%
Auth/security 100%
Utilities 90%
UI components 70%

Coverage Report Analysis

Summary

File           | % Stmts | % Branch | % Funcs | % Lines
---------------|---------|----------|---------|--------
All files      |   XX    |    XX    |   XX    |   XX

Low Coverage Files

[Files below target, prioritized by criticality]

Uncovered Lines

[Specific lines that need tests]

Test Generation

For each uncovered area:

[Function/Component Name]

Location: src/path/file.ts:123

Coverage Gap: [description]

Suggested Tests:

describe('functionName', () => {
  it('should [expected behavior]', () => {
    // Test code
  })

  it('should handle [edge case]', () => {
    // Edge case test
  })
})

Coverage Improvement Plan

  1. Critical (add immediately)

    • file1.ts - Auth logic
    • file2.ts - Payment handling
  2. High (add this sprint)

    • file3.ts - Core business logic
  3. Medium (add when touching file)

    • file4.ts - Utilities

IMPORTANT: Coverage is a metric, not a goal. Focus on meaningful tests, not just hitting numbers.