Worklog Review
- 1 installs
- Updated June 4, 2026
- dimonsmart/aitexteditor
Reviews whether current changes follow the project's worklog-driven development rules, checking work-document type, numbering, index and archive placement.
About
Reads the worklog method, current diff and work documents to verify the change follows worklog rules for spec/adr/spike type, numbering, INDEX.md and archiving. A developer uses it before a commit to check worklog structure and get concrete fixes.
- Checks whether changes follow worklog-driven development rules
- Validates work-doc type, numbering, INDEX.md and archive placement
Worklog Review by the numbers
- 1 all-time installs (skills.sh)
- Ranked #1,361 of 1,879 Documentation skills by installs in the Skillselion catalog
- Data as of Jul 8, 2026 (Skillselion catalog sync)
npx skills add https://github.com/dimonsmart/aitexteditor --skill worklog-reviewAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| Last updated | June 4, 2026 |
| Repository | dimonsmart/aitexteditor ↗ |
What it does
Reviews whether current changes follow the project's worklog-driven development rules, checking work-document type, numbering, index and archive placement.
Files
Worklog review
Read:
1. docs/worklog-method.md 2. relevant numbered current work documents directly under .worklog/ 3. current git diff 4. AGENTS.md 5. CLAUDE.md if present
Check:
1. Does this change require a work document? 2. If yes, does the document exist? 3. Is the type correct: spec, adr, or spike? 4. Is the numeric sequence correct across .worklog/ and .worklog/archive/? 5. Are current work documents stored directly under .worklog/? 6. Are archived work documents stored under .worklog/archive/? 7. Do work document filenames avoid old lifecycle markers? 8. Does .worklog/INDEX.md exist and reflect the current numbered documents? 9. Does the document have clear Goal, Context, and done criteria? 10. For specs, are scope and non-goals present? 11. For specs and ADRs, if Outcome exists, does it add durable engineering context instead of task status? 12. For spikes, are Result and Recommendation present and meaningful? 13. Are archived documents excluded from current requirements unless referenced through Replaces or explicitly needed for history? 14. If an old requirement or ADR changed, was the old document moved to .worklog/archive/ and the new current document given Replaces:? 15. Are accepted ADRs and old requirements left semantically immutable? 16. Are micro-changes and product-neutral small changes kept out of .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.md
These should be renamed to the new lifecycle-free format.
Output:
OKif the structure is fine.- Otherwise list concrete fixes.
- Do not modify files unless the user asks.
Related skills
Lark MarkdownInstantly turn any markdown file into clean, formatted Lark/Figma-compatible documents without manual reformatting.488k
Lark DocCreate, read, update, summarize, rewrite and manage Feishu/Lark cloud documents directly from agent workflows.401k16.1kLark WikiCreate, organize, query, and manage documents, spaces, and members inside Lark (Feishu) knowledge bases directly from AI agent workflows.397k16.1k
Domain ModelingBuild and sharpen a project's domain model: pin down domain terminology in a glossary and record architectural decisions as ADRs.318k202k
Opensource Guide CoachGet expert, attribution-safe guidance on launching and sustaining an open-source project.270k71Readme I18nMaintain consistent, updatable language selector blocks across every README variant in a multilingual repository.270k71