agentleFS
rlajousrlajous/claude-code-commands/CLAUDE.md

claude-code-commands

CLAUDE.md30 starsChanged 3 months agoMITView on GitHub

This repository is the dual-runtime Git Workflow package. Claude Code consumes its marketplace/plugin packaging and Claude-specific frontmatter; Codex consumes .codex-plugin/plugin.json and generated .codex/agents/*.toml. Shared workflow configuration lives in .git-workflow/config.yaml, with legacy .claude/config.yaml reads retained for compatibility. Each capability is a skill: a directory under skills/ containing a SKILL.md with YAML frontmatter. This is the current, preferred format (t

The file

We split this CLAUDE.md into the rules it gives an agent

9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Strictly Reactive: Only perform the specific task requested.

    line 11
  2. Distinctive:

    Seek Confirmation: Always wait for user confirmation after completing a discrete task before moving to anything else.

    line 12
  3. Distinctive:

    No Unapproved Side Effects: Do not apply database migrations, execute scripts, or modify the system state without explicit approval for …

    line 13
  4. Distinctive:

    Verify YAML frontmatter is valid

    line 222
  5. Distinctive:

    Check command steps are numbered correctly

    line 223
  6. Distinctive:

    Ensure config references match schema

    line 224
  7. Distinctive:

    Test with and without config file

    line 225
  8. Very specific:

    Run bash scripts/validate.sh to check manifests (valid JSON, aligned versions), skill/agent frontmatter, and SKILL.md sizes.

    line 227
  9. Distinctive:

    When creating git commits, do NOT include Co-Authored-By lines in commit messages.

    line 233

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Overview

This repository is the dual-runtime Git Workflow package. Claude Code consumes its marketplace/plugin packaging and Claude-specific frontmatter; Codex consumes .codex-plugin/plugin.json and generated .codex/agents/*.toml. Shared workflow configuration lives in .git-workflow/config.yaml, with legacy .claude/config.yaml reads retained for compatibility.

Behavioral Guidelines

  • Strictly Reactive: Only perform the specific task requested. Do not perform follow-up research, planning for future phases, or speculative actions unless explicitly asked.
  • Seek Confirmation: Always wait for user confirmation after completing a discrete task before moving to anything else.
  • No Unapproved Side Effects: Do not apply database migrations, execute scripts, or modify the system state without explicit approval for that specific action.

Repository Structure

.claude-plugin/
├── marketplace.json       # Marketplace catalog for distribution
└── plugin.json            # Plugin manifest

.codex-plugin/
└── plugin.json            # Codex plugin manifest

.codex/agents/             # Generated Codex project agents (do not hand-edit)

skills/                    # Skills (each an invocable slash command via SKILL.md)
├── setup/SKILL.md         # Interactive setup wizard
├── start/SKILL.md         # Create feature branch from ticket
├── plan-tdd/SKILL.md      # Design a reviewed TDD plan before coding
├── tdd/SKILL.md           # Test-Driven Development workflow
├── commit/SKILL.md        # Stage and commit with conventions
├── finish/SKILL.md        # Create PR with full description
├── review/SKILL.md        # Comprehensive code review on a PR
├── release/SKILL.md       # Create release branch and PR
├── release-notes/SKILL.md # Generate GitHub release notes
├── sync/SKILL.md          # Back-merge main to development
├── plan-qa/SKILL.md       # Generate QA test plan
├── start-qa/SKILL.md      # Execute QA tests
├── rfc/SKILL.md           # Create an auto-numbered RFC document
├── review-request/SKILL.md # Draft a paste-ready PR review request
├── standup/SKILL.md       # Async standup from recent activity
├── update/SKILL.md        # Update skills/agents from source
├── clean-gone/SKILL.md    # Delete local branches gone on the remote
├── status/SKILL.md        # Show workflow position and next step
├── review-watch/SKILL.md  # Auto-review PRs that request your review, in a loop
├── notifications/SKILL.md # Opt-in agent and authored-PR activity alerts
└── change-brief/SKILL.md  # Self-contained HTML explainer of a change

agents/                    # Subagents for specialized tasks
├── pr-reviewer.md         # Code review agent
├── release-validator.md   # Release validation agent
└── qa-executor.md         # QA test execution agent

templates/
├── config.yaml.template   # Configuration template
├── settings.json.template # Hooks configuration template
└── CLAUDE.md.template     # CLAUDE.md template for projects

examples/                  # Stack-specific examples
├── nestjs/               # NestJS backend config
├── nextjs/               # Next.js frontend config
├── python/               # Python FastAPI config
├── react-native/         # React Native config
└── monorepo/             # Turborepo monorepo config

README.md                  # Main documentation
INSTALLATION.md            # Setup guide
CONFIGURATION.md           # Configuration reference
COMMANDS.md                # Commands reference documentation
AGENTS.md                  # Concise Codex contributor guidance
docs/SUBAGENTS.md          # User-facing agent catalog
HOOKS.md                   # Hooks documentation
LICENSE                    # MIT license

Skills Format

Each capability is a skill: a directory under skills/ containing a SKILL.md with YAML frontmatter. This is the current, preferred format (the older .claude/commands/*.md layout is legacy). A skill with user-invocable: true still works as a manual slash command (/start), and — unless disable-model-invocation: true is set — can also be auto-invoked by Claude when its description matches the task.

---
name: start
description: What this skill does, with trigger phrases for auto-invocation
argument-hint: "[optional-arg]"
disable-model-invocation: true
allowed-tools: Read, Grep, Glob, Bash
user-invocable: true
---

Key frontmatter fields:

  • name: Skill identifier (required); also the slash command name
  • description: Shown in the menu and used to decide auto-invocation
  • argument-hint: Shows expected arguments
  • disable-model-invocation: Prevents auto-invocation (kept on side-effecting workflow actions; omitted on read-only skills like review)
  • allowed-tools: Tools Claude can use without asking permission
  • user-invocable: Makes the skill available as a /name slash command

Skills may bundle references/, scripts/, examples/, or assets/ in their directory for progressive disclosure (loaded on demand, keeping SKILL.md lean).

Marketplace Format

This repo serves as both a plugin and a marketplace:

  • marketplace.json: Catalog of plugins in this marketplace
  • plugin.json: Metadata for the git-workflow plugin

Users can install via:

/plugin marketplace add rlajous/claude-code-commands
/plugin install git-workflow@git-workflow-marketplace

Workflow Commands

CommandPurpose
/setupInteractive setup for MCP servers and config
/startCreate feature branch from ticket ID
/plan-tddDesign a reviewed TDD plan (HTML + YAML) before coding
/tddImplement ticket using TDD (RED-GREEN-REFACTOR)
/commitStage and commit with formatted message
/finishPush branch and create PR
/reviewComprehensive code review on a PR
/releaseCreate release branch, bump version, PR to main
/release-notesGenerate GitHub release with detailed notes
/syncBack-merge main to development branch
/plan-qaGenerate QA test plan YAML from ticket
/start-qaExecute QA tests from plan file
/rfcCreate an auto-numbered RFC document
/review-requestDraft a paste-ready PR review request
/standupAsync standup (Did / Next / Blockers)
/close-customer-loopVerify a customer/partner fix is live in prod and the reporter was told, before closing a ticket
/updateUpdate skills/agents from source repo
/clean-goneDelete local branches gone on the remote and their worktrees
/statusShow workflow position and the recommended next step
/review-watchAuto-review PRs that request your review, in a loop (REQUEST_CHANGES / APPROVE)
/notificationsDiagnose opt-in main-agent and authored-PR review notifications
/change-briefGenerate a self-contained HTML explainer of a change

Subagents

AgentPurpose
pr-reviewerExpert code reviewer for quality and security
release-validatorPre-release validation (tests, build, deps)
qa-executorExecute QA tests with detailed reporting
silent-failure-hunterHunts swallowed errors, over-broad catch blocks, and silent fallbacks in changed code
type-design-analyzerRates type design: encapsulation, invariant expression, usefulness, enforcement (1-10 each)
pr-test-analyzerFinds behavioral test-coverage gaps, rating each missing test's criticality and the regression it catches
comment-analyzerDetects comment rot and docstrings that no longer match the code
version-delta-analystCatalogs breaking changes, deprecations, and migration steps between two versions of a dependency/stack/API

Standard Workflows

PR Flow

/start → make changes → /commit → /finish → /review

TDD Flow

/start → /tdd → /commit → /finish

Release Flow

/release → review → merge → /release-notes → /sync

Hooks

Hooks automate actions during Claude Code execution. Configure in settings.json:

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

The repo also ships opt-in hooks. Claude selects hooks/claude-hooks.json; Codex discovers hooks/hooks.json. Both call hooks/review-commit.sh after eligible Git commands and the notification adapter after the main turn stops. Enable commit review with review-on-commit: true in .git-workflow/git-workflow.local.md; enable completion alerts with notifications.agentComplete: true in .git-workflow/config.yaml. The old .claude/ paths remain read-only fallbacks.

See HOOKS.md for complete documentation.

Design Decisions

Marketplace Structure

  • Single plugin containing all commands (cohesive workflow)
  • Skills in skills/<name>/SKILL.md format
  • Agents in agents/ at root level

Configuration System

  • Zero-config design with sensible defaults
  • Cascading config: explicit config > auto-detection > defaults
  • Context persistence via .pr-context.json

Issue Tracker Support

  • Auto-detection from ticket format
  • Linear, Jira, and GitHub Issues integration
  • MCP servers for automatic authentication

Multi-Stack Support

  • Auto-detects package manager from lock files
  • Supports multiple version file formats
  • Examples for common tech stacks

Testing Changes

When modifying commands:

  1. Verify YAML frontmatter is valid
  2. Check command steps are numbered correctly
  3. Ensure config references match schema
  4. Test with and without config file

Run bash scripts/validate.sh to check manifests (valid JSON, aligned versions), skill/agent frontmatter, and SKILL.md sizes. CI runs the same check on every PR (.github/workflows/validate.yml).

Git Commits

When creating git commits, do NOT include Co-Authored-By lines in commit messages.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.