mcpbeat Sign in

Git Pr Workflows Git Workflow Agent Skill

Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern g

3k tokens
context cost
the whole folder, loaded on every use
11
files
instructions only
0
copies elsewhere
how many repositories repackaged it
505
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill git-pr-workflows-git-workflow

What comes with it

7 702 bytes besides the instruction
sub-skills/1-branch-management.md
sub-skills/1-change-analysis-and-categorization.md
sub-skills/1-code-quality-assessment.md
sub-skills/1-pr-description-generation.md
sub-skills/1-test-execution-and-coverage.md
sub-skills/2-conventional-commit-message-creation.md
sub-skills/2-dependency-and-breaking-change-analysis.md
sub-skills/2-pr-metadata-and-automation-setup.md
sub-skills/2-pre-push-validation.md
sub-skills/2-test-recommendations-and-gap-analysis.md

The instruction itself

17 sections, as written by the author

Complete Git Workflow with Multi-Agent Orchestration

Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern git best practices including Conventional Commits, automated testing, and structured PR creation.

[Extended thinking: This workflow coordinates multiple specialized agents to ensure code quality before commits are made. The code-reviewer agent performs initial quality checks, test-automator ensures all tests pass, and deployment-engineer verifies production readiness. By orchestrating these agents sequentially with context passing, we prevent broken code from entering the repository while maintaining high velocity. The workflow supports both trunk-based and feature-branch strategies with configurable options for different team needs.]

Use this skill when

  • Working on complete git workflow with multi-agent orchestration tasks or workflows
  • Needing guidance, best practices, or checklists for complete git workflow with multi-agent orchestration

Do not use this skill when

  • The task is unrelated to complete git workflow with multi-agent orchestration
  • You need a different domain or tool outside this scope

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.
  • If detailed examples are required, open resources/implementation-playbook.md.

Configuration

Target branch: $ARGUMENTS (defaults to 'main' if not specified)

Supported flags:

  • --skip-tests: Skip automated test execution (use with caution)
  • --draft-pr: Create PR as draft for work-in-progress
  • --no-push: Perform all checks but don't push to remote
  • --squash: Squash commits before pushing
  • --conventional: Enforce Conventional Commits format strictly
  • --trunk-based: Use trunk-based development workflow
  • --feature-branch: Use feature branch workflow (default)

Phase 1: Pre-Commit Review and Analysis

🧠 Knowledge Modules (Fractal Skills)

1. 1. Code Quality Assessment

2. 2. Dependency and Breaking Change Analysis

3. 1. Test Execution and Coverage

4. 2. Test Recommendations and Gap Analysis

5. 1. Change Analysis and Categorization

6. 2. Conventional Commit Message Creation

7. 1. Branch Management

8. 2. Pre-Push Validation

9. 1. PR Description Generation

10. 2. PR Metadata and Automation Setup

Other skills for the same job

different authors, same section of the catalogue
Git Commit
by github
vendor ×3

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

799 tokens
Github Code Review
by ComeOnOliver
×3

Comprehensive GitHub code review with AI-powered swarm coordination

13k tokens
Commit Work
by softaworks
×2

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens
Verification & Quality Assurance
by Microck
×2

Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.

4k tokens
Gh CLI
by christophacham
×2

GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.

10k tokens
Github
by Dicklesworthstone
×2

GitHub CLI - manage repositories, issues, pull requests, actions, releases, and more from the command line.

1k tokens
Codebase Cleanup Refactor Clean
by ComeOnOliver
×2

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.

9k tokens
Codebase Cleanup Tech Debt
by ComeOnOliver
×2

You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti

6k tokens

How to use it

Copy the folder

Take dokhacgiakhoa/git-pr-workflows-git-workflow from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.