mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-02-08 07:33:08 +08:00
6d440c036d
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
| 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: ✅ Passing / ❌ 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.