Enforces staged Git workflows with per-file checkpoints and descriptive commit messages.
npx skills add https://github.com/dzackgarza/ai --skill git-guidelines
Please help me install this Agent Skill. Skill: git-guidelines Source: https://github.com/dzackgarza/ai/tree/main/opencode/skills/git-guidelines Command: npx skills add https://github.com/dzackgarza/ai --skill git-guidelines
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.
Begin by checkpointing before editing each file and writing a descriptive commit message that documents the rationale for every change.
High-intent search queries and answers about installing and using this skill.
Safe Git workflows are enforced by mandating per-file checkpoints and descriptive commit messages. This requires applying a Read, Checkpoint, Edit, and Verify sequence for every edit to capture the current state and allow precise rollbacks.
Preventing destructive actions in version control involves enforcing safe-branching rules, explicit verification after each change, and structured commit guidelines. These rules ensure review-friendly histories and prevent accidental data loss.
Per-file checkpoints are needed in Git workflows to capture the current state before editing each file. This practice allows precise rollbacks and makes it easier to trace exactly why specific changes were made, improving overall traceability.
Descriptive commit messages for traceability must document the rationale, scope, and outcomes of changes. This structured approach replaces vague messages, ensuring the history clearly explains the reasoning behind every modification.
The Read, Checkpoint, Edit, Verify sequence supports code review by requiring explicit checks after each modification. Following this structured workflow ensures modifications are auditable and generates review-friendly commit histories.
Structured Git checkpoints require strict adherence to the Read, Checkpoint, Edit, Verify workflow for every file edit. This overhead may slow down rapid prototyping but is necessary to maintain auditable histories and rollback capability.
alexanderopCreate isolated git worktrees for feature branches with safety checks.
trysmrCommit current changes to a Git branch and push to the remote.
jaeyeonlingStandardize Git workflows with conventional commits and branching strategies.
pazdedavGenerate conventional Git commits by analyzing code diffs and staging files.
