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.

⭐6stars🔀2forks📁View on GitHub🕐Updated Jan 5, 2026⬇️1downloads

When & Why to Use This Skill

The Cursor Diary skill automates the creation of detailed, step-by-step implementation logs during coding sessions. It enhances developer productivity and code maintainability by capturing the rationale, commands, and failures of every minor change, ensuring full reproducibility and streamlined code reviews through seamless docmgr integration. By maintaining a 'tiny-step' diary, it bridges the gap between raw code and technical documentation.

Use Cases

  • Case 1: Documenting complex feature implementations to provide a clear narrative for code reviewers, highlighting 'tricky' logic and validation steps.
  • Case 2: Tracking intensive debugging sessions by recording failed commands and error messages to prevent redundant efforts and capture lessons learned.
  • Case 3: Maintaining high-fidelity audit trails for sensitive system changes, including exact commands, file paths, and commit hashes.
  • Case 4: Streamlining team knowledge transfer by creating a searchable history of implementation decisions and architectural evolutions for new contributors.
namecursor-diary
descriptionKeep 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.