gitflow SKILL.md skillA

gitflow from jorgecostamacia/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add jorgecostamacia/skills/gitflow@git:20261109.86064cf

Pins git:20261109.86064cf in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
jorgecostamacia/skills
Path
plugins/gitflow/SKILL.md
Versions recorded
5
Latest version
git:20261109.86064cf, committed Nov 9, 2026
First version recorded
Oct 26, 2026
Size
6,826 bytes
Repository stars
2
License
MIT

A GitFlow workflow for branches and releases. Use this whenever the work touches branching or releasing in a repo that follows it — starting or finishing a feature, bugfix, release, or hotfix; creating a release/hotfix branch; bumping a version; tagging (`vX.Y.Z`); merging into develop or main; or publishing a new version — even when the user doesn't say "gitflow" explicitly (e.g. "cut a release", "ship 2.1.0", "merge this to main", "tag the version", "start a feature for X"). It encodes…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# GitFlow

This mirrors the [`gitflow-vscode`](https://github.com/JorgeCostaMacia/gitflow-vscode) extension; when in doubt, its source is the reference. Follow it **from the start** of any branching/release work. Never improvise direct `develop→main` merges or bolt a tag on at the end.

## Branch model

| Type | Branch | Starts from | Merges into | Tagged |
|---|---|---|---|---|
| Feature | `feature/<name>-<timestamp>` | develop | develop | no |
| Bugfix | `bugfix/<name>-<timestamp>` | develop | develop | no |
| Release | `release/<version>` | develop | develop **and** main | `v<version>` |
| Hotfix | `hotfix/<version>` | main | develop **and** main | `v<version>` |

Branch prefixes are **only** `feature` / `bugfix` / `release` / `hotfix`. Never use `chore/` or anything else as a branch prefix (`chore` is a Conventional-Commits *message* type, not a GitFlow branch). A hotfix merges into `develop` even while a release branch is open (the original model would merge it into that release instead): that is what the extension does; an open release branch that needs the fix merges `develop` into itself by hand.

## Validation (reject, don't sanitize)
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5ha3trmaafp6gunm/f8517dd7ee91ef88f436f1969309cfdbc5e514da83100e7e5e7d2e100fbf1d69.json

Then /plugin install gitflow@markdownregistry-5ha3trmaafp6gunm in Claude Code. It installs git:20261109.86064cf, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add jorgecostamacia/skills/gitflow@sha256:f8517dd7ee91ef88

The line at the top of this page pins the label git:20261109.86064cf, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_5ha3trmaafp6gunm.svg)](https://markdownregistry.com/a/art_5ha3trmaafp6gunm)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in jorgecostamacia/skills/gitflow since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of gitflow from somewhere else? Ask it: where did my gitflow come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 5 versions of this file, between Oct 26, 2026 and Nov 9, 2026, about one every 3 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261109.86064cf latest2026-11-09 86064cf 6,826 BA view · diff
git:20261026.fee98c82026-10-26 fee98c8 6,687 BA view · diff
git:20261026.664268c2026-10-26 664268c 6,226 BA view · diff
git:20261026.57bc3ba2026-10-26 57bc3ba 6,220 BA view · diff
git:20261026.2907f7b2026-10-26 2907f7b 5,410 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (6826 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

jorgecostamacia/skills · 2 stars · license MIT · pushed 2026-11-18 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_5ha3trmaafp6gunm
GET https://markdownregistry.com/api/v1/resolve?ref=jorgecostamacia/skills/gitflow
GET https://markdownregistry.com/api/v1/blob/f8517dd7ee91ef88f436f1969309cfdbc5e514da83100e7e5e7d2e100fbf1d69

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from jorgecostamacia/skills

jorgecostamacia-agent-skills Plugin marketplace
jorgecostamacia/skills · .claude-plugin/marketplace.json · Agent skills for software engineering: stack-agnostic principles (SOLID, clean architecture, DDD, testing, logging…
git:20261118.e2dbf8e · audit A · 2 stars
AGENTS.md AGENTS.md file
jorgecostamacia/skills · AGENTS.md
git:20261118.bf6b205 · audit A · 2 stars
CLAUDE.md CLAUDE.md file
jorgecostamacia/skills · CLAUDE.md
git:20260630.eb9757d · audit B · 2 stars
astro SKILL.md skill
jorgecostamacia/skills · plugins/astro/SKILL.md · How a static website is built with Astro and served as plain files. Use when creating or maintaining an Astro site, or…
git:20261118.e2dbf8e · audit B · 2 stars
build-dotnet SKILL.md skill
jorgecostamacia/skills · plugins/build-dotnet/SKILL.md · How a .NET repository is built, versioned and restored — the house conventions on top of MSBuild and NuGet. Use when…
git:20261108.c2f94bf · audit A · 2 stars
bus-dotnet SKILL.md skill
jorgecostamacia/skills · plugins/bus-dotnet/SKILL.md · The .NET realization of the messaging principles with the JorgeCostaMacia.Bus family — what is the same whatever the…
git:20261108.057c33b · audit A · 2 stars
bus-kafka-dotnet SKILL.md skill
jorgecostamacia/skills · plugins/bus-kafka-dotnet/SKILL.md · How the services use the Kafka transport of the JorgeCostaMacia.Bus family — the decisions on top of the library (see…
git:20261109.539d918 · audit A · 2 stars
changelog SKILL.md skill
jorgecostamacia/skills · plugins/changelog/SKILL.md · How a repository keeps its changelog: one CHANGELOG.md at the root listing, newest first, only what whoever consumes…
git:20261116.2cacb7d · audit A · 2 stars
clean-architecture-dotnet SKILL.md skill
jorgecostamacia/skills · plugins/clean-architecture-dotnet/SKILL.md · The .NET realization of clean architecture (see the `clean-architecture` skill for the principles): how a .NET service…
git:20261108.c2f94bf · audit A · 2 stars
clean-architecture SKILL.md skill
jorgecostamacia/skills · plugins/clean-architecture/SKILL.md · Clean architecture layering with hexagonal (ports & adapters) boundaries — stack-agnostic and canon-anchored…
git:20261026.fee98c8 · audit A · 2 stars
code-style-dotnet SKILL.md skill
jorgecostamacia/skills · plugins/code-style-dotnet/SKILL.md · How C# is written — the house style every .NET repo enforces. Use when writing, generating or reviewing any C# code…
git:20261108.c2f94bf · audit A · 2 stars
code-style-md SKILL.md skill
jorgecostamacia/skills · plugins/code-style-md/SKILL.md · How Markdown is written in every repository — README, AGENTS, CONTRIBUTING, CHANGELOG, SECURITY, a skill's SKILL.md…
git:20261116.b190342 · audit A · 2 stars

Every file in jorgecostamacia/skills

Other files named gitflow

gitflow SKILL.md skill
mindrally/skills · gitflow/SKILL.md · Branching, merging, versioning, and release conventions for the Gitflow workflow, covering main/develop branches…
git:20261008.7682ca7 · audit A · 308 stars
gitflow SKILL.md skill
mgiovani/cc-arsenal · skills/gitflow/SKILL.md · Manage a gitflow branching workflow, starting and finishing feature,
v1.0.0 · audit A · 8 stars

Browse by kind, by grade A, or by owner.