git-commit

Create signed, atomic git commits with comprehensive messages.

219|41|Updated Feb 21, 2024
One-click install
npx skills add https://github.com/proto-at-block/bitkey --skill git-commit-proto-at-block
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/proto-at-block/bitkey/tree/main/app/ai-rules/skills/git-commit
Command: npx skills add https://github.com/proto-at-block/bitkey --skill git-commit-proto-at-block

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to ensure every code change is committed with a verifiable signature, committed in an atomic scope, and described with a clear, context-rich message that supports future investigation and auditability.

Core Features & Use Cases

  • Signed commits: Enforce using the -S flag to attach a GPG signature to every commit for verification.
  • Atomic commits: Promote one complete unit per commit to keep history clean and reviewable.
  • Comprehensive messages: Include business domain context, technical decisions, architectural rationale, and rationale for changes to capture intent.
  • Workflow hygiene: Supports squashing related changes into a single coherent history and keeping independent changes separate with distinct purposes.

Quick Start

Always sign commits with -S and ensure each commit is atomic and well-documented.

Frequently Asked Questions about git-commit

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

FAQPage Schema
What is an atomic git commit and why is it needed for version control?

An atomic git commit encapsulates one complete, self-contained unit of change to keep repository history clean and reviewable. This practice maintains clear traceability by ensuring independent changes remain separate with distinct purposes.

How do I write comprehensive git commit messages for code reviews?

Comprehensive git commit messages should include business domain context, technical decisions, and architectural rationale. Capturing this intent and decision context in commit messages supports future investigation, auditability, and effective code reviews.

How do I enforce signed commits using the git -S flag?

Enforce signed commits by applying the git -S flag to attach a GPG signature to every commit. This ensures a verifiable history by cryptographically validating the author identity across daily coding and PR submissions.

What's the best way to squash related changes into a single coherent git history?

The best way to maintain coherent git history is to squash related changes into a single atomic commit while keeping independent changes separate. This workflow hygiene ensures each commit represents a distinct, complete purpose for reviewability.

Does git commit signing work with standard code review and PR workflows?

Git commit signing applies directly to daily coding, code reviews, and PR submissions. By requiring the -S flag for GPG signatures, it maintains verifiable traceability across standard version control workflows without disrupting them.