skills.rest
ProfFroggo
ProfFroggoCOMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Standardize Git branching, commit, and PR workflows for Mission Control.

1|Updated Mar 8, 2026
Search Tags:#git#workflow#commit#branching#worktree#pull-request#team-workflow
One-click install
npx skills add https://github.com/ProfFroggo/froggo-mission-control --skill git-workflow-proffroggo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/ProfFroggo/froggo-mission-control/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/ProfFroggo/froggo-mission-control --skill git-workflow-proffroggo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git branching, commit, and PR workflows are standardized to prevent chaotic development and merge conflicts within Mission Control.

Core Features & Use Cases

  • Branch Naming: feature/{ticket-id}-short-description, fix/{ticket-id}-short-description, agent/{agent-name} for agent worktrees.
  • Commit Format: {type}({scope}): {short description} using types like feat, fix, refactor, test, docs, chore.
  • Worktree and Protected Workflows: agent worktrees setup, PR gates, and main branch protection.
  • Per-Task & Pre-commit Rules: ensure focused commits and pre-commit checks.
  • Use Case: coordinate simultaneous feature work and bug fixes across agents with PR-based reviews.

Quick Start

Create a feature branch like feature/{ticket-id}-short-description, implement changes following the commit format, run the pre-commit checks, and open a PR to merge into main.

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 for feature work and bug fixes?▼

Git branch naming standardizes development by using formats like feature/{ticket-id}-short-description for features and fix/{ticket-id}-short-description for bug fixes, preventing chaotic merges and ensuring consistent tracking across development teams.

What is the conventional commit format for structured git workflows?▼

The conventional commit format structures git history using {type}({scope}): {short description}, employing types like feat, fix, refactor, test, docs, and chore to categorize changes and ensure focused, readable commit logs.

How do I set up agent worktrees for parallel development tasks?▼

Agent worktrees setup uses the agent/{agent-name} branch naming convention to isolate parallel tasks, enabling simultaneous feature work and bug fixes across agents with PR-based reviews and protected main workflows.

Can I use pre-commit checks to enforce per-task rules in a git workflow?▼

Pre-commit checks enforce per-task rules by running automated gates before commits are finalized, ensuring focused commits and standardized formatting while maintaining protected main branch workflows and PR review processes.

What's the best way to coordinate simultaneous feature work across multiple agents?▼

Coordinating simultaneous feature work across agents requires structured git workflows with PR-based reviews, agent worktrees using agent/{agent-name} branches, and protected main branch gates to prevent merge conflicts and ensure consistent processes.

Related Skills

Explore More Software Engineering Skills→
thomfilgthomfilg

cleanup-worktrees

Clean up git worktrees after verifying merged code and Done/Closed ticket tasks.

Community
Advanced
hschnehschne
1

worktree

Automate git worktree creation, setup, integration, and safe cleanup.

Community
Intermediate
baphledbaphled
1

check-compliance

Run linting, formatting, security scans, and tests before committing code.

Community
Intermediate
TheArchitectitTheArchitectit
3

git-workflow

Standardize Git branching workflows and Conventional Commits enforcement across teams.

Community
Intermediate