New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Git Flow

by WrongStack in WrongStack/WrongStack

A skill your agent uses when committing, branching, opening a pull request, resolving conflicts, or recovering from a git mistake in any repository.

MITAuto-check passedDevelopment

Install Git Flow

skills CLI
$ npx skills add WrongStack/WrongStack --skill git-flow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install WrongStack/WrongStack git-flow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/WrongStack/WrongStack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/core/skills/git-flow .claude/skills/git-flow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
git-flow
GitHub stars
370
Token cost
~1.3k tokens
SKILL.md length
634 words
Files
2
Skills in repo
38
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when committing, branching, opening a pull request, resolving conflicts, or recovering from a git mistake in any repository.

  • Works in 7 steps: Commit, push, or open a pull request… → Look before you write: check status and… → Follow the repository's conventions.… → …
  • Opening a pull request
  • SKILL.md covers Overview, Rules, Before a commit and Messages, plus 7 more sections
  • Calls git

What it does

Git Flow is an agent skill from WrongStack/WrongStack. Use this skill when committing, branching, opening a pull request, resolving conflicts, or recovering from a git mistake in any repository. Triggers: user mentions "commit", "branch", "PR", "pull request", "merge", "rebase", "conflict", "stash", "cherry-pick", "revert", "bisect", "reflog", "force push".

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `SKILL.save.md`).

It sits in Development, covering Git workflow and Pull requests. It works with Git. The repository describes itself as: An AI coding agent that reads your code, edits files, runs commands, and reasons through bugs — across a terminal REPL, a full-screen TUI, and a browser UI, while you keep your… The licence is MIT.

When your agent uses it

  • Opening a pull request
  • Resolving conflicts
  • Recovering from a git mistake in any repository

Example prompts

  • “commit”
  • “branch”
  • “pull request”
  • “/git-flow”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Commit, push, or open a pull request only when the user asked for it. Never
  2. Look before you write: check status and both the unstaged and staged diff
  3. Follow the repository's conventions. Read recent history and any
  4. Never bypass hooks or signing (--no-verify, -n, --no-gpg-sign). When a
  5. Inspect before anything destructive — reset --hard, checkout -- ,
  6. Don't rewrite shared history. On a branch others use, add commits or revert.
  7. One concern per commit. The message says why; the diff already shows what.

What it can do on your machine

Read from SKILL.md and the folder at commit 57f6018. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Git Flow loads about 1.3k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 634 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~78
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from WrongStack/WrongStack at commit 57f6018, republished under its MIT licence (© WrongStack). 634 words, ~1,292 tokens.

Download SKILL.mdSave it as .claude/skills/git-flow/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
git-flow
description
Use this skill when committing, branching, opening a pull request, resolving conflicts, or recovering from a git mistake in any repository. Triggers: user mentions "commit", "branch", "PR", "pull request", "merge", "rebase", "conflict", "stash", "cherry-pick", "revert", "bisect", "reflog", "force push".
version
2.0.0
required-capabilities
version-control.manage

Git Workflow

Overview

Agents damage repositories in a few repeatable ways: committing files that belong to someone else, rewriting shared history, destroying uncommitted work, and bypassing hooks. This skill is the discipline that prevents those, applied on top of the repository's own conventions.

Rules

  1. Commit, push, or open a pull request only when the user asked for it. Never push on your own initiative.
  2. Look before you write: check status and both the unstaged and staged diff before every commit. Stage explicit paths — never git add -A or git add . in a worktree that may hold someone else's in-progress changes.
  3. Follow the repository's conventions. Read recent history and any CONTRIBUTING, commitlint, or PR template before choosing a message format or branch name.
  4. Never bypass hooks or signing (--no-verify, -n, --no-gpg-sign). When a hook fails, fix the cause or report it.
  5. Inspect before anything destructive — reset --hard, checkout -- <path>, clean -fd, branch -D, force pushes, rebasing pushed commits. Know what would be lost, prefer the non-destructive alternative, and ask when work could be lost.
  6. Don't rewrite shared history. On a branch others use, add commits or revert. On your own pushed branch, --force-with-lease, never --force.
  7. One concern per commit. The message says why; the diff already shows what.

Before a commit

bash
git status --short
git diff --stat           # unstaged
git diff --staged         # exactly what will be committed
git log --oneline -15     # the message style to match

Confirm the staged list contains only files changed for this task. Lockfiles, generated files, and formatting churn go in only when they belong to the change.

Messages

Match the existing style. When the repository has none:

text
fix(auth): refresh the token before it expires, not after

Requests made in the last 30 s of a token's life failed with 401 and were
retried blindly. Refreshing at 80% of the lifetime removes the window.

Refs #123

Subject: imperative, at most 72 characters, no trailing period. Body: the reason, the trade-off, and anything a reviewer can't see in the diff.

Conflicts

  1. List conflicted files and read both sides before editing.
  2. Resolve by intent, not by taking one side wholesale; keep both changes when both are valid.
  3. Remove every conflict marker, then build and run the relevant tests before staging and continuing.
  4. When resolving needs a product decision, stop and ask. git merge --abort or git rebase --abort returns to the starting point.

Recovery

SituationRecovery
Commit lost after a reset or rebasegit reflog, then git branch rescue <sha>
Committed to the wrong branch (not pushed)git branch <new-branch>, then move the wrong branch back
Need to undo a pushed commitgit revert <sha>
Uncommitted work at riskgit stash push -m "<reason>" (add -u for untracked files)
Find the commit that broke somethinggit bisect start <bad> <good>, then git bisect run <test command>
Show full SKILL.md (219 more words)Show less

Safety table

ActionSafe?Do instead
Force push to a shared branch❌Revert or add a commit
--force-with-lease to your own branch✅—
reset --hard with uncommitted work❌Stash or commit first
Amend a pushed commit❌Follow-up commit
git add -A in a shared worktree❌Stage explicit paths
Skipping hooks❌Fix what the hook reports

Pull requests

  • Title in commit-message style. Body: what changed, why, how it was verified, and the risks.
  • One reviewable concern per pull request; read the full diff yourself first.
  • To merge a clean topic branch without a merge commit: git checkout main && git merge --ff-only feature.

Anti-patterns

  • "Update stuff" commits spanning unrelated changes — split them.
  • Committing everything the worktree contains instead of the task's files.
  • Resolving a conflict by deleting the other side without reading it.
  • Treating a failing hook as an obstacle rather than a finding.

Before returning

  • Commit, push, or PR happened only because the user asked
  • Staged list reviewed; only this task's files are in it
  • Message matches the repository's convention and explains why
  • No hook bypass; no force push to shared history
  • Anything destructive was inspected first and is recoverable

Skills in scope

  • refactor-planner — for sequencing a large change into reviewable commits
  • bug-hunter — for a last pass over the diff before committing
  • output-standards — for the <nextsteps> shape in the final report

© WrongStack, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in packages/core/skills/git-flow of WrongStack/WrongStack.

  • SKILL.md
  • SKILL.save.md

Open the folder on GitHubat commit 57f6018

Compare with similar skills

Git Flow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Git Flow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Git Flow this skillWrongStack/WrongStack370—~1.3kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Git Branch Namingmakeplane/plane61k—~594Automated safety check: PassAGPL-3.0
Creating Description For Gh PRredis/jedis12k—~838Automated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Git Branch Naming

    makeplane/plane

    Names a new Git branch with a type prefix, the lowercased work item ID and a short kebab-case description, so the ID can be extracted later from the branch name.

    61k GitHub stars~594 tokensUpdated today
    DevelopmentAuto-check passed

  • Creating Description For Gh PR

    redis/jedis

    Official

    Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.

    12k GitHub stars~838 tokensUpdated today
    DevelopmentAuto-check passed

  • Create Pull Request with Work Item ID

    makeplane/plane

    Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.

    61k GitHub stars~824 tokensUpdated today
    DevelopmentAuto-check passed

More from WrongStack/WrongStack

All 38 skills in this repo

  • Design Craft

    WrongStack/WrongStack

    Design or substantially improve user-facing interfaces with a product-specific visual direction, content hierarchy, and rendered critique.

    370 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Design Critique

    WrongStack/WrongStack

    A skill your agent uses to audit an interface that already exists and say precisely why it looks generated, templated, or unfinished — a scored rubric across composition, typography, color, states…

    370 GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Mailbox Bridge

    WrongStack/WrongStack

    A skill your agent uses when external coding agents (Claude Code, Aider, custom scripts) need to participate in the project's shared WrongStack mailbox, or when a user asks to "expose the mailbox"…

    370 GitHub stars~3.9k tokensUpdated today
    Auto-check passed

  • Multi Agent

    WrongStack/WrongStack

    A skill your agent uses whenever work can be split across multiple AI agents running in parallel, or when orchestrating leader/worker patterns in WrongStack.

    370 GitHub stars~3.6k tokensUpdated today
    Auto-check passed

  • Web Platform Baseline

    WrongStack/WrongStack

    Use this skill before asserting that a CSS, HTML or accessibility capability is available, unavailable, or the right tool — it carries dated, refreshable platform facts and refuses to let stale…

    370 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Wrongstack Mailbox

    WrongStack/WrongStack

    A skill your agent uses when the user wants to communicate with WrongStack's shared project mailbox from outside WrongStack — read messages sent by WrongStack agents, send replies, broadcast to all…

    370 GitHub stars~3.5k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Git Flow

What does Git Flow do?

A skill your agent uses when committing, branching, opening a pull request, resolving conflicts, or recovering from a git mistake in any repository. Git Flow is an agent skill from WrongStack/WrongStack. Use this skill when committing, branching, opening a pull request, resolving conflicts, or recovering from a git mistake in any repository.

When should I use Git Flow?

Git Flow fits situations like: opening a pull request; resolving conflicts; recovering from a git mistake in any repository.

How do I install Git Flow in Claude Code?

Run `npx skills add WrongStack/WrongStack --skill git-flow -a claude-code`. Or copy the skill folder (packages/core/skills/git-flow in WrongStack/WrongStack) into .claude/skills/git-flow in your project. Claude Code loads it when a task matches its description.

How do I install Git Flow in Codex?

Run `npx skills add WrongStack/WrongStack --skill git-flow -a codex`. Or copy the skill folder (packages/core/skills/git-flow in WrongStack/WrongStack) into .agents/skills/git-flow in your project. Codex loads it when a task matches its description.

Can I use Git Flow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add WrongStack/WrongStack --skill git-flow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/git-flow, .gemini/skills/git-flow, .github/skills/git-flow and .opencode/skills/git-flow in your project.

What does Git Flow need to run?

Going by SKILL.md and its folder, Git Flow needs the command-line tools its instructions call (git).

Does Git Flow access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Git Flow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Git Flow use?

Git Flow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Git Flow use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Git Flow?

Skills that share tags, products or a category with Git Flow: Finishing a Development Branch (obra/superpowers, 296k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars) and Git Branch Naming (makeplane/plane, 61k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Git Flow?

WrongStack (a GitHub organization) maintains it in WrongStack/WrongStack, which has 370 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on October 7, 2026.

Source: WrongStack/WrongStack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.