Skip to main content
rule CX Codex

git-workflow — Claude Code rule: what it does, how to install

The git-workflow rule defines commit formats (feat, fix, docs and five other types), PR steps, and a three-stage flow with planner, TDD-guide and code-reviewer agents.

MIT ★ 6,739 updated 2026-01-23

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add WorldFlowAI/everything-claude-code
/plugin install everything-claude-code@everything-claude-code
Open on GitHub

What git-workflow does

The rule embeds a commit template with mandatory type (feat, fix, refactor, docs, test, chore, perf, ci) and description, PR steps (full commit history via git diff [base-branch]...HEAD, test plan, -u flag for new branches) and a three-stage process for new features: **planner** agent drafts the plan, **tdd-guide** writes tests before code and checks coverage above 80%, and **code-reviewer** analyses and flags issues.

Attribution is globally disabled via ~/.claude/settings.json.

The rule references three sub-agents — planner, tdd-guide and code-reviewer — their names are hardcoded, with no configuration options.

What it helps with

  • enforce a single commit format across the team
  • embed the TDD cycle (RED → GREEN → IMPROVE) into the standard flow
  • run automatic review before every push
  • generate a full PR description from all branch commits
  • break a large feature into phases before writing code

Example prompts for the agent

  • Make a commit with type feat for the new login function
  • Create a PR, analyse the whole branch and write a summary of changes
  • Run planner to break the Stripe integration into steps

How to install git-workflow

1Plugin marketplace

/plugin marketplace add WorldFlowAI/everything-claude-code
/plugin install everything-claude-code@everything-claude-code

2Manually: put the files in place

.claude/rules/git-workflow.md

The paths frontmatter field limits the files

Step by step, with commands for each platform: AGENTS.md vs CLAUDE.md: what they are and which one to use

Questions about git-workflow

How to install git-workflow in Claude Code?

First /plugin marketplace add WorldFlowAI/everything-claude-code, then /plugin install everything-claude-code@everything-claude-code — the rule will be placed in .claude/rules/git-workflow.md.

What does git-workflow do?

Defines a commit template with eight types (feat, fix, refactor and others), a PR creation process via git diff and a three-step flow for features: planner, TDD-agent and code-reviewer.

Why the 80% coverage threshold in the TDD cycle?

The **tdd-guide** agent checks coverage after the green phase; below 80%, the rule treats refactoring as incomplete. The threshold is hardcoded in the rule text.

Source text

git-workflow.md · MIT
# Git Workflow

## Commit Message Format

```
<type>: <description>

<optional body>
```

Types: feat, fix, refactor, docs, test, chore, perf, ci

Note: Attribution disabled globally via ~/.claude/settings.json.

## Pull Request Workflow

When creating PRs:
1. Analyze full commit history (not just latest commit)
2. Use `git diff [base-branch]...HEAD` to see all changes
3. Draft comprehensive PR summary
4. Include test plan with TODOs
5. Push with `-u` flag if new branch

## Feature Implementation Workflow

1. **Plan First**
   - Use **planner** agent to create implementation plan
   - Identify dependencies and risks
   - Break down into phases

2. **TDD Approach**
   - Use **tdd-guide** agent
   - Write tests first (RED)
   - Implement to pass tests (GREEN)
   - Refactor (IMPROVE)
   - Verify 80%+ coverage

3. **Code Review**
   - Use **code-reviewer** agent immediately after writing code
   - Address CRITICAL and HIGH issues
   - Fix MEDIUM issues when possible

4. **Commit & Push**
   - Detailed commit messages
   - Follow conventional commits format

© Affaan Mustafa · MIT · WorldFlowAI/everything-claude-code

Similar IDE rules

All IDE rules for Git and GitHub →

From the same set29

The whole set →
build-fix build-fix fixes TypeScript and build failures one at a time, rerunning the build after each change. Useful when the error list needs a controlled pass. CX Codex +1 ★ 6,739repo stars refactor-clean refactor-clean identifies unused code across your codebase, categorizes findings by risk level, and removes them with test verification. Runs the full test suite before and after each deletion to catch regressions. CX Codex +1 ★ 6,739repo stars security security is a Claude Code rule that checks changes for exposed secrets, input validation, and protection against web attacks before commit. CX Codex +1 ★ 6,739repo stars code-review code-review is a Claude Code command that checks uncommitted changes for security flaws and code-quality issues. It reports findings and blocks commits when it detects CRITICAL or HIGH severity problems. CX Codex +1 ★ 6,739repo stars patterns patterns sets standard TypeScript interfaces for APIs and repositories, provides a useDebounce hook, and defines a workflow for evaluating skeleton repos. CX Codex +1 ★ 6,739repo stars verify The verify command checks the build, types, lint, tests, logs, and Git state. Use it before a commit or pull request. CX Codex +1 ★ 6,739repo stars performance performance — a Claude Code rule that matches model to task and keeps heavy refactors away from the tail of the context window. CX Codex +1 ★ 6,739repo stars coding-style coding-style is a Claude Code rule for code structure and quality checks. It applies while an agent writes or changes code. CX Codex +1 ★ 6,739repo stars

More in the catalog

Project sponsors

Companies that keep this analytics open