Files
ECC/.opencode/commands/learn.md
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

62 lines
1.3 KiB
Markdown

---
description: Extract patterns and learnings from current session
agent: build
---
# Learn Command
Extract patterns, learnings, and reusable insights from the current session: $ARGUMENTS
## Your Task
Analyze the conversation and code changes to extract:
1. **Patterns discovered** - Recurring solutions or approaches
2. **Best practices applied** - Techniques that worked well
3. **Mistakes to avoid** - Issues encountered and solutions
4. **Reusable snippets** - Code patterns worth saving
## Output Format
### Patterns Discovered
**Pattern: [Name]**
- Context: When to use this pattern
- Implementation: How to apply it
- Example: Code snippet
### Best Practices Applied
1. [Practice name]
- Why it works
- When to apply
### Mistakes to Avoid
1. [Mistake description]
- What went wrong
- How to prevent it
### Suggested Skill Updates
If patterns are significant, suggest updates to:
- `skills/coding-standards/SKILL.md`
- `skills/[domain]/SKILL.md`
- `rules/[category].md`
## Instinct Format (for continuous-learning-v2)
```json
{
"trigger": "[situation that triggers this learning]",
"action": "[what to do]",
"confidence": 0.7,
"source": "session-extraction",
"timestamp": "[ISO timestamp]"
}
```
---
**TIP**: Run `/learn` periodically during long sessions to capture insights before context compaction.