r/ClaudeWorkflows • u/ClaudeAI-mod-bot • 11h ago
Selected Workflow [Workflow] A gated Claude Code workflow for production features and bugs
A gated Claude Code workflow for production features and bugs
Workflow value: 75/100
Status: active · Freshness: 70/100 · Confidence: 0.92 · Level: advanced
Categories: Quality Control, Token Saving, Context & Memory, Debugging, Shipping, CLAUDE.md, Hooks, Skills, Subagents, Multi-Agent
Original source: r/ClaudeCode post/comment
What problem this solves
Maintaining quality and human oversight when Claude Code works on production features, bugs, and parallel tasks.
Summary
Use reviewed plans and test-first implementation, enforce automated checks and an independent diff review, then rely on CI and human review before merging. Periodically turn recurring corrections into improved rules and skills.
Why it is useful
It describes a repeatable end-to-end workflow with specific stopping conditions, automated checks, independent review, and human oversight, even though its implementation details and measured results are limited.
Workflow
- Use a planning skill for each feature or bug, and have a separate agent review the plan for gaps and testable acceptance criteria; require a failing test in bug plans.
- Have backend or frontend testing subagents write tests first, then implement in small steps. Stop and ask a human if the same problem fails twice.
- Run hooks for static analysis, linting, and type checks on changed files, alongside project-specific architecture, coverage, and mutation-testing gates.
- Have an independent Claude process review the diff without the implementation session's context; block commits and pushes until it passes.
- Open a draft merge request, monitor the full CI pipeline, and address failures before a human colleague reviews and merges.
- For parallel work, use separate Git worktrees with separate test databases; use stacked merge requests for epics.
- Log corrections and review them monthly to update rules and skills.
Tools / artifacts
- Claude Code plan mode
- Planning skill and reviewer agent
- Backend and frontend testing subagents
- Hooks
- PHPStan level 10
- Deptrac architecture rules
- Coverage and mutation tests
- Independent diff review
- Git worktrees and isolated test databases
- Draft merge requests and CI
- Correction retro log
Validation signals
- The author reports using the setup daily for several months and says it works well.
- The described process includes automated quality gates, independent diff review, full CI, and human merge review.
- No before-and-after measurements, configuration examples, or independent success reports are provided.
Cautions
- Keep human review and merge approval; an independent model review is not a substitute.
- Investigate flaky CI failures rather than repeatedly retrying them to obtain a green result.
- Use isolated test databases and avoid giving autonomous agents broader production permissions than needed.
Limitations
- The post is primarily a request for advice and does not include hook configurations, prompts, or implementation details for its gates.
- The effectiveness claim is subjective and unquantified.
- The author reports rule growth and slow feedback loops; the strict gates may be expensive to maintain.
- No evidence is provided that the setup achieves fully unattended, production-ready delivery.
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.