context-log

Maintaining .opencode/context-log.md for session continuity

1.78x

Quality

55%

Does it follow best practices?

Impact

100%

1.78x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./dot_config/opencode/skill/context-log/SKILL.md

Purpose

The context log preserves incremental context across:

Long sessions (Review/QA need to understand what changed)
Compaction (history gets summarized, log persists)
Handoffs (another agent can pick up where you left off)

Location

.opencode/context-log.md in project root (created if missing)

When to Update

Event	Action
Session start	Create with issue context
After each commit	Append checkpoint
On compaction	Reference log instead of re-summarizing

Initial Template

# 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

Checkpoint Template

### [timestamp] commit-sha-short
- **Intent**: What this commit accomplishes
- **Tests**: green/red, which ones
- **Next**: What to do next

Example Checkpoint

### 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 middleware

On Compaction

Don't re-summarize. Just say:

See .opencode/context-log.md for issue context and build history.

Repository: athal7/dotfiles
Commit: 4ed3a13

Last updated: about 14 hours ago
Created: about 14 hours ago

Is this your skill?

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.