git-workflow

Standardize Git workflows with branch naming, conventional commits, and PR processes.

Updated Oct 4, 2025
One-click install
npx skills add https://github.com/Maple-and-Spruce/maple-and-spruce --skill git-workflow-maple-and-spruce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/Maple-and-Spruce/maple-and-spruce/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/Maple-and-Spruce/maple-and-spruce --skill git-workflow-maple-and-spruce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes Git workflows to reduce merge conflicts, improve traceability, and streamline collaboration across teams by defining branch naming, commit conventions, PR processes, and issue tracking.

Core Features & Use Cases

  • Branch Naming: enforce patterns like feature/{issue-number}-{short-description}, fix/{issue-number}-{short-description}, and chore/{description} to keep history clean and navigable.
  • Commit Conventions: use conventional commits and include issue references to maintain a readable history.
  • PR Process: require pull requests for all changes, include templates, and enforce code review and CI checks before merging.
  • Issue Tracking: link commits and PRs to issues to maintain end-to-end traceability across the lifecycle.

Quick Start

Create a feature/{issue-number}-{short-description} branch, commit changes with clear messages, and open a PR for review.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I standardize Git branch naming to reduce merge conflicts across teams?

Standardize Git branch naming by enforcing patterns like feature/{issue-number}-{short-description}, fix/{issue-number}-{short-description}, and chore/{description} to keep history clean and navigable.

What's the best way to link Git commits and pull requests to issue tracking?

Link Git commits and pull requests to issue tracking by including issue references in commit messages and PR descriptions, maintaining end-to-end traceability across the development lifecycle.

How do I enforce conventional commits and pull requests for all code changes?

Enforce conventional commits and pull requests by requiring PRs for all changes, applying commit message conventions, and mandating code review and CI checks before merging.

Can I use this Git workflow for collaborative software development without external dependencies?

Yes, you can use this Git workflow for collaborative software development as it requires no external dependencies, standardizing branch creation, commits, and PRs independently.

Why does requiring pull requests for all changes improve code review?

Requiring pull requests for all changes improves code review by enforcing templates and CI checks before merging, ensuring collaborative validation and standardized commit conventions.

When do I need to use chore branch naming instead of feature or fix branches?

Use chore/{description} branch naming for maintenance tasks that do not fit feature development or bug fixes, keeping repository history organized and navigable alongside feature and fix branches.