skills.rest
vonomarap
vonomarapCOMMUNITY
Explore all skills by this author →
GitHub

coordinator-branchspec-gitflow

Generate GitFlow branch specifications with PR routing and safety constraints.

Updated Aug 30, 2025
Search Tags:#git#pr#policy#branch-naming#gitflow#branchspec
One-click install
npx skills add https://github.com/vonomarap/kanokna --skill coordinator-branchspec-gitflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coordinator-branchspec-gitflow
Source: https://github.com/vonomarap/kanokna/tree/main/agents/coordinator/skills/coordinator-branchspec-gitflow
Command: npx skills add https://github.com/vonomarap/kanokna --skill coordinator-branchspec-gitflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces consistent branch naming, PR routing, merge methods, and safety constraints so teams avoid unsafe direct pushes, force-pushes, and ambiguous task scopes when working with GitFlow-based workflows.

Core Features & Use Cases

  • BranchSpec Generation: Produces a complete BRANCH_SPEC record (id, classification, branch name, base branch, PR target, preferred merge method, back-merge requirement) suitable for coder automation and repository policy.
  • Mapping from Architect Advisories: Translates Architect GIT_IMPACT advisory blocks into concrete BranchSpec fields and PR body requirements, including RiskNotes and contract references.
  • Safety Enforcement: Encodes hard rules such as forbidding direct pushes to main/develop, banning force-push, and enforcing one-branch-per-task and back-merge rules; useful when preparing implementation from an approved handoff.
  • Use Case: Prepare PRs for feature, bugfix, chore, release, and hotfix branches consistent with GitFlow defaults and organization handoff metadata.

Quick Start

Generate a BranchSpec for a feature branch from approved handoff Handoff-YYYYMMDD-## using the Architect GIT_IMPACT advisory and GitFlow defaults.

Frequently Asked Questions about coordinator-branchspec-gitflow

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

FAQPage Schema
How do I enforce GitFlow branch naming conventions for pull requests?▼

Enforce GitFlow branch naming by generating branch specifications that classify feature, bugfix, chore, release, and hotfix branches. These specs ensure PR targets follow GitFlow defaults and require one-branch-per-task rules.

What is the best way to prevent direct pushes to main and develop branches in a GitFlow workflow?▼

Prevent direct pushes to main and develop by applying hard safety constraints encoded in branch specifications. These rules forbid direct pushes and force-pushes, ensuring all changes route through approved pull requests.

How do I translate Architect GIT_IMPACT advisories into pull request requirements?▼

Translate Architect GIT_IMPACT advisories into concrete BranchSpec fields that populate PR bodies with handoff metadata, scope, contract references, and risk notes. This ensures PRs contain required implementation context.

Does this GitFlow policy enforcement tool support hotfix and release branch workflows?▼

Yes, GitFlow policy enforcement supports hotfix and release branch workflows. It generates branch specifications that define base branches, PR targets, preferred merge methods, and back-merge requirements for these specific workflow types.

How do I generate a branch specification from an approved handoff for a feature branch?▼

Generate a branch specification from an approved handoff by creating a BRANCH_SPEC record containing the branch ID, classification, name, base branch, PR target, merge method, and back-merge requirement for coder automation.

Why do I need back-merge rules when preparing pull requests in GitFlow?▼

Back-merge rules are required in GitFlow to ensure changes from release or hotfix branches propagate back to develop. Enforcing these rules within branch specifications prevents branch divergence and maintains repository consistency.

Related Skills

Explore More Software Engineering Skills→
PanJasonPanJason
1

product-manager

Convert vague product prompts into a PLAN.md with scope, metrics, and architect handoff.

Community
Intermediate
cegit27cegit27
3

land-and-deploy

Merge pull requests, wait for CI and deployment, and verify production health.

Official
Advanced
githubgithub
4.9k

github-issue-query

Query GitHub issues with jq filters via the gh CLI.

Official
Intermediate
etylsarinetylsarin
59

git-workflow

Enforce feature-branch pull request workflows and prevent direct commits to main.

Community
Intermediate