coordinator-branchspec-gitflow

Community

Enforce GitFlow branch naming and PR rules

Authorvonomarap
Version1.0.0
Installs0

System Documentation

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.

Dependency Matrix

Required Modules

None required

Components

Standard package

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: coordinator-branchspec-gitflow
Download link: https://github.com/vonomarap/kanokna/archive/main.zip#coordinator-branchspec-gitflow

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.