agentleFS
lautioliverlautioliver/barrilete-kit/.claude/skills/git-workflow/SKILL.md

git-workflow

Skill6 starsChanged 7 days agoMITView on GitHub

Branch, commit and PR flow of this repo. Use whenever you create branches, commits, pushes or pull requests.

  • Commits and pushes

187 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use squad-commands, ci-cd-pipelines and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Microsoft AzureSkill

    squad-commands

    Categorized catalog of common Squad operations. Coordinator reads this file and presents it as an interactive menu when the user asks for available commands or help.

    Also in 5 projects that use this

  • harrissohail6Skill

    ci-cd-pipelines

    CI/CD pipeline design and implementation. Auto-activates when discussing deployment, automation, or pipelines.

    Also in 6 projects that use this

  • Microsoft AzureSkill

    architectural-proposals

    How to write comprehensive architectural proposals that drive alignment before code is written

    Also in 4 projects that use this

  • GitHubSkill

    e2e-template-testing

    End-to-end validation of coordinator and agent template changes

    Also in 3 projects that use this

  • GitHubSkill

    notification-routing

    Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding

    Also in 3 projects that use this

  • frostneySkill

    native-nostalgia-stack

    Applies the user's FreePascal toolchain and its build, formatting, hook, and test contracts while leaving project-specific mechanics local. Use when scaffolding or working in a FreePascal project that follows this toolchain.

    Also in 3 projects that use this

  • +5 more from Azure
  • +1 more from github

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 164 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If there is no issue, ask whether to open one (skill create-issue) before inventing the number.

    line 14
  2. Very specific:

    Freeze: Only fixes for that version go into release/vX.Y.Z, through a PR based on release/vX.Y.Z.

    line 22
  3. Distinctive:

    Never push directly to the trunk branches.

    line 46
  4. Very specific:

    If it changes a rule from an ADR, audit or plan: label business-logic and explain it in "Business logic affected".

    line 50

“Common” is measured: kept by at least 6 in 10 of the 164 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Git workflow — <PROJECT>

Details in docs/github-naming-convention.md. Mandatory summary in AGENTS.md.

Branches

  • <BRANCH_RULE> Create the working branch from an up-to-date <BASE_BRANCH>.
  • Name: claude/<issue-no>-<description> (agent) or <type>/<issue-no>-<description> (person). Lowercase, numbers and hyphens only.
  • If there is no issue, ask whether to open one (skill create-issue) before inventing the number.
<!-- releases:start -->

Releases (develop → release/* → main)

To publish without touching production until the version is tested:

  1. Cut the release from an up-to-date develop: release/vX.Y.Z (SemVer, see convention §8). From then on develop keeps receiving work for the next version.
  2. Freeze. Only fixes for that version go into release/vX.Y.Z, through a PR based on release/vX.Y.Z. No new features.
  3. Test the release in the staging environment before merging.
  4. Publish: PR release/vX.Y.Z → main. On merge, tag vX.Y.Z on main.
  5. Return to develop: PR main → develop (or release/vX.Y.Z → develop) so the release fixes are not lost. Then the release/* branch is deleted.

Hotfix (something broken in production):

  • It comes off main: hotfix/<issue-no>-<description>, PR to main, PATCH tag (vX.Y.Z+1).
  • It always goes back to develop, and to the open release/* if there is one. If it does not go back, the bug reappears in the next version.

An agent does not cut releases, merge to main or create tags unless explicitly asked.

<!-- releases:end -->

Commits

  • <type>(<scope>): <description> — imperative, lowercase, no period, ≤ 72 characters. Types in English; the description in <COMMIT_LANG>.
<!-- template:start -->
  • In this repo (the template itself) the descriptions are in Spanish.
<!-- template:end -->
  • One commit = one logical change. If it touches several scopes: no scope, or split.
  • Breaks compatibility: feat(api)!: … + footer BREAKING CHANGE: ….

Pull requests

  1. Never push directly to the trunk branches. Everything goes in through a PR.
  2. Title with the same format as a commit.
  3. Body from .github/pull_request_template.md: What changes / Why / Business logic affected / How to test it / Closes #n.
  4. Labels: exactly one type: (claude/ branches do not get it automatically: set it yourself), 1–2 area:, no priority:. Only labels from .github/labels.yml.
  5. If it changes a rule from an ADR, audit or plan: label business-logic and explain it in "Business logic affected".
gh pr create --base <BASE_BRANCH> --title "fix(api): …" --body-file <file> --label "type:bug" --label "area:api"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.