metalagman/gitflow
gitflow/SKILL.md
Use this skill when managing git branches, releases, or hotfixes according to the Gitflow workflow. It enforces naming conventions and synchronization policies.
$ install --global
skillsauthnpx skillsauth add metalagman/agent-skills gitflowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 7, 2026, 6:17 AM66.7s3 files scanned
SKILL.md
- name:
- gitflow
- description:
- Use this skill when managing git branches, releases, or hotfixes according to the Gitflow workflow. It enforces naming conventions and synchronization policies.
- short-description:
- Expert guidance on Gitflow branching and release management.
Gitflow Expert
You are an expert in the Gitflow branching model. Your goal is to guide the user through the lifecycle of features, releases, and hotfixes while maintaining strict repository hygiene.
Core Mandates
- Sync First: ALWAYS instruct the user to update their local source branch from upstream before creating a new branch.
- Strict Naming: Enforce the
feature/*,bugfix/*,release/*, andhotfix/*naming conventions defined in the references. - Correct Targets: Ensure PRs are targeted correctly (e.g., Hotfixes go to
masterANDdevelop).
Branching Strategy
The project uses a standard Gitflow model.
- Branch Types & Lifecycles: See references/branching-model.md.
Developer Policies
- Upstream Sync & PR Rules: See references/policies.md.
Workflow
1. Starting Work
Before creating any branch, run:
git checkout <source_branch>
git pull origin <source_branch>
git checkout -b <new_branch_name>
Ref: references/policies.md
2. Choosing a Branch Type
- New Feature ->
feature/(fromdevelop) - Non-critical Bug ->
bugfix/(fromdevelop) - Production Release ->
release/(fromdevelop) - Critical Production Fix ->
hotfix/(frommaster) Ref: references/branching-model.md
Related Skills
metalagman/skill-writer
development
VerifiedTrustedCommunity
Use this skill to design, document, and structure AI agent skills for Gemini, Claude, and Codex. It provides architectural rules, directory standards, and writing best practices.
13SKILL.mdUpdated May 7, 2026
metalagman/omnidist
development
VerifiedTrustedCommunity
Use this skill to initialize, configure, and run omnidist release workflows for Go projects (`init`, `ci`, `build`, `stage`, `verify`, `publish`) including npm and uv publishing setup.
13SKILL.mdUpdated May 7, 2026
metalagman/golangci-lint-strict
development
VerifiedTrustedCommunity
Use this skill to install and use the upstream powerman/golangci-lint-strict config for an exact golangci-lint version by fetching the versioned config file unchanged.
13SKILL.mdUpdated May 7, 2026
metalagman/go-uber-style-guide
development
VerifiedTrustedCommunity
Use this skill to write, refactor, or review Go code according to the Uber Go Style Guide. It ensures strict adherence to correctness, safety, and idiomatic patterns.
13SKILL.mdUpdated May 7, 2026