git-workflow

git-workflow is a skill for Claude Code from povvo/claudikins-kernel. It costs 54 tokens per session (3,207 once invoked), scanned A, original, MIT.

A workflow guide for breaking development plans into isolated tasks and reviewing them in controlled batches. A Git branch is a separate line of project history, and the guide uses one branch per task to keep changes apart.

In plain words
What is it for?
Use it when running the execute command, dividing plans into tasks, choosing batch sizes, setting up two-stage reviews, or handling agents that get stuck or fail.
Why use it?
It prevents parallel agents from polluting one another’s work, encourages manageable batches, and adds human checkpoints before changes are combined.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the TodoWrite tool.

Part of the claudikins-kernel plugin — 4 skills, 4 commands, 7 agents, 8 hooks shipped together

Good fit Use it when running the execute command, dividing plans into tasks, choosing batch sizes, setting up two-stage reviews, or handling agents that get stuck or fail.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/povvo/claudikins-kernel/git-workflow
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 povvo/claudikins-kernel --skill git-workflow
Clone the repo
git clone --depth 1 https://github.com/povvo/claudikins-kernel

Made for: Claude Code.

Or install claudikins-kernel, the plugin that ships this one along with the rest of its 4 skills, 4 commands, 7 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.

agentmods badge for git-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/povvo/claudikins-kernel/git-workflow/github.svg)](https://agentmods.dev/skills/povvo/claudikins-kernel/git-workflow)
Your own site
<a href="https://agentmods.dev/skills/povvo/claudikins-kernel/git-workflow"><img src="https://agentmods.dev/badge/skills/povvo/claudikins-kernel/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.

agentmods 80×15 button for git-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/povvo/claudikins-kernel/git-workflow"><img src="https://agentmods.dev/badge/skills/povvo/claudikins-kernel/git-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,207 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.03207
Opus 5.5 $0.00022 $0.01283
Sonnet 5.5 $0.00011 $0.00641
Haiku 4.5 $0.00005 $0.00321

Measured 2mo ago against content hash 23b70f74a15f, 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 2mo 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.

skills/git-workflow/SKILL.md · 383 lines

How it starts

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

Git Workflow Methodology

When to use this skill

Use this skill when you need to:

  • Run the claudikins-kernel:execute command
  • Decompose plans into executable tasks
  • Set up two-stage code review
  • Decide batch sizes and checkpoints
  • Handle stuck agents or failed tasks

Core Philosophy

"I'd use 5-7 agents per SESSION, not 30 per batch." - Boris

Execution is about isolation, verification, and human checkpoints. Not speed.

The Six Principles

  1. One task = one branch - Isolation prevents pollution
  2. Fresh context per task - context: fork gives a clean slate
  3. Two-stage review - Spec compliance first, then code quality
  4. Human checkpoints between batches - Not between individual tasks
  5. Commands own git - Agents never checkout/merge/push
  6. Features are the unit - Batch at feature level, not task level

Batch Size Guidance (GOSPEL)

Wrong: 30 agents for 10 tasks (3 per task micro-management) Right: 5-7 agents total (feature-level batches)

Scenario Wrong Right
10 tasks, 5 features 30 micro-task agents 5-7 feature agents
Simple refactor 10 agents for tiny changes 1-2 feature agents

Default --batch 1 is correct. Features are the unit of work.

Task Decomposition

From a plan, extract tasks that are:

Quality Definition Example
Atomic Completable in one agent session "Add auth middleware" not "Build auth system"
Testable Has measurable acceptance criteria "Returns 401 for invalid token"
Independent Minimal dependencies on other tasks Can be reviewed in isolation
Right-sized Not too small (noise) or large (context death) 50-200 lines of changes

Read the full file on GitHub · 383 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. 2mo ago First seen · 383 lines · 54 tokens per session scan A 23b70f74a15f

Subscribe to this mod's changes

git-workflow is a skill published in the GitHub repository povvo/claudikins-kernel (127 stars, last pushed 6mo ago), licensed MIT. It adds 54 tokens to every session and 3,207 once invoked, about $0.0002 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

git-workflow compared with skills from other repositories

git-workflow next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
git-workflowpovvo/claudikins-kernelSkill1276mo agoMITA54Claude Code
OCR Review-to-Approval Loopspencermarx/open-code-reviewSkill3825d agoApache-2.0A213Claude Code
merge-quizorenluxy/fable-methodSkill21mo agoMITA78Claude Code
pull-requestjon-greeff-katsini/outside-daveSkill21mo agononeA86Claude Code
prumputun/cc-thingzSkill4933d agoMITA51Claude Code
pr-threads-addressposit-dev/skillsSkill5544d agoMITA48Claude Code
deploy-landedavelikiy/great_ctoSkill1122d agoMITA103Claude Code