git-workflow

Claude Code Git Workflow

Production-ready slash commands for Claude Code that automate your Git workflow, PR creation, release management, and QA testing.

Features

• Framework-agnostic - Works with any language or framework
• Configurable - Customize everything via .claude/config.yaml
• Issue tracker integration - Linear, Jira, and GitHub Issues
• Multi-workflow support - Staging-based, tag-based, or direct workflows
• Zero configuration - Sensible defaults work out of the box
• Subagents - Specialized AI assistants for code review, release validation, and QA
• Hooks - Automate actions before/after tool use
• Marketplace plugin - Installable from Claude marketplace

Quick Start

Option 1: Install from Marketplace (Recommended)

# Add the marketplace
/plugin marketplace add rlajous/claude-code-commands

# Install the plugin
/plugin install git-workflow@git-workflow-marketplace

After installation, commands are available with the git-workflow: prefix:

/git-workflow:start PROJ-123
/git-workflow:commit
/git-workflow:finish

Option 2: Manual Installation (Shorter Command Names)

For shorter command names (e.g., /start instead of /git-workflow:start):

# Clone and copy to your project
git clone https://github.com/rlajous/claude-code-commands.git
cp -r claude-code-commands/commands your-project/.claude/
cp -r claude-code-commands/agents your-project/.claude/

Cursor users: Cursor also detects commands from .claude/. Manual installation works as-is. See INSTALLATION.md for details.

3. (Optional) Add Configuration

Create .claude/config.yaml for project-specific settings:

# Basic configuration example
workflow:
  developmentBranch: staging
  productionBranch: main

issueTracker:
  type: linear  # or jira, github

pullRequests:
  reviewers:
    - your-team

See CONFIGURATION.md for all options.

4. Run Setup (Recommended)

/setup  # or /git-workflow:setup if installed via marketplace

This guides you through configuring issue trackers and MCP servers.

5. Use the Commands

# Start a new feature
/start

# Commit changes
/commit

# Create a PR
/finish

Commands

Command	Description
/setup	Interactive setup wizard for MCP and config
/start	Create a feature branch from a ticket ID
/tdd	Implement ticket using Test-Driven Development
/commit	Stage and commit with conventional format
/finish	Push branch and create PR with full description
/review	Comprehensive code review on a PR
/release	Create release branch with version bump
/release-notes	Generate GitHub release with detailed notes
/sync	Back-merge production to development branch
/plan-qa	Generate QA test plan from ticket
/start-qa	Execute QA tests from plan file
/update	Update commands and agents from source repo

Note: If installed via marketplace, prefix commands with git-workflow: (e.g., /git-workflow:start)

Subagents

Specialized AI assistants for common tasks:

Agent	Description
pr-reviewer	Expert code reviewer for quality, security, and best practices
release-validator	Pre-release validation (tests, build, dependencies)
qa-executor	Executes QA test plans with detailed reporting

Using Subagents

Subagents are invoked automatically when relevant, or explicitly:

Review the code changes in this PR
Use the release-validator to check if we're ready to release

See AGENTS.md for complete documentation.

Hooks

Automate actions at key points in your workflow:

• PostToolUse - Run after file edits (auto-format, lint)
• PreToolUse - Validate before execution (prevent dangerous commands)
• SessionStart/End - Setup and logging

Example Hook

{
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "Write|Edit",
        "hooks": [
          {
            "type": "command",
            "command": "npm run lint:fix -- $CLAUDE_FILE_PATH"
          }
        ]
      }
    ]
  }
}

See HOOKS.md for complete documentation.

Commands

Commands are defined using YAML frontmatter in markdown files.

Using Commands

Commands can be invoked in multiple ways:

# As slash commands
/start PROJ-123
/commit
/finish

# With arguments
/plan-qa PROJ-123 --url https://api.staging.example.com

# In conversation
"Run /commit and then /finish for me"

Command Format

Each command file uses YAML frontmatter for configuration:

---
description: What this command does
argument-hint: "[optional-arg]"
disable-model-invocation: true
---

See COMMANDS.md for complete documentation.

Discover more command ideas at skills.sh.

Workflow