What is git-workflow?

A rule-management workflow for setting and changing a team's Git practices, including branches, commits, pull requests, tickets, and enforcement. It stores those rules in project configuration files and changes them through scripts.

It helps teams set up a Git workflow for a new or existing repository and later review or change those rules.

It prevents undocumented or inconsistent workflow changes. It also records the team's decisions and uses repository history as evidence when proposing initial rules.

git-workflow — Skill for Claude Code and Codex by Eliyce/paqad-ai

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 Eliyce/paqad-ai --skill git-workflow

Clone the repo

git clone --depth 1 https://github.com/Eliyce/paqad-ai

Made for: Claude Code, Codex.

Or install paqad, the plugin that ships this one along with the rest of its 125 skills, 9 agents, 8 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/eliyce/paqad-ai/git-workflow/github.svg)](https://agentmods.dev/skills/eliyce/paqad-ai/git-workflow)

Your own site

<a href="https://agentmods.dev/skills/eliyce/paqad-ai/git-workflow"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/git-workflow/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/eliyce/paqad-ai/git-workflow"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/git-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 144 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,784 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00144	$0.01784
Opus 5.5	$0.00058	$0.00714
Sonnet 5.5	$0.00029	$0.00357
Haiku 4.5	$0.00014	$0.00178

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

Security

Grade A, and why

git-workflow 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 2d ago.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/apply.mjs, scripts/change.mjs, scripts/check.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

runtime/base/skills/git-workflow/SKILL.md · 115 lines

How it starts

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

Rules

Change .paqad/configs/git-workflow/ only through this skill's scripts. Never edit those files with Edit, Write or a shell command: paqad blocks direct edits, and a change that skips the scripts is never checked or recorded.
Base every proposal on what the scripts found. When history is mixed, ask the team; don't pick for them. When something can't be read, say it's unknown, never that it doesn't exist.
Record every answer as a decision, so the team can see later why each rule exists.

What It Does

One skill is in charge of .paqad/configs/git-workflow/, the five files that hold this team's rules for tickets, branches, commits, pull requests and how strictly they're checked (tickets.yaml, branches.yaml, commits.yaml, pull-requests.yaml, enforcement.yaml). It handles three cases:

first setup from the repo's history, during create documentation
a new project with no history
any later change the team asks for

The scripts read git and gh, propose with evidence, validate and write. Your job is only to ask the team and explain.

Use This When

create documentation reaches its git workflow step (first setup).
The repo has no remote, fewer than 20 main-line commits, or no branches besides the base (the scripts report mode: new-project).
Someone asks to change how branches are named, where changes start, how commits or PR titles are written, which labels or reviewers a PR gets, which tickets a change links, how ticket statuses move, or how strictly any of that is checked. This applies whatever workflow the request routed to, and even when the request doesn't mention the config.

Inputs

project_root (path, optional): defaults to cwd.
flow (string, optional): first-setup, new-project or change. Picked from the request when not given.

Procedure

Every script prints JSON on stdout, never prompts, and exits 0 on success, 1 on invalid input or config, and 2 when git or gh failed.

Read the full file on GitHub · 115 lines

Files

What ships with it

13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2d ago First seen · 115 lines · 144 tokens per session scan A 366db4ff198b

Subscribe to this mod's changes

git-workflow is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed today), licensed MIT. It adds 144 tokens to every session and 1,784 once invoked, about $0.0006 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-11-04.

Claude Code Commits Git and workflow agent-framework ai ai-agents cli codex

git-workflow next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
git-workflowEliyce/paqad-ai	Skill	8	today	MIT	A	144	Claude Code, Codex
lore-commitInsajin/autopus-adk	Skill	111	1mo ago	MIT	A	20	Claude Code, Codex
autofix-prQwenLM/qwen-code	Skill	29k	yesterday	Apache-2.0	A	141	Claude Code
cw-landHmbown/Codewhale	Skill	41k	1mo ago	MIT	A	44	Claude Code, Codex
git-commitUfoMiao/zcf	Skill	6.1k	8d ago	MIT	A	41	Claude Code
git-mastercode-yeongyu/lazycodex	Skill	3.9k	yesterday	MIT	A	93	Codex
ghbubbuild/bub	Skill	1.7k	yesterday	Apache-2.0	A	96	Claude Code, Codex