mirror of
https://github.com/affaan-m/ECC.git
synced 2026-08-20 14:32:24 +02:00
Gaurav Dubey
9d1ecb0754
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
68 lines
1.3 KiB
Markdown
68 lines
1.3 KiB
Markdown
---
|
|
description: Update documentation for recent changes
|
|
agent: doc-updater
|
|
subtask: true
|
|
---
|
|
|
|
# Update Docs Command
|
|
|
|
Update documentation to reflect recent changes: $ARGUMENTS
|
|
|
|
## Your Task
|
|
|
|
1. **Identify changed code** - `git diff --name-only`
|
|
2. **Find related docs** - README, API docs, guides
|
|
3. **Update documentation** - Keep in sync with code
|
|
4. **Verify accuracy** - Docs match implementation
|
|
|
|
## Documentation Types
|
|
|
|
### README.md
|
|
- Installation instructions
|
|
- Quick start guide
|
|
- Feature overview
|
|
- Configuration options
|
|
|
|
### API Documentation
|
|
- Endpoint descriptions
|
|
- Request/response formats
|
|
- Authentication details
|
|
- Error codes
|
|
|
|
### Code Comments
|
|
- JSDoc for public APIs
|
|
- Complex logic explanations
|
|
- TODO/FIXME cleanup
|
|
|
|
### Guides
|
|
- How-to tutorials
|
|
- Architecture decisions (ADRs)
|
|
- Troubleshooting guides
|
|
|
|
## Update Checklist
|
|
|
|
- [ ] README reflects current features
|
|
- [ ] API docs match endpoints
|
|
- [ ] JSDoc updated for changed functions
|
|
- [ ] Examples are working
|
|
- [ ] Links are valid
|
|
- [ ] Version numbers updated
|
|
|
|
## Documentation Quality
|
|
|
|
### Good Documentation
|
|
- Accurate and up-to-date
|
|
- Clear and concise
|
|
- Has working examples
|
|
- Covers edge cases
|
|
|
|
### Avoid
|
|
- Outdated information
|
|
- Missing parameters
|
|
- Broken examples
|
|
- Ambiguous language
|
|
|
|
---
|
|
|
|
**IMPORTANT**: Documentation should be updated alongside code changes, not as an afterthought.
|