Maintaining .opencode/context-log.md for session continuity
72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
The context log preserves incremental context across:
.opencode/context-log.md in project root (created if missing)
| Event | Action |
|---|---|
| Session start | Create with issue context |
| After each commit | Append checkpoint |
| On compaction | Reference log instead of re-summarizing |
# Context Log
## Issue
- **Key**: PROJ-123
- **Title**: Add password reset flow
- **Acceptance Criteria**:
- User can request reset via email
- Token expires after 24h
- Rate limited to 3 requests/hour
## Checkpoints### [timestamp] commit-sha-short
- **Intent**: What this commit accomplishes
- **Tests**: green/red, which ones
- **Next**: What to do next### 2024-01-15 14:30 abc1234
- **Intent**: Add token generation and email service
- **Tests**: green (token_test.rb), red (rate_limit_test.rb - not implemented yet)
- **Next**: Implement rate limiting middlewareDon't re-summarize. Just say:
See
.opencode/context-log.mdfor issue context and build history.
31daf20
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.