reviewing-drift-logslisted

# Reviewing Drift Logs ## Purpose This skill covers the full lifecycle of drift-log entries after they are created: triage, OPEN → APPLIED transition, staleness review, applied-directory compaction, and promotion of a recurring insight into a standing rule. **Use this skill when:** - Triaging existing `open/` entries to decide whether to resolve, refile, or drop them - Transitioning an entry from OPEN to APPLIED after implementing its proposed change - Checking whether any `open/` entries are overdue (past their priority threshold) - Compacting the `applied/` directory once it grows large - Promoting a frequently-applied insight into a codified rule in CLAUDE.md or a skill **Do NOT use this skill for:** - Creating a new drift-log entry (use the `creating-drift-logs` skill instead) - Editing the narrative body of an existing entry (that body is immutable — see `creating-drift-logs/rules/02-immutability.md`) ## Pre-checks - Confirm `.claude/drift-log/` exists and has `open/` and `applied/` subdirectories. - List `.claude/drift-log/open/` to see current OPEN entries (each file there is an open entry). - Identify the task: transition a specific entry, triage all stale entries, compact `applied/`, or promote an insight. ## Workflow ### Path A: OPEN → APPLIED transition Run this when the proposed change in a drift entry has been implemented (or when dropping/refiling): 1. `git mv .claude/drift-log/open/<file>.md .claude/drift-log/applied/<file>.md` 2. Edit frontmatter: