recording-changes

Name: recording-changes
Availability: InStock
Author: masa-codehub

Stage changes and emit compliant git commit messages with branch validation.

Updated Aug 18, 2025

Search Tags:#git #commit #pre-commit #workflows #guardrails #branch-strategy #record-changes

Ready to run

npx skills add https://github.com/masa-codehub/gemini_agent --skill recording-changes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: recording-changes
Source: https://github.com/masa-codehub/gemini_agent/tree/main/.gemini/skills/recording-changes
Command: npx skills add https://github.com/masa-codehub/gemini_agent --skill recording-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Replaces ad-hoc commits with a controlled workflow that ensures changes are recorded consistently and atomically, following project conventions. This helps maintain clear history, enforce pre-commit integrity, and recover gracefully from hook failures.

Core Features & Use Cases

Role: Gatekeeper ensures all changes are staged and committed with compliant messages.
Workflow covers Branch Validation, Staging & Commit, and Error Recovery to keep history clean.
Use Case: Staging a batch of product changes and ADR drafts while preserving a deterministic history.

Quick Start

Switch to your feature branch, stage the changes, and commit with a compliant message so pre-commit hooks pass.

Frequently Asked Questions about recording-changes

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

FAQPage Schema

How do I enforce a consistent git commit workflow with pre-commit hooks?▼

To enforce a consistent git commit workflow, you must stage changes and emit compliant messages so pre-commit hooks pass. This ensures changes are recorded atomically and project conventions are maintained without ad-hoc commits.

What is the best way to stage batch product changes and ADR drafts while keeping git history clean?▼

The best way to stage batch product changes and ADR drafts is to use a controlled workflow that validates your branch, stages the batch atomically, and commits with a compliant message to preserve a deterministic git history.

Do I need a defined base branch to use pre-commit guardrails for recording changes?▼

Yes, you need a defined base branch in your repository to use pre-commit guardrails for recording changes. The workflow expects this setup to validate branches and properly guard the commit process.

How do I recover from pre-commit hook failures when committing design artifacts?▼

To recover from pre-commit hook failures when committing design artifacts, you follow the error recovery workflow designed to gracefully handle hook failures while maintaining clear history and pre-commit integrity.

Why should I use atomic commits instead of ad-hoc commits in my git branch strategy?▼

You should use atomic commits instead of ad-hoc commits because they ensure changes are recorded consistently, maintain clear history, enforce pre-commit integrity, and follow project conventions for a deterministic branch strategy.