mirror of https://github.com/affaan-m/ECC.git synced 2026-08-17 21:15:40 +02:00

Files

T

Gaurav Dubey 9d1ecb0754 fix(opencode): resolve command agent ids to registered opencode agents (#2477 )

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

2026-07-10 09:46:40 +05:30

1.1 KiB

Raw Permalink Blame History

description, agent, subtask

description	agent	subtask
Create implementation plan with risk assessment	planner	true

Plan Command

Create a detailed implementation plan for: $ARGUMENTS

Your Task

Restate Requirements - Clarify what needs to be built
Identify Risks - Surface potential issues, blockers, and dependencies
Create Step Plan - Break down implementation into phases
Wait for Confirmation - MUST receive user approval before proceeding

Output Format

Requirements Restatement

[Clear, concise restatement of what will be built]

Implementation Phases

[Phase 1: Description]

Step 1.1
Step 1.2 ...

[Phase 2: Description]

Step 2.1
Step 2.2 ...

Dependencies

[List external dependencies, APIs, services needed]

Risks

HIGH: [Critical risks that could block implementation]
MEDIUM: [Moderate risks to address]
LOW: [Minor concerns]

Estimated Complexity

[HIGH/MEDIUM/LOW with time estimates]

WAITING FOR CONFIRMATION: Proceed with this plan? (yes/no/modify)

CRITICAL: Do NOT write any code until the user explicitly confirms with "yes", "proceed", or similar affirmative response.

1.1 KiB Raw Permalink Blame History