abc-git-flow_skill

This skill helps you manage the ABC Git Flow workflow, guiding branch operations, tagging, and release steps across environments.

Python

15

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill abcfed/claude-marketplace --skill abc-git-flow

SKILL.md9.5 KB

Overview

This skill assists with ABC backend Git branch-management workflows based on an extended git-flow that supports gray releases. It provides command shortcuts (git abc ...) for creating and finishing feature/hotfix/rc/gray flows, tag creation, and MR handling, plus non-interactive scripts for CI use. It enforces branch rules, tag naming, and push/cleanup steps to keep releases predictable.

How this skill works

The skill maps common keywords (feature, hotfix, rc, tag, MR, gray, release, merge) to the appropriate git abc commands and workflow guidance. It explains branch origins, the sequence for feature development, hotfixes (master or gray), and release promotion (develop → rc → gray → master). It also documents interactive commands and their non-interactive Python script equivalents for CI automation.

When to use it

Starting a new feature branch or finishing feature development
Fixing urgent bugs in production (hotfix) or gray environment (hotfix-g)
Preparing and promoting releases: t/p/g/v tag flows (test→pre-release→gray→full)
Creating Merge Requests or configuring MR tokens
Automating tag or MR creation in CI using non-interactive scripts

Best practices

Always run git status and ensure a clean working tree before git abc actions
After finish operations, immediately push all affected long-lived branches
Use rebase only for single-developer branches; avoid rebase on shared branches
Use provided non-interactive Python scripts for CI/CD to avoid blocking prompts
Delete temporary feature/hotfix branches after merge to keep repo tidy

Example use cases

Create feature branch and create f-tag for tester: git abc feature start <name> → develop rebase → git abc tag create
Patch production bug: git abc hotfix start <name> → fix → git abc tag create → git abc hotfix finish <name> → push master gray rc develop
Promote a release: git abc rc start → git abc tag create (p) → git abc rc finish → git abc tag create (g) → git abc gray publish → git abc tag create (v)
Automate tag creation in CI: scripts/tag_create.py v --deps "service-A" --operation "deploy" --skipdeploy to generate a compliant tag non-interactively
Create MR from script: scripts/mr_create.py -t develop -T "feat: new API" -r Alice Bob --skip-notify

FAQ

Rebase is recommended for independent single-developer branches to keep history tidy. For branches worked on by multiple people, use merge to avoid rewriting shared history.

Which branches must I push after a hotfix finish?

hotfix finish merges into master, gray, rc, and develop — you must push master, gray, rc, and develop. For hotfix-g, push gray, rc, and develop (not master).