git-workflows

Enforce trunk-based branching, squash merges, and veto rules for Git workflows.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/fyrsmithlabs/marketplace --skill git-workflows-fyrsmithlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflows
Source: https://github.com/fyrsmithlabs/marketplace/tree/main/plugins/fs-dev/skills/git-workflows
Command: npx skills add https://github.com/fyrsmithlabs/marketplace --skill git-workflows-fyrsmithlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git projects often struggle with coordinating multiple agents, PR planning, and consistent reviews. This skill provides governance to enforce modern, agent-driven git workflows across the lifecycle of changes, ensuring transparency and traceability.

Core Features & Use Cases

  • Parallel agent coordination: manage multi-branch work and concurrent reviews without conflicts.
  • Consensus-driven reviews: enforce veto rules and collective decision making before merging.
  • Contextd integration guidance: guidance on memory/learning capture and remediation tracking in PR workflows.
  • Use Case: When delivering a feature across several teams, the skill coordinates PR creation, review gates, and final approval with a shared context.

Quick Start

  • Initialize a new feature work using trunk-based branching
  • Run parallel consensus reviews with agents
  • Merge using squash after all approvals

Frequently Asked Questions about git-workflows

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

FAQPage Schema
How do I coordinate parallel Git workflows with multiple AI agents?

Multi-agent Git workflow coordination is managed by enforcing trunk-based branching and parallel consensus reviews, ensuring concurrent feature work across multiple branches proceeds without conflicts before merging.

How does consensus-based code review work for multi-agent PRs?

Consensus-based code review enforces collective decision-making and veto rules across AI agents, requiring all approval gates to pass before allowing a squash merge into the main repository.

Can I enforce veto rules and pre-flight checks before merging a PR?

Yes, you can enforce veto rules and pre-flight checks to govern PR workflows, ensuring that all consensus requirements and automated governance gates are satisfied prior to final merge.

What is the best way to manage trunk-based branching for concurrent AI development teams?

Trunk-based branching for concurrent teams is managed by automating PR creation and review gates, coordinating parallel agent work, and enforcing squash merges only after all collective approvals are met.

Does this Git workflow governance integrate with memory and remediation tracking?

Yes, Git workflow governance integrates with contextd to provide guidance on memory and learning capture, enabling remediation tracking and shared context throughout the PR review lifecycle.

When do I need automated governance for agent-driven Git workflows?

Automated governance is needed when delivering features across several teams using AI agents, providing the traceability, transparency, and consensus enforcement required for complex, parallel repository changes.