skills.rest
go-go-golems
go-go-golemsOFFICIAL
Explore all skills by this author →
GitHub

cursor-diary

Capture reproducible coding steps with intent, commands, and outcomes.

13|3|Updated Nov 4, 2025
Search Tags:#workflow#changelog#documentation#diary#dev-log#docmgr#relate
One-click install
npx skills add https://github.com/go-go-golems/docmgr --skill cursor-diary
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cursor-diary
Source: https://github.com/go-go-golems/docmgr/tree/main/.codex/skills/cursor-diary
Command: npx skills add https://github.com/go-go-golems/docmgr --skill cursor-diary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Keeping a live, auditable record of coding work — what you changed, why, the exact commands you ran, failures, and what you learned — without losing context across sessions.

Core Features & Use Cases

  • Structured diary entries that capture intent, actions, and outcomes for reproducibility.
  • docmgr integration to relate diary steps to tickets, update changelogs, and track file changes.
  • Predefined templates in references/diary.md to standardize how work is documented.
  • Guided workflow that helps teams maintain thorough, reviewable documentation during development.

Quick Start

Create a new diary document and begin recording each coding step with intent, commands, and outcomes.

Frequently Asked Questions about cursor-diary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep a reproducible diary of coding steps and decisions during development?▼

A coding diary captures intent, commands, results, and lessons learned in structured entries. Using predefined templates standardizes documentation, ensuring work remains auditable and reproducible across sessions.

What is the best way to document intent and outcomes for changelog updates?▼

Documenting intent and outcomes for changelogs involves recording exact commands and failures during development. Integrating with docmgr relates diary steps to tickets and updates changelogs automatically.

Can I use docmgr to relate diary entries to specific file changes and tickets?▼

Yes, docmgr integrates directly with the diary workflow to relate files, track changes, and link documentation steps to tickets. This maintains a live, auditable record of coding work.

How do I standardize how my team documents development sessions?▼

Standardizing development documentation uses predefined templates in references to guide entries. A guided workflow helps teams capture intent, actions, and outcomes for reviewable records.

Why does my development team lose context across coding sessions?▼

Context is lost across coding sessions when work is undocumented. A structured dev-log diary captures what changed, why, and exact commands, preserving context and preventing knowledge loss.

Related Skills

Explore More Software Engineering Skills→
trueratruera
3.5k

trulens-dataset-curation

Create and curate ground-truth evaluation datasets for TruLens.

Official
Intermediate
thomfilgthomfilg

brief

Generate a structured product brief from ticket details or a manual description.

Community
Intermediate
LucasPierLucasPier

docs

Audit and standardize project documentation across JavaScript, CSS, and JSON files.

Community
Intermediate
MomoChenisMeMomoChenisMe
1

speclink-discuss

Initiate and record focused discussions as Markdown documents within Speclink.

Community
Advanced