mirror of
https://github.com/affaan-m/ECC.git
synced 2026-08-17 21:15:40 +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
1.3 KiB
1.3 KiB
description, agent
| description | agent |
|---|---|
| Save verification state and progress checkpoint | build |
Checkpoint Command
Save current verification state and create progress checkpoint: $ARGUMENTS
Your Task
Create a snapshot of current progress including:
- Tests status - Which tests pass/fail
- Coverage - Current coverage metrics
- Build status - Build succeeds or errors
- Code changes - Summary of modifications
- Next steps - What remains to be done
Checkpoint Format
Checkpoint: [Timestamp]
Tests
- Total: X
- Passing: Y
- Failing: Z
- Coverage: XX%
Build
- Status: PASS: Passing / FAIL: Failing
- Errors: [if any]
Changes Since Last Checkpoint
git diff --stat [last-checkpoint-commit]
Completed Tasks
- Task 1
- Task 2
- Task 3 (in progress)
Blocking Issues
- [Issue description]
Next Steps
- Step 1
- Step 2
Usage with Verification Loop
Checkpoints integrate with the verification loop:
/plan → implement → /checkpoint → /verify → /checkpoint → implement → ...
Use checkpoints to:
- Save state before risky changes
- Track progress through phases
- Enable rollback if needed
- Document verification points
TIP: Create checkpoints at natural breakpoints: after each phase, before major refactoring, after fixing critical bugs.