cursor-diary
/cursor-diary
Keep a tiny-step implementation diary during coding sessions (what changed, why, commands run, failures, and what was learned), with docmgr integration (doc add/relate/changelog). Use when the user asks to "keep a diary", "write a dev log", or document work step-by-step.
- Author
- go-go-golems ↗
- Repository
- docmgr ↗
- Licence
- MIT
- Last repository change
- 10.09.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Keep a tiny-step implementation diary during coding sessions (what changed, why, commands run, failures, and what was learned), with docmgr integration (doc add/relate/changelog). Use when the user asks to "keep a diary", "write a dev log", or document work step-by-step.
Triggers from the description
Original author description
Keep a tiny-step implementation diary during coding sessions (what changed, why, commands run, failures, and what was learned), with docmgr integration (doc add/relate/changelog). Use when the user asks to "keep a diary", "write a dev log", or document work step-by-step.
How it works
- Overview
- Workflow
- Output template
- Notes
SKILL.md preview
--- name: cursor-diary description: Keep a tiny-step implementation diary during coding sessions (what changed, why, commands run, failures, and what was learned), with docmgr integration (doc add/relate/changelog). Use when the user asks to "keep a diary", "write a dev log", or document work step-by-step. --- # Cursor Diary ## Overview Maintain a step-by-step implementation diary as you work, focused on reproducibility (exact commands, file paths, commit hashes) and review efficiency (what to check + how to validate). ## Workflow ### 1) Bootstrap - Create a diary doc early (before exploration if possible). - If using docmgr tickets: `docmgr doc add --ticket TICKET-ID --doc-type reference --title "Diary"` ### 2) Record each tiny step (frequently) - Write 1–2 short prose paragraphs first (intent + what it unlocked). - Include exact commands, key outputs, and versions when relevant. - Capture failures verbatim (errors are valuable). ### 3) Keep code ↔ docs consistent (docmgr loop) - Implement + format + test. - Commit code (record hash). - Update diary with the commit hash + rationale. - Relate files to the diary with absolute paths: `docmgr doc relate --doc <diary-path> --file-note "/abs/path:why it matters"` - Update ticket changelog per step: `docmgr changelog update --ticket TICKET-ID --entry "Step N: ..." --file-note "/abs/path:reason"` - Commit docs separately (e.g., `Diary: record Step N`). ## Output template - Use the diary template in `references/diary.md` (copy/paste) as the canonical structure. ## Notes - Prefer many small steps over a few big ones. - Always include: “What was tricky to build” + “What warrants a second pair of eyes” when behavior changes.
Files in this package (2)
- SKILL.md 2 KB
- references/diary.md 6 KB
Versions
The database has no other skills named cursor-diary.
Database snapshot: 13.11.2026 · package version b3ffbf490872 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100diary
Write and maintain an implementation diary: step-by-step narrative of what changed, why, what worked, what failed (with exact errors/commands), what was tricky, and how to review/validate. Use when a user asks to create/update a “Diary” doc, record work for a ticket, document… - 90cursor-docmgr
Use the docmgr CLI to manage ticketed docs (create tickets, add docs, relate code files with file-note, update changelog, and search). Use when the user asks how to use docmgr, wants a docmgr command sequence, or needs docmgr best practices (file-note, quoting, doctor). - 100diary
Use when the user says 'save diary', 'log session', 'wrapping up', or at end of a productive session. - 100diary
Write today's diary - what got done, what was wasted, what was learned - bake it into a kid's picture-diary PNG, and update the rules ledger. Use when the user says "write the diary", "diary", "/diary", "picture diary", "일기 써", "그림일기", "오늘 일기", or on a daily schedule. - 95memstack-development-changelog-generator
Use when the user says 'generate changelog', 'update changelog', 'what changed', 'release notes', 'write changelog', or needs a formatted CHANGELOG.md from git commit history. Do NOT use for diary entries, git log viewing, or commit message writing. - 96writing-dev-diary
「開発日誌更新」「開発日誌作って」の言及時に使用。esa-llm-scoped-guardで開発日誌を新規作成・更新します。