git-flow

Automate Git commit hygiene, PR readiness, and issue linking workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ClementWalter/claudine --skill git-flow-clementwalter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-flow
Source: https://github.com/ClementWalter/claudine/tree/main/.claude/skills/git-flow
Command: npx skills add https://github.com/ClementWalter/claudine --skill git-flow-clementwalter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates Git workflow hygiene by enforcing minimal, meaningful commit messages, ensuring PR readiness, and preserving clean repository states.

Core Features & Use Cases

  • Commit hygiene: enforces concise, semantic commit messages and prevents drift.
  • PR readiness: guides PR creation with proper context, links to issues, and avoids scope creep.
  • State validation: checks for a clean working tree before operations and maintains consistent workflow.

Quick Start

Run the git-flow workflow to structure commits, PRs, and issue linking with minimal effort.

Frequently Asked Questions about git-flow

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

FAQPage Schema
How do I automate Git workflows to enforce clean commit messages?

Automating Git workflows enforces concise, semantic commit messages through scripted validation, preventing message drift and ensuring repository hygiene across all team contributions.

What is the best way to prepare a pull request with proper issue tracking context?

Preparing pull requests with issue tracking involves validating a clean working tree, linking relevant issues, and providing proper context to avoid scope creep during PR creation.

How do I link issues and close them automatically through commit messages?

Linking issues through commit messages uses issue closing semantics within a scripted workflow, automatically associating commits with tracked issues to close them upon PR merge.

Does Git workflow automation check for a clean working tree before creating commits?

Git workflow automation checks for a clean working tree before operations, validating repository state to maintain consistent workflow and prevent committing unintended changes.

Can I use commit conventions to guide PR creation and prevent scope creep?

Commit conventions guide PR creation by structuring semantic commit messages and ensuring PR readiness with proper context, actively preventing scope creep across repositories.