git-workflow

Guides commit preparation, branch hygiene review, and change packaging for collaborative git workflows.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/Boulea7/ohmyclaude --skill git-workflow-boulea7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/Boulea7/ohmyclaude/tree/main/src/ohmyclaude/templates/skills/git-workflow
Command: npx skills add https://github.com/Boulea7/ohmyclaude --skill git-workflow-boulea7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams and AI agents often produce messy git histories with mixed unrelated changes, vague commit messages, or accidentally staged secrets. This Skill provides a disciplined checklist and guardrails for preparing commits and reviewing branch hygiene so history stays understandable and reviewable. ## Core Features & Use Cases - Commit Preparation Checklist: Inspect the working tree, separate unrelated changes, and confirm no sensitive files or secrets are staged before committing. - Commit Message Guidance: Write short, specific messages describing the user-visible change, with testing or validation noted in the final summary. - Safety Guardrails: Never amend or rewrite history unless explicitly requested, never revert unrelated local changes, and prefer non-interactive git commands. - Use Case: Before committing a feature branch, an agent follows the checklist to split unrelated edits into separate commits, verify no credentials are staged, and produce a clear commit message for reviewers. ## Quick Start Use the git-workflow skill to review my current working tree and help me prepare clean, well-described commits.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I prepare clean git commits before pushing?▼

Inspect the working tree first, separate unrelated changes into distinct commits, and write a short specific message describing the user-visible change. Confirm no sensitive files or secrets are staged, and mention testing or validation in the final summary.

How to write good commit messages for code review?▼

Use a short, specific message that describes the user-visible change rather than implementation details. In the final summary, mention what testing or validation was performed so reviewers understand the change's impact and verification status.

When is it safe to amend or rewrite git history?▼

Only amend or rewrite history when explicitly requested by the user or team. This Skill's guardrails prohibit history rewriting by default because it can disrupt collaborators who have based work on the existing commits.

How do I avoid committing secrets or sensitive files?▼

Before committing, inspect the staged changes and confirm that credentials, API keys, and sensitive configuration files are not included. This checklist step should run on every commit preparation, not just occasionally.

What are the limitations of a checklist-based git workflow?▼

A checklist guides behavior but does not enforce it technically; it relies on the agent or developer following each step. For hard enforcement, combine it with git hooks or CI checks that block secrets and enforce message formats.