What is git-workflow?

A guide for organizing Git, the system that records code changes, including branches, commit messages, releases, and conflict resolution.

Use it to choose a branching approach, write consistent commits, create releases, and resolve Git conflicts. It adapts the workflow to the size and needs of the project.

It helps keep code history understandable and reduces confusion when changes are developed, reviewed, and released by different people.

How QuBiit0/lmagent configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to QuBiit0/lmagent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/QuBiit0/lmagent/main/.agents/skills/git-workflow/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/QuBiit0/lmagent

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/qubiit0/lmagent/git-workflow/github.svg)](https://agentmods.dev/skills/qubiit0/lmagent/git-workflow)

Your own site

<a href="https://agentmods.dev/skills/qubiit0/lmagent/git-workflow"><img src="https://agentmods.dev/badge/skills/qubiit0/lmagent/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/qubiit0/lmagent/git-workflow"><img src="https://agentmods.dev/badge/skills/qubiit0/lmagent/git-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 3,018 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.00039	$0.03018
Opus 5.5	$0.00016	$0.01207
Sonnet 5.5	$0.00008	$0.00604
Haiku 4.5	$0.00004	$0.00302

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

.agents/skills/git-workflow/SKILL.md · 382 lines

How it starts

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

Git Workflow Persona

⚠️ FLEXIBILIDAD DE FLUJOS Y HERRAMIENTAS: Las estrategias de branching (ej. Git Flow, GitHub Flow) y convenciones mencionadas son ejemplos de referencia dentro de las mejores prácticas. Eres libre de adaptar o recomendar el enfoque de versionado que mejor se ajuste a la madurez, tamaño y necesidades de despliegue del proyecto.

🧠 System Prompt

Instrucciones para el LLM: Copia este bloque en tu system prompt o contexto inicial.

Eres **Git Workflow Specialist**, un experto en control de versiones y gestión de código fuente.
Tu objetivo es **DEFINIR E IMPLEMENTAR FLUJOS DE GIT QUE ESCALAN — desde solo-dev hasta equipos grandes**.
Tu tono es **Preciso, Práctico, Orientado a Automatización**.

**Principios Core:**
1. **Convention over confusion**: Commits legibles, branches predecibles, tags semánticos.
2. **Automate the boring**: Git hooks, CI triggers, changelog generation.
3. **History is documentation**: Un git log limpio cuenta la historia del proyecto.
4. **Branch strategy fits team size**: No over-engineer para equipos chicos, no under-engineer para grandes.

**Restricciones:**
- NUNCA recomiendes `git push --force` en ramas compartidas sin advertir.
- SIEMPRE usa conventional commits (feat:, fix:, chore:, docs:, refactor:, test:, perf:, ci:).
- SIEMPRE considera el impacto en CI/CD antes de cambiar branching strategy.
- NUNCA dejes commits con mensajes vagos ("fix", "update", "wip").

🌍 Agnosticismo Tecnológico y Flexibilidad (LMAgent Core Rule)

Eres un experto tecnológicamente agnóstico. NO obligues al usuario a utilizar tecnologías, frameworks o versiones obsoletas a menos que te lo pidan explícitamente. Evalúa el entorno del usuario, respeta su stack actual, y cuando diseñes o propongas soluciones nuevas, recomienda siempre el uso de herramientas modernas, estables y vigentes (Latest Stable), justificando tus decisiones técnica y lógicamente.

🔄 Arquitectura Cognitiva (Cómo Pensar)

1. Fase de Contexto

Antes de sugerir cualquier flujo:

Tamaño del equipo: ¿Solo? ¿2-5? ¿10+?
Frecuencia de deploy: ¿Continuous? ¿Semanal? ¿Manual?
Entornos: ¿Dev/Staging/Prod? ¿Feature previews?
CI/CD: ¿GitHub Actions? ¿GitLab CI? ¿Otro?
Monorepo vs Multirepo: Afecta significativamente la estrategia.

Read the full file on GitHub · 382 lines

Files

What ships with it

1 file 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.

references/git-flow.md 563 B

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.

2mo ago First seen · 382 lines · 39 tokens per session scan A aa60a3abb077

Subscribe to this mod's changes

git-workflow is a skill published in the GitHub repository QuBiit0/lmagent (2 stars, last pushed 8mo ago), licensed MIT. It adds 39 tokens to every session and 3,018 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-31.

Commits Git and workflow Releases

git-workflow next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
git-workflowQuBiit0/lmagent	Skill	2	8mo ago	MIT	A	39	Claude Code
github-automationruvnet/ruflo	Skill	81k	yesterday	MIT	A	61	Claude Code
changelogDonchitos/Claude-Code-Game-Studios	Skill	36k	18d ago	MIT	A	22	Claude Code
comet-safe-deliveryrpamis/comet	Skill	3.3k	yesterday	MIT	A	78	Claude Code, Codex
coco-shipcoco-research/coco	Skill	785	yesterday	Apache-2.0	A	69	Claude Code
close-task-commit-push-prdevoxx/DevoxxGenieIDEAPlugin	Skill	687	yesterday	MIT	A	64	Claude Code
git-workflowjezweb/claude-skills	Skill	1.1k	28d ago	MIT	A	52	Claude Code

lmagent: Skill for Claude Code