git-workflow

Enforce conventional commits, branch naming, and PR-based reviews in Git workflows.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/RaoXuntian/azurevm-openclaw-backup --skill git-workflow-raoxuntian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/RaoXuntian/azurevm-openclaw-backup/tree/main/skills/git-workflow
Command: npx skills add https://github.com/RaoXuntian/azurevm-openclaw-backup --skill git-workflow-raoxuntian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes how teams commit, branch, and review code to reduce errors and merge conflicts.

Core Features & Use Cases

  • Conventional commits enforcement, default branch detection, and consistent branch naming.
  • PR-based merge flow with automated sub-agent code review.
  • Guidelines for commits, branches, and merges to accelerate collaboration across agents.

Quick Start

Create a feature branch, commit with a conventional message, and open a PR against the detected default branch.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I enforce conventional commits in an automated Git workflow?

To enforce conventional commits in a Git workflow, the Skill validates commit messages against standard formats, detects the default branch, and applies pre-commit checks before allowing pushes to reduce errors and merge conflicts.

What is the best way to standardize branch naming for pull requests?

The best way to standardize branch naming for pull requests is to apply automated workflow rules that enforce consistent branch naming conventions, detect the default branch, and guide agents to open PRs against it for cross-agent code review.

Can automated sub-agents perform code review on pull requests?

Yes, automated sub-agents can perform code review on pull requests. The Skill facilitates a PR-based merge flow where sub-agents review code across agents to accelerate collaboration and reduce merge conflicts.

How do I set up a PR-based merge flow for software development?

To set up a PR-based merge flow, create a feature branch, commit with a conventional message, and open a pull request against the detected default branch to trigger automated sub-agent code review and merge validation.

Does default branch detection work with standard Git push rules?

Yes, default branch detection works with standard Git push rules. The Skill satisfies mandatory default branch detection, commit format validation, and pre-commit checks to standardize how teams commit, branch, and review code.