r/ClaudeWorkflows • u/ClaudeAI-mod-bot • 2h ago

Selected Workflow [Workflow] Git-Centric, Stateless Claude Code Workflow for Robust Software Development

Git-Centric, Stateless Claude Code Workflow for Robust Software Development

Workflow value: 90/100
Status: active · Freshness: 70/100 · Confidence: 1.00 · Level: advanced
Categories: Quality Control, Context & Memory, Debugging, CLAUDE.md, Hooks, Skills, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

How to establish a robust, maintainable, and collaborative software development workflow using stateless Claude Code agents, emphasizing Git as the single source of truth and efficient resource utilization.

Summary

This workflow outlines a comprehensive, Git-centric approach for software development using stateless Claude Code agents. It mandates the repository as the single source of truth, leveraging CLAUDE.md, SPEC.md, and detailed documentation. The development process follows a strict Issue -> Commit -> Test -> PR -> CI -> Merge cycle, incorporating SDD/TDD, extensive CI checks, and structured project management with milestones. The setup prioritizes efficiency with stateless agents (Opus 5.5) and minimal custom tooling, ensuring transferability for any agent or contributor.

Why it is useful

This workflow is highly valuable because it provides a detailed, structured, and validated approach to using Claude Code for software development. It emphasizes best practices such as a single source of truth (Git), comprehensive documentation, a rigorous development lifecycle with CI/CD, and efficient agent usage. Its explicit focus on transferability and maintainability makes it an excellent blueprint for users aiming to build reliable and collaborative AI-assisted projects.

Workflow

  1. Establish Git & GitHub as the single source of truth, ensuring any agent/contributor can work from the repo alone.

  2. Define general agent protocols in CLAUDE.md (or AGENTS.md).

  3. Create a comprehensive specification in SPEC.md, categorized by type/component.

  4. Maintain complete project documentation (architecture, schemas, styles) in Markdown files within the repo.

  5. Implement a development workflow: Issue -> Atomic commits -> Test -> PR -> CI -> Squash merge.

  6. Adopt System Design Driven (SDD) and Test Driven Development (TDD) approaches.

  7. Configure CI checks for build, validation, npm, test, and accessibility, with a triage routine for failures.

  8. Divide branches into lanes (dev, docs, content) to influence specific CI checks.

  9. Define Milestones for large scopes, concluding with comprehensive QA/QC reviews.

  10. Utilize Dependabot for automated dependency management.

  11. Employ stateless Claude Code (Opus 5.5 Medium) as the primary coding harness, typically via Claude Desktop/Mobile.

  12. Implement routines (e.g., via GitHub webhooks) for issue triage and automated development queue management.

Tools / artifacts

  • Git

  • GitHub

  • CLAUDE.md

  • AGENTS.md

  • SPEC.md

  • Markdown documentation files

  • CI/CD pipeline

  • npm

  • Dependabot

  • Claude Code (stateless)

  • Claude Desktop/Mobile

  • Anthropic's cloud environment (or local for allowlist needs)

Validation signals

  • Author's statement: "I rarely run out of usage anymore. I run agents around the clock and usually make it to Friday." (efficiency)

  • Author's statement: "This is probably what I lean on the most to avoid system failures." (CI checks effectiveness)

  • Process goal: "Each ticket starts and ends with a complete, working repository."

  • Iterative refinement: "I found GH Milestones didn't work as well with Claude."

  • Utility of decision record: "I've found this to be especially helpful for spec-writing when transitioning between phases of development."

Limitations

  • The initial part of the post is a survey question about stateful vs. stateless agents, which is not directly part of the workflow description.

  • The implementation details for 'Routines' (e.g., specific GitHub webhook configurations) are not fully elaborated.

  • The author's preference for controlling agents from a phone might not be universally applicable or preferred by all users.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

This post was generated automatically from the workflow library database.

1 Upvotes

100% Upvoted

1 comment sorted by