wa:git-flow

Automate Git Flow branching, commits, pushes, and pull requests.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-git-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wa:git-flow
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/git-flow
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-git-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inconsistent or unsafe Git workflow execution by standardizing how teams calibrate branching strategy, validate repository state, and run the requested Git Flow action.

Core Features & Use Cases

  • Mode calibration (lite/standard/strict): Automatically resolves the development mode and applies the correct branching/PR rules and guardrails.
  • End-to-end Git Flow actions: Supports status, commit, push, and pr while enforcing branch and merge constraints (e.g., no force pushes, no merges without approval).
  • Pre-flight safety checks: Ensures dev is up to date with main when required, reducing integration drift and conflicts.

Quick Start

Ask to run Git Flow status by instructing the assistant: “Execute /wa:git-flow status.”

Frequently Asked Questions about wa:git-flow

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

FAQPage Schema
How do I automate git flow branching and pull request creation safely?

Automating git flow requires standardizing branching strategy, validating repository state, and enforcing pull request approvals. This Skill executes mode-calibrated branching, formatted commits, and PR creation while preventing unsafe actions like force pushes or unapproved merges.

What is the best way to enforce pre-flight checks before creating a pull request?

Pre-flight checks for pull requests ensure branches are synchronized and prevent integration drift. This Skill performs mandatory validations, such as verifying the development branch is up to date with main, before allowing any push or PR creation action to proceed.

Can I use mode-specific git flow rules for different team scenarios?

Mode-specific git flow rules allow teams to calibrate development rigor from configuration. This Skill supports lite, standard, and strict modes, automatically applying the correct branching constraints, guardrails, and pre-flight validations based on the resolved mode.

How do I prevent force pushes and unapproved merges in automated git flow?

Preventing force pushes and unapproved merges requires enforcing branch and merge constraints during workflow execution. This Skill applies guardrails that block unsafe git actions, ensuring all dev-to-main release PRs and feature-to-dev merges receive required approvals.

Why does my feature-to-dev pull request fail integration checks?

Feature-to-dev pull requests fail integration checks when development branches are not synchronized with the main branch. This Skill resolves this by running pre-flight safety checks to ensure dev is fully up to date with main before proceeding.

How do I standardize commit message formatting with domain prefixes across multiple repositories?

Standardizing commit message formatting with domain prefixes requires applying consistent rules across multiple repositories. This Skill automates formatted commits with domain prefixes and performs multi-repo status checks to maintain workflow consistency.