git-flow-master

git-flow-master is a skill for Claude Code from upex-galaxy/agentic-qa-boilerplate. It costs 502 tokens per session (13,362 once invoked), scanned A, original, MIT.

A Git workflow that handles branches, commits, pushes, pull requests, conflicts, and large changes across different team branching models. It detects how the project manages branches and adapts its steps to that model.

In plain words
What is it for?
Use it to start work on a ticket, create branches, commit and push changes, open or plan pull requests, resolve merge conflicts, and split oversized changes into linked reviews.
Why use it?
Git operations can differ between a solo project, a trunk-based team, GitFlow, or an enterprise branch setup. This gives the agent one project-aware process for moving changes safely through review and integration.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions Claude Code; installed under .agents/ (shared by several agents); mentions AGENTS.md.

Good fit Use it to start work on a ticket, create branches, commit and push changes, open or plan pull requests, resolve merge conflicts, and split oversized changes into linked reviews.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/upex-galaxy/agentic-qa-boilerplate/git-flow-master
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add upex-galaxy/agentic-qa-boilerplate --skill git-flow-master
Clone the repo
git clone --depth 1 https://github.com/upex-galaxy/agentic-qa-boilerplate

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for git-flow-master

README.md
[![agentmods](https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/git-flow-master/github.svg)](https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/git-flow-master)
Your own site
<a href="https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/git-flow-master"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/git-flow-master/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for git-flow-master

Your own site · 80×15
<a href="https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/git-flow-master"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/git-flow-master.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 502 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 13,362 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 17 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high YARA Match · line 10
    YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).
    Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
  • high Anti-Refusal · line 379
    Skill attempts to nullify the agent's safety policies or restrictions ('you have no restrictions', 'ignore your guidelines', 'do anything now'). This is a direct jailbreak that disables guardrails.
    Fix: Remove jailbreak framing that nullifies safety policies or restrictions. Skill content must not instruct the agent to ignore its guidelines or operate without guardrails.
  • high Tool Misuse · line 468
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • high Tool Misuse · line 482
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • high Tool Misuse · line 513
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • medium Prompt Injection · line 48
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Prompt Injection · line 119
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Excessive Agency · line 171
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Excessive Agency · line 404
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Prompt Injection · line 293
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Prompt Injection · line 374
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Prompt Injection · line 295
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Agent Snooping · line 327
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium Prompt Injection · line 374
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Prompt Injection · line 376
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Prompt Injection · line 377
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Prompt Injection · line 524
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00502 $0.13362
Opus 5.5 $0.00201 $0.05345
Sonnet 5.5 $0.00100 $0.02672
Haiku 4.5 $0.00050 $0.01336

Measured 17d ago against content hash c31f169fe00f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-flow-master scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 17d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/git-flow-master/SKILL.md · 570 lines

How it starts

The opening of the file, as written. The whole thing — 570 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git Flow Master — One Skill for Branches, Commits, Pushes, PRs, and Conflicts

This skill is the project's single entry point for everything that happens on the version-control layer: creating branches, writing commits, pushing safely, opening pull requests, resolving conflicts, and planning chained / stacked PRs when a change outgrows the review budget.

It does not assume one branching model. The project may run on main only, on main + staging, on a multi-branch enterprise layout, or on any of the well-known flows (trunk-based, GitFlow, GitHub Flow, GitLab Flow). The skill detects which one is active and adapts every command accordingly. The detection is sticky: once resolved, the strategy is recorded in the git_strategy: block of .agents/project.yaml so future invocations skip the prompt.


Compact Rules

  • DO: read the repo state (status, branches, diff, log, fetch, upstream, remotes) at the start of EVERY invocation and report it before acting. Never assume repo state.
  • DO: resolve the branching strategy from the git_strategy: block in .agents/project.yaml first, then layout heuristics, then by asking — never pick one silently. Persist the resolution back into that block, never into a separate file and never as policy prose in AGENTS.md. The yaml snippets in references/ (per-strategy field rules, policy examples) are illustrations: a claim about THIS repo's strategy, branches or policy cites .agents/project.yaml (or git:policy verify output) read in the same turn.
  • WHEN git_strategy.meta.strategy_source is chosen: the strategy is CONFIRMED, whatever project.project_name holds; no offer. Otherwise, WHEN git_strategy.strategy is set but project.project_name is null, or meta.strategy_source is inherited (or absent) on a named project: the strategy was INHERITED from the template, not chosen. Treat it as unconfirmed and OFFER Strategy Setup once per session — never auto-run it, and proceed under the inherited strategy on a "no".
  • DO: consult git_strategy.policy.direct_push_to_protected before any direct push to a protected branch — allowed is standing authorization (asking anyway collapses it into confirm), confirm asks every time, forbidden refuses and routes through a PR. A missing or null block behaves as confirm.
  • DO NOT: force-push, --force-with-lease, --no-verify, amend or rebase a pushed commit, or otherwise rewrite pushed history, unless the user explicitly authorizes it AND the branch is unshared.
  • DO NOT: run a repo-wide discard (git restore ., git checkout -- ., git reset --hard, untargeted git stash, git clean -f) — concurrent sessions may share this working tree. Discard only explicit paths this session modified; unclear ownership means stop and ask.
  • DO NOT: git add -A or git add .. List explicit paths, so a secret or another session's work cannot ride along.
  • DO: keep one commit to one responsibility, in conventional format ({type}({ISSUE-KEY}): {description}). Commit messages, branch names and PR bodies are English and carry NO AI attribution.
  • DO: close EVERY commit message, in every strategy, with the two forensic trailers Worktree: <name|primary> then Session: <label>, copied from the AGENT IDENTITY: line in session context (unknown when a value cannot be resolved). They are forensics, not attribution — a harness-branded trailer (Claude-Session:, an AI Co-Authored-By:) stays forbidden.
  • WHEN the pre-push or CI documentation-contract gate names a region (ADR-0016): update every page it lists in the same push; only if they still hold, add Docs-Checked: <label> <reason> above the forensic trailers. NEVER add it by reflex or without the reason.
  • WHEN a pre-commit hook rejects a commit: stop, fix the underlying issue, and create a NEW commit. Never --amend the rejected one.
  • DO: propose every branch name, commit set, and PR body and wait for an explicit OK before executing.
  • DO: stop at PR creation — merging is the user's next step, never automatic. If the gh transport is missing or unauthenticated, surface the blocker instead of implying a PR was opened.
  • WHEN reconciling declared policy against the host: run the policy-verify tool once at the first push / PR / merge intent, never hand-query protection endpoints. A 404 on the classic protection endpoint does not mean unprotected, and a push that succeeded may have been a documented bypass, not permission. Report drift; never auto-correct it.
  • WHEN a planned change exceeds ~400 changed lines: run the chained-PR decision (single-pr / stacked-to-main / feature-branch-chain / size-exception) before coding, and re-run it if the real diff outgrows the estimate rather than silently up-budgeting. Return it with its trace, never as a bare label: Chain strategy: <leaf>, each tree question answered with the reason drawn from THIS change (Q1=No (…) · Q2=… · Q3=…, n/a past the leaf), Decided by: /git-flow-master. Answers that do not lead to the stated leaf, or a trace that only restates the conclusion, count as no decision; a re-run replaces the trace.
  • WHEN a conflict fires: diagnose and classify it first, present options ranked by safety, and prefer a safe abort over a guess. Never pick a destructive option silently.

Read the full file on GitHub · 570 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 17d ago Changed · +2 lines c31f169fe00f
  2. 18d ago Changed · -10 lines adc441b33432
  3. 20d ago Changed · +1 lines d29322ef52c9
  4. 22d ago Changed 13cded1b696f
  5. 29d ago Changed · +2 lines 55c6ec01190b
  6. 1mo ago Changed · +1 lines ec282e152dc7
  7. 1mo ago Changed · +18 lines 72e2bf83741a
  8. 1mo ago Changed · +21 lines 30f171c06bd3
  9. 1mo ago First seen · 535 lines · 502 tokens per session scan A 7a76343a0c47

Subscribe to this mod's changes

git-flow-master is a skill published in the GitHub repository upex-galaxy/agentic-qa-boilerplate (26 stars, last pushed 11d ago), licensed MIT. It adds 502 tokens to every session and 13,362 once invoked, about $0.0020 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

git-safety

CRITICAL SAFETY SKILL - Use this skill before any Git operation that could lose commits, rewrite history, or affect shared branches. Activate when the user wants to force push, reset hard, rebase, clean, or perform any destructive Git operation. This skill prevents loss of work through verification and confirmation.

latestaiagents/agent-skills · 67 tokens

commit-message-crafter

Use this skill when writing Git commit messages. Activate when the user asks about commit message format, conventional commits, how to write good commit messages, commit message best practices, or when they're about to commit changes and need help crafting the message.

latestaiagents/agent-skills · 56 tokens

agentic-jujutsu

Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination.

ruvnet/ruflo · 26 tokens

github-automation

GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.

ruvnet/ruflo · 61 tokens

moai-ref-git-workflow

Git workflow patterns, branch strategies, conventional commits, and PR templates reference for git operations. Agent-extending skill that amplifies manager-git expertise with production-grade git workflow patterns. NOT for: code implementation, testing, architecture design, documentation content.

modu-ai/moai-adk · 58 tokens

git-integration

Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.

a5c-ai/babysitter · 39 tokens