Menu
Review whether current changes follow the worklog-driven development rules. Use before commits or when checking worklog structure.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Apply C# nullable analysis attributes from System.Diagnostics.CodeAnalysis when `?`, non-nullable declarations, and ordinary flow analysis are not enough. Use for Try-patterns, guard helpers, late initialization, member null-state guarantees, generic nullability, and compiler flow hints around nullable warnings.
Create, edit, review, or polish README.md and README-like Markdown fragments in a calm, concrete, non-marketing engineering style close to the repository author's voice. Use for README.md, README*.md, README sections in Markdown files, and short documentation fragments intended to be copied into README.
Import existing specs/docs/planning documents from an explicitly provided SOURCE_FOLDER into .worklog. Use only when invoked manually by the user as /worklog-import SOURCE_FOLDER. SOURCE_FOLDER is required; if it is missing, ask for it and do not inspect or move source files.
Rebuild or update `.worklog/INDEX.md` from current worklog documents. Use after creating, archiving, replacing, importing, or reconciling worklog documents.
Compare an existing work document with the actual implementation, git diff, and recent commits. Use after significant implementation or investigation to decide whether an Outcome section, a follow-up work document, or no worklog update is needed.
Create the next numbered work document before significant implementation work. Use when starting a feature, user-visible behavior change, architecture decision, or spike.
| name | worklog-review |
| description | Review whether current changes follow the worklog-driven development rules. Use before commits or when checking worklog structure. |
Read:
docs/worklog-method.md.worklog/AGENTS.mdCLAUDE.md if presentCheck:
spec, adr, or spike?.worklog/ and .worklog/archive/?.worklog/?.worklog/archive/?.worklog/INDEX.md exist and reflect the current numbered documents?Outcome exists, does it add durable engineering context instead of task status?Result and Recommendation present and meaningful?Replaces or explicitly needed for history?.worklog/archive/ and the new current document given Replaces:?.worklog/ and left to commit messages?Legacy migration check:
Flag files matching:
.worklog/*.active.md.worklog/*.retired.md.worklog/archive/*.active.md.worklog/archive/*.retired.mdThese should be renamed to the new lifecycle-free format.
Output:
OK if the structure is fine.