lusena-pre-commit-sync

Analyze uncommitted diffs to update memory bank documentation and changelog entries.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/fulfon/lusena-dawn --skill lusena-pre-commit-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lusena-pre-commit-sync
Source: https://github.com/fulfon/lusena-dawn/tree/main/.opencode/skills/lusena-pre-commit-sync
Command: npx skills add https://github.com/fulfon/lusena-dawn --skill lusena-pre-commit-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that your project's documentation and memory bank are always up-to-date and accurately reflect the latest code changes before you commit, preventing outdated information and ensuring consistency.

Core Features & Use Cases

  • Automated Documentation Sync: Analyzes uncommitted changes against the current branch to identify and update documentation gaps.
  • Memory Bank Maintenance: Updates core files like activeContext.md, progress.md, and feature/pattern documentation.
  • Changelog Generation: Automatically creates new entries in the changelog file.
  • Use Case: Before committing a set of changes that introduce a new feature and modify several existing ones, run this skill to ensure all related documentation, including feature descriptions and the changelog, is updated accordingly.

Quick Start

Run the lusena-pre-commit-sync skill to update all documentation based on your current uncommitted changes.

Frequently Asked Questions about lusena-pre-commit-sync

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

FAQPage Schema
How do I automatically sync documentation before a git commit?

Syncing project memory before a commit involves analyzing uncommitted code diffs and updating memory bank files like activeContext.md. It ensures documentation parity across progress, system patterns, and technical context before finalizing the commit.

How do I generate changelog entries automatically from uncommitted changes?

Generating changelog entries from uncommitted changes requires analyzing git diffs to identify code modifications. The process automatically creates new entries in the changelog file while updating related feature and pattern documentation to maintain consistency.

Can I update project memory bank files without manual file editing?

Updating project memory bank files without manual editing is possible by running a synchronization process against your current branch. It automatically updates core files like activeContext.md and progress.md based on identified documentation gaps from uncommitted changes.

Does this documentation sync approach work with standard git workflows?

Documentation sync works directly with standard git workflows by requiring git commands for diff analysis. It integrates into your existing version control process to update technical context and product context files before you finalize a commit.

What is the best way to maintain documentation parity across multiple project contexts?

Maintaining documentation parity across project contexts is best achieved by synchronizing the memory bank before committing. This updates active context, progress, system patterns, technical context, product context, features, and patterns simultaneously.