cursor-diary

The Cursor Diary skill is designed for software developers and engineers who prioritize reproducibility and structured documentation in their coding workflows. By maintaining a granular implementation log, it ensures that every step of a session—including intent, exact command executions, error outputs, and design rationale—is captured systematically. It serves as a personal knowledge base that bridges the gap between raw code changes and long-term project documentation.

• Automatically links implementation steps to docmgr tickets and workspaces for unified project tracking.

• Captures verbatim error logs and failures to aid in debugging and future root-cause analysis.

• Encourages small-step commits, ensuring that each change is isolated and documented with its corresponding commit hash.

• Provides templates for capturing high-value information like tricky technical hurdles and code-review-ready observations.

• Enables bidirectional traceability by relating specific source files to diary entries using absolute file paths.

• Facilitates changelog maintenance by automating the record-keeping process for ticket-based workflows.

• Users should initiate the diary at the start of a session or task to ensure full context coverage.

• Expected inputs include the intent for a coding task, commands run, failures encountered, and insights gained during the build process.

• The tool expects the presence of a docmgr workspace and relies on the user to follow the provided directory structure (typically found in ttmp/ directories).

• It is best practice to commit diary updates separately from code changes to maintain a clean git history.

• Constraints include the need for consistent use of the docmgr CLI for metadata management and file linking.

• The output is optimized for developers who need to review their own work or hand off context to a second pair of eyes, ensuring that all technical artifacts and rationales remain consistent with the codebase.