write-diary

Write diary entries to /docs/diary/YYYYMMDD.md with session context and logs.

1|Updated Aug 31, 2024
One-click install
npx skills add https://github.com/nnsi/hono-practice --skill write-diary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-diary
Source: https://github.com/nnsi/hono-practice/tree/main/.claude/skills/write-diary
Command: npx skills add https://github.com/nnsi/hono-practice --skill write-diary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers capture session progress, reflections, and lessons learned by automatically writing diary entries to a structured log in the docs folder.

Core Features & Use Cases

  • Automated diary generation: creates or updates /docs/diary/YYYYMMDD.md with current session content and context.
  • Context-aware logging: reads existing /docs/diary-cc-logs/ when available to include before/after details, then cleans up logs after diary creation.
  • Guideline-driven writing: adheres to CLAUDE diary guidelines when formatting entries and updating CLAUDE.md accordingly.
  • Use Case: end-of-day recap during a coding session, sprint retrospective notes, or learning reflections after experiments.

Quick Start

Write a diary entry for today describing your session and lessons learned.

Frequently Asked Questions about write-diary

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

FAQPage Schema
How do I automate daily development session logging into a structured diary?

Automating daily development session logging is achieved by creating or updating a structured markdown file at /docs/diary/YYYYMMDD.md, which captures your session progress, reflections, and lessons learned using current session context.

What is the best way to document coding reflections and lessons learned after a sprint?

Documenting coding reflections and lessons learned after a sprint is handled by assembling diary content that adheres to specific formatting guidelines, automatically recording your development notes and retrospective observations into a daily log file.

Does the daily diary generation work without manual context input?

Daily diary generation works without manual context input by automatically retrieving the current date, resolving the file path, and reading existing nearby logs in /docs/diary-cc-logs/ to include before and after session details.

How do I ensure my development notes follow consistent formatting guidelines?

Ensuring consistent formatting for development notes is achieved through guideline-driven writing that adheres to predefined CLAUDE diary guidelines when assembling entries and updating CLAUDE.md accordingly.

What happens to temporary session logs after a diary entry is created?

After a diary entry is created, temporary session logs are handled by a cleanup step that removes the existing logs from /docs/diary-cc-logs/ once the before and after details have been successfully integrated into the daily markdown file.