git-guidelines

What problem does it solve?

Regular Git workflows are error-prone when editing multiple files, making it hard to trace why changes were made and risking messy histories. This Skill enforces a safety net by guiding Read → Checkpoint → Edit → Verify steps, requiring per-file checkpoints and descriptive commit messages to improve traceability and rollback capability.

Core Features & Use Cases

• Per-file checkpoints: checkpoint before editing each file to capture the current state and allow precise rollbacks.
• Mandatory, descriptive commits: commit messages must explain the rationale, scope, and outcomes of changes.
• Structured workflow: define and follow a Read → Checkpoint → Edit → Verify sequence for every edit, with explicit verification after each change.
• Safe operations guidance: rules for branching, pushing, and deleting files to prevent destructive actions and ensure review-friendly histories.

Quick Start

Begin by checkpointing before editing each file and writing a descriptive commit message that documents the rationale for every change.