skills.rest
cloga
clogaCOMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Enforce branch-based VCS workflows with pull requests and MCP governance.

3|2|Updated Mar 6, 2026
Search Tags:#git#workflow#mcp#branching#code-review#pull-request#version-control
One-click install
npx skills add https://github.com/cloga/optimus-code --skill git-workflow-cloga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/cloga/optimus-code/tree/main/optimus-plugin/skills/git-workflow
Command: npx skills add https://github.com/cloga/optimus-code --skill git-workflow-cloga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Every code change must go through a branch and Pull Request to ensure traceability and prevent direct commits to master/main.

Core Features & Use Cases

  • Branch-based changes with mandatory PR reviews to enforce code governance.
  • MCP-driven workflow using vcs_create_work_item, vcs_create_pr, and vcs_merge_pr to manage tracking, review, and merging.
  • Guardrails for safe merges, including rebasing before merging and avoiding direct pushes to protected branches.
  • Use Case: A developer fixes a bug on a feature branch, creates a Tracking Issue, opens a PR for peer review, and, after approvals, merges the PR into the main line via the MCP commands.

Quick Start

Create a feature branch, submit a PR, and merge via the MCP workflow to complete a feature safely.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I enforce a branch-based git workflow with mandatory pull request reviews?▼

You enforce a branch-based git workflow by routing every code change through a feature branch and pull request to ensure traceability. This Skill mandates peer reviews and prevents direct commits to master or main for safe code governance.

Can I use MCP commands to automate pull request creation and merging?▼

Yes, you can use MCP commands to automate pull request creation and merging. This Skill uses vcs_create_work_item, vcs_create_pr, and vcs_merge_pr to manage work item tracking, code review, and merging into the main branch.

What is the best way to prevent direct pushes to protected branches in version control?▼

The best way to prevent direct pushes to protected branches is to apply branch protection guardrails. This Skill blocks direct pushes to the main line, requiring a feature branch and a pull request to route and review all code changes safely.

How does rebase-first merging work for git pull requests?▼

Rebase-first merging works by enforcing guardrails that require a feature branch to be rebased before merging into the main line. This ensures a clean, traceable version control history and prevents direct commits to master or main.

Do I need a tracking issue for every git pull request?▼

Yes, you need a tracking issue for every pull request to maintain traceability across your software project. This Skill's MCP workflow uses vcs_create_work_item to create tracking issues, ensuring every feature branch change is linked and reviewed before merging.

Related Skills

Explore More Software Engineering Skills→
onshoreoutsourcingonshoreoutsourcing

git-repository-setup-validation

Validate Git repository branch structure and protection rules.

Official
Intermediate
pkuppenspkuppens

deployment-release

Coordinates artifact delivery, tests, and rollback decisions for software releases.

Community
Advanced
guccangguccang
3

requesting-code-review

Automate pre-commit code review for security issues, regressions, and quality problems.

Community
Advanced
jal-cojal-co
35

git

Guide Git and GitHub CLI operations for version control and pull requests.

Community
Advanced