Use when adding a new feature or changing existing behavior in a codebase. Read OKF before implementation and prefer the smallest coherent change. Do not use for pure bug triage, test-only work, or behavior-preserving refactors.
Use after implementation changes to update OKF from git diff or changed files. Extract durable behavior, architecture, domain, data, and playbook changes into relevant OKF documents and log entries. Do not use for temporary task notes or changes with no durable project knowledge impact.
Use when adding or improving tests for existing behavior, regressions, edge cases, or coverage gaps. Follow existing test style and cover normal, error, and boundary cases where relevant. Do not use when behavior is undefined or implementation must change first.
Use when a defect, regression, failing test, incident, or unclear failure needs investigation. Reproduce and analyze before fixing. Do not use when the exact root cause and approved fix are already known.
Use when improving internal structure, readability, duplication, or maintainability without changing behavior. Keep diffs small and preserve public APIs, schemas, and user-visible behavior. Do not use when behavior, contracts, or migrations must change.
★not rated 2 14d agoA52 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: