thread-keep

Create evidence-backed pending Thread Keep context notes with stable rationale and references for changed Go entities. Use when a code change needs an intent, decision, constraint, example, or warning recorded without source annotations, or when existing committed context needs a successor revision before a human explicitly commits the context change.

Review code changes against active Thread Keep intent, decisions, constraints, examples, and warnings. Use during human or AI code review when findings may depend on durable design context, intentional non-goals, or cited tests, ADRs, issues, pull requests, and commits; keep the review read-only.