← All Workflows Review Lane

Review Cycle

Multi-dimensional code review with dual critique gates that prevent blind acceptance of suggestions.

PLAN REVIEW SHIP informs executes configures findings to staged for merged then feeds into fixes flow into or ship directly release after approved, then invokes invokes invokes invokes conditionally invokes invokes /jira-sdlc Create & manage Jira issue… INTEGRATIONS /plan-sdlc Write implementation plans PLANNING /execute-plan-sdlc Execute plans with paralle… PLANNING /setup-sdlc Configure review dimension… REVIEW /review-sdlc Multi-dimension code revie… REVIEW /received-review-sdlc Process review feedback REVIEW /commit-sdlc Smart commit message gener… GITOPS /pr-sdlc Create structured pull req… GITOPS /version-sdlc Bump version and create re… GITOPS /ship-sdlc Full pipeline orchestrator WORKFLOWS

PLAN

/jira-sdlc Create & manage Jira issues /plan-sdlc Write implementation plans /execute-plan-sdlc Execute plans with parallel waves

REVIEW

/setup-sdlc Configure review dimensions, PR template, guardrails /review-sdlc Multi-dimension code review /received-review-sdlc Process review feedback

SHIP

/commit-sdlc Smart commit message generation /pr-sdlc Create structured pull requests /version-sdlc Bump version and create release /ship-sdlc Full pipeline orchestrator
1

Initialize with /setup-sdlc

Scans your project's tech stack -- package.json, directory structure, file patterns -- and proposes relevant review dimensions from a catalog of 31 types. You select which dimensions to install. Each dimension becomes a focused lens for code review.

Dimension files are written to .claude/review-dimensions/ and optionally mirrored as GitHub Copilot instruction files. This is typically a one-time setup, though you can re-run it when your stack changes.

2

Review with /review-sdlc

The core review skill loads your installed dimensions and matches them to the changed files via glob patterns. Parallel subagents review each matching dimension independently, then findings are deduplicated and merged into a consolidated report.

The review can target different scopes: --committed for branch commits, --staged for what's about to be committed, or --working for uncommitted changes. The consolidated comment is posted to the PR via the GitHub CLI.

3

Respond with /received-review-sdlc

When review findings exist, this skill processes the feedback through two critique gates. First, it reads the actual code referenced in each finding and evaluates whether the suggestion is technically correct. Then a self-critique pass catches performative agreement or blind compliance.

Accepted fixes are implemented in priority order. Thread replies are posted back to the PR, creating a traceable conversation. The output flows naturally into the ship lane -- commit the fixes, update the PR.

What happens next?

Commit the fixes received-review-sdlc flows into commit-sdlc to package accepted changes Review planned work execute-plan-sdlc feeds its output into review-sdlc for quality checks