diary

Generate development diaries from Claude Code history and Git commits.

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/creepyblues/kstorybridge-integrated --skill diary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diary
Source: https://github.com/creepyblues/kstorybridge-integrated/tree/main/.claude/skills/diary
Command: npx skills add https://github.com/creepyblues/kstorybridge-integrated --skill diary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Teams struggle to capture daily development work and publish it consistently. This skill automates gathering Claude Code history and Git commits to generate structured development diaries for internal review and public posting on kstorybridge.com.

Core Features & Use Cases

  • Automates diary generation by aggregating Claude Code history and repository commits for the KStoryBridge project.
  • Produces publish-ready diary entries including daily summaries, work sessions, categorized activities, and statistics.
  • Supports optional Slack notifications when configured and publishes to marketing diary draft.

Quick Start

Run the daily diary script to generate yesterday's entry.

Frequently Asked Questions about diary

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

FAQPage Schema
How do I automate development diary generation from Git commits and Claude history?

Automate development diary generation by running Python scripts that aggregate local Claude Code history and Git commits to produce structured, publish-ready daily summaries for stakeholders.

Can I send automated Slack notifications when a new dev diary is published?

Yes, automated Slack notifications can be sent when a new dev diary is published. You must configure a Slack webhook in the environment before running the generation script.

What do I need to generate a publish-ready development diary from Git and Claude?

To generate a publish-ready development diary, you need local Claude Code history, a configured Slack webhook, and the included Python scripts to render and publish the aggregated entries.

How does aggregating Claude Code history and Git commits work for daily development logs?

Aggregating Claude Code history and Git commits works by analyzing daily activity across sessions and commits to format structured diary entries with categorized activities and statistics.

Does the automated diary generation store drafts before publishing final entries?

Yes, the automated diary generation system stores drafts before publishing final entries. It renders the aggregated content into a marketing diary draft for internal review and public posting.