git-workflow

Standardize Git commit messages, branch names, and PR descriptions with templates and conventions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes commit messages, branch naming, and PR descriptions to ensure predictable history.

Core Features & Use Cases

  • Commit messaging standards: enforce conventional commits for new changes.
  • Branch naming conventions: guide feature/bugfix branch prefixes and ticket IDs.
  • PR and code review templates: provide consistent PR descriptions and review checklists.

Quick Start

Use this skill to align your team's Git workflow by configuring commit message formats, branch prefixes, and PR templates.

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 commit messages across my team?

Conventional commits standardize commit message format with type, scope, and description (e.g., feat: add login). This Skill configures your repository to enforce this format, ensuring predictable Git history and automated changelog generation for all team members.

What's the best way to standardize branch naming conventions?

Branch naming conventions organize your workflow by prefixing branches with type and ticket ID (e.g., feature/PROJ-123). This Skill applies naming patterns across your repository so feature, bugfix, and hotfix branches follow a consistent structure your team recognizes.

Can I use pull request templates to guide code reviews?

Pull request templates provide structured descriptions and review checklists for every PR. This Skill configures PR templates so reviewers have consistent context, acceptance criteria, and testing steps documented before evaluation.

How do I align Git workflow across multiple projects?

Git workflow alignment means applying the same commit, branch, and PR standards across projects. This Skill enforces unified conventions so developers follow identical patterns regardless of which repository they work in, reducing friction and improving predictability.

What problems does standardizing Git workflows solve?

Standardized Git workflows prevent messy histories, unclear commits, and inconsistent PR descriptions. This Skill solves these by enforcing conventional commits, branch naming, and PR templates, making your repository history readable, searchable, and automatable.