git-workflow

git-workflow is a command for Claude Code from HermeticOrmus/LibreUIUX-Claude-Code. It costs 0 tokens per session (2,002 once invoked), scanned A, original, MIT.

A coordinated Git workflow that checks code, runs tests, verifies deployment readiness, and prepares a pull request. Git is a version-control system, and a pull request is a proposed set of changes for review.

In plain words
What is it for?
Use it to run code review and automated tests, follow Conventional Commits, check production readiness, support trunk-based or feature-branch work, and create draft or squashed pull requests.
Why use it?
It helps catch quality, test, and release problems before changes are committed, pushed, or merged into a shared branch.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

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.

agentmods
npx agentmods add commands/hermeticormus/libreuiux-claude-code/git-workflow
Clone the repo
git clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-Code

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-workflow

README.md
[![agentmods](https://agentmods.dev/badge/commands/hermeticormus/libreuiux-claude-code/git-workflow.svg)](https://agentmods.dev/commands/hermeticormus/libreuiux-claude-code/git-workflow)
Your own site
<a href="https://agentmods.dev/commands/hermeticormus/libreuiux-claude-code/git-workflow"><img src="https://agentmods.dev/badge/commands/hermeticormus/libreuiux-claude-code/git-workflow.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,002 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00000 $0.02002
Opus 5 $0.00000 $0.01001
Sonnet 5 $0.00000 $0.00400
Haiku 4.5 $0.00000 $0.00200

Measured 2d ago against content hash dcaa5f768a93, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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.

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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

plugins/git-pr-workflows/commands/git-workflow.md · 118 lines

How it starts

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

Complete Git Workflow with Multi-Agent Orchestration

Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern git best practices including Conventional Commits, automated testing, and structured PR creation.

[Extended thinking: This workflow coordinates multiple specialized agents to ensure code quality before commits are made. The code-reviewer agent performs initial quality checks, test-automator ensures all tests pass, and deployment-engineer verifies production readiness. By orchestrating these agents sequentially with context passing, we prevent broken code from entering the repository while maintaining high velocity. The workflow supports both trunk-based and feature-branch strategies with configurable options for different team needs.]

Configuration

Target branch: $ARGUMENTS (defaults to 'main' if not specified)

Supported flags:

  • --skip-tests: Skip automated test execution (use with caution)
  • --draft-pr: Create PR as draft for work-in-progress
  • --no-push: Perform all checks but don't push to remote
  • --squash: Squash commits before pushing
  • --conventional: Enforce Conventional Commits format strictly
  • --trunk-based: Use trunk-based development workflow
  • --feature-branch: Use feature branch workflow (default)

Phase 1: Pre-Commit Review and Analysis

1. Code Quality Assessment

  • Use Task tool with subagent_type="code-reviewer"
  • Prompt: "Review all uncommitted changes for code quality issues. Check for: 1) Code style violations, 2) Security vulnerabilities, 3) Performance concerns, 4) Missing error handling, 5) Incomplete implementations. Generate a detailed report with severity levels (critical/high/medium/low) and provide specific line-by-line feedback. Output format: JSON with {issues: [], summary: {critical: 0, high: 0, medium: 0, low: 0}, recommendations: []}"
  • Expected output: Structured code review report for next phase

Read the full file on GitHub · 118 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. 2d ago First seen · 118 lines · 0 tokens per session scan A dcaa5f768a93

Subscribe to this mod's changes

git-workflow is a command published in the GitHub repository HermeticOrmus/LibreUIUX-Claude-Code (101 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,002 tokens. 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-09-03.