mirror of
https://github.com/affaan-m/ECC.git
synced 2026-08-20 06:25:43 +02:00
The `.opencode/commands/*.md` frontmatter referenced agents with the Claude Code plugin namespace (`agent: everything-claude-code:<name>`), but ECC's opencode integration registers its agents unscoped in `opencode.json`'s `agent` map (`code-reviewer`, `planner`, ...), and that file's own `command` section already references them unscoped. The `everything-claude-code:` scope resolves under no opencode config (the opencode plugin package is `ecc-universal`, and inline-config agents are bare), so subtask commands like `/code-review` hard-fail with `Agent not found: everything-claude-code:code-reviewer`. Non-subtask commands fall back to the default agent and appear to work — which is why only some commands failed. Strip the `everything-claude-code:` prefix from all 30 command frontmatter agent ids so they match the registered agents, fix the MIGRATION.md example, and replace the test that enforced the broken scoped invariant with one that asserts each command agent id is a registered opencode agent (fails on the old scoped ids, passes on the fix). Fixes #2477
1.3 KiB
1.3 KiB
description, agent, subtask
| description | agent | subtask |
|---|---|---|
| Update codemaps for codebase navigation | doc-updater | true |
Update Codemaps Command
Update codemaps to reflect current codebase structure: $ARGUMENTS
Your Task
Generate or update codemaps in docs/CODEMAPS/ directory:
- Analyze codebase structure
- Generate component maps
- Document relationships
- Update navigation guides
Codemap Types
Architecture Map
docs/CODEMAPS/ARCHITECTURE.md
- High-level system overview
- Component relationships
- Data flow diagrams
Module Map
docs/CODEMAPS/MODULES.md
- Module descriptions
- Public APIs
- Dependencies
File Map
docs/CODEMAPS/FILES.md
- Directory structure
- File purposes
- Key files
Codemap Format
[Module Name]
Purpose: [Brief description]
Location: src/[path]/
Key Files:
file1.ts- [purpose]file2.ts- [purpose]
Dependencies:
- [Module A]
- [Module B]
Exports:
functionName()- [description]ClassName- [description]
Usage Example:
import { functionName } from '@/module'
Generation Process
- Scan directory structure
- Parse imports/exports
- Build dependency graph
- Generate markdown maps
- Validate links
TIP: Keep codemaps updated when adding new modules or significant refactoring.