mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-02-08 07:33:08 +08:00
Major OpenCode integration overhaul: - llms.txt: Comprehensive OpenCode documentation for LLMs (642 lines) - .opencode/plugins/ecc-hooks.ts: All Claude Code hooks translated to OpenCode's plugin system - .opencode/tools/*.ts: 3 custom tools (run-tests, check-coverage, security-audit) - .opencode/commands/*.md: All 24 commands in OpenCode format - .opencode/package.json: npm package structure for opencode-ecc - .opencode/index.ts: Main plugin entry point - Delete incorrect LIMITATIONS.md (hooks ARE supported via plugins) - Rewrite MIGRATION.md with correct hook event mapping - Update README.md OpenCode section to show full feature parity OpenCode has 20+ events vs Claude Code's 3 phases: - PreToolUse → tool.execute.before - PostToolUse → tool.execute.after - Stop → session.idle - SessionStart → session.created - SessionEnd → session.deleted - Plus: file.edited, file.watcher.updated, permission.asked, todo.updated - 12 agents: Full parity - 24 commands: Full parity (+1 from original 23) - 16 skills: Full parity - Hooks: OpenCode has MORE (20+ events vs 3 phases) - Custom Tools: 3 native OpenCode tools The OpenCode configuration can now be: 1. Used directly: cd everything-claude-code && opencode 2. Installed via npm: npm install opencode-ecc
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.