dev-memory-update

Extract development events from git commits into ai_memory/events.jsonl.

7|3|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/BerryKuipers/claude-code-toolkit --skill dev-memory-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-memory-update
Source: https://github.com/BerryKuipers/claude-code-toolkit/tree/main/.claude/skills/memory/dev-memory/update
Command: npx skills add https://github.com/BerryKuipers/claude-code-toolkit --skill dev-memory-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically extract and store development events from git commits into ai_memory/events.jsonl.

Core Features & Use Cases

  • Automatic extraction: Parse commit message, diff, and metadata to infer events.
  • Timeline storage: Persist events to ai_memory/events.jsonl.
  • Backfill support: Manually process past commits or non-commit activities.

Quick Start

After configuring, call the skill with repository, branch, commit_hash, commit_message, and commit_timestamp. Optional fields include diff_summary, files_changed, related_issues, related_prs, author.

Frequently Asked Questions about dev-memory-update

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

FAQPage Schema
How do I automatically capture development events from git commits?

Extract and store development events from git commits into ai_memory/events.jsonl by calling the skill with commit metadata (message, diff, branch, timestamp). The skill analyzes this data, infers event types, and persists structured records with required fields like repo, branch, commit_hash, and commit_message.

Can I set up automatic post-commit hooks to capture events?

Yes, the skill supports automatic post-commit hooks that trigger event extraction without manual intervention. After configuration, commits are parsed and events are stored automatically, or you can manually process past commits and backfill the timeline.

What metadata does the skill capture from each commit?

The skill captures required fields—repo, branch, commit_hash, commit_message, commit_timestamp—and optional metadata including diff_summary, files_changed, related_issues, related_prs, and author. It generates event IDs and infers event types from commit messages for consistent records.

How do I backfill development events from past commits?

Process past commits or non-commit activities manually by calling the skill with historical commit data. Batch processing is supported, allowing you to retroactively populate ai_memory/events.jsonl with events from your repository's history.

What happens if required commit fields are missing?

The skill enforces required fields: repo, branch, commit_hash, commit_message, and commit_timestamp. Events cannot be stored without these fields; optional metadata like diff_summary or author can be omitted, but core commit details must be provided for event creation.