MANDATORY: Before accepting any rationalization for rubber-stamping code quality, consult

references/rationalization-refutation.md

. Every common excuse is catalogued with a counter-argument and the correct action.

• Spec review has passed

• /review

  command (after spec review)
• Ready to assess code quality
• Before synthesis/merge

1. Generate diff:

   git diff main...HEAD

   or

   git diff main...integration-branch

2. Pass diff content in the subagent dispatch prompt
3. Include state file path for artifact resolution
4. Include spec review results (must be PASS)

1. Receive diff content from dispatch prompt (do NOT re-generate)
2. Read state file for design/plan artifact paths
3. Run static analysis and security scripts against the working tree
4. Return structured JSON verdict

• Evaluation strategy:

  exarchos_orchestrate({ action: "runbook", id: "review-strategy" })

  to determine single-pass vs two-pass evaluation strategy based on diff size and task count.

• The complete stack diff (all task branches vs main), or the feature/integration-branch diff when using integration branches
• All changes across all tasks in one view
• The full picture of combined code quality

• Cross-task SOLID violations
• Duplicate code across task boundaries
• Inconsistent patterns between tasks

• Code quality and readability
• SOLID principles
• Error handling
• Test quality
• Performance considerations
• Security basics

• Functional completeness (spec review)
• TDD compliance (spec review)

mcp__exarchos__exarchos_view({ action: "code_quality", workflowId: "<featureId>" })

• If

  regressions

  is non-empty, report active quality regressions to the user before proceeding
• If any hint has

  confidenceLevel: 'actionable'

  , present the

  suggestedAction

  to the user
• If

  gatePassRate < 0.80

  for the target skill, warn about degrading quality

Runbook: Run quality evaluation gates via runbook:

exarchos_orchestrate({ action: "runbook", id: "quality-evaluation" })

If runbook unavailable, use

describe

to retrieve gate schemas:

exarchos_orchestrate({ action: "describe", actions: ["check_static_analysis", "check_security_scan", "check_convergence", "check_review_verdict"] })

references/gate-execution.md

1. check_static_analysis

   — lint, typecheck, quality-check (D2). Must pass before continuing.

2. check_security_scan

   — security pattern detection (D1). Include findings in report.
3. Optional D3-D5 gates:

   check_context_economy

   ,

   check_operational_resilience

   ,

   check_workflow_determinism

   — advisory, feed convergence view.

• HIGH: security vulnerabilities, data loss risk, API contract breaks, uncaught exception paths
• MEDIUM: SOLID violations (LSP, ISP), cyclomatic complexity >15, test coverage <70%
• LOW: naming, code style, comment clarity, non-impactful performance

1. Create fix task listing each HIGH finding with file, issue, and required fix
2. Dispatch to implementer subagent
3. Re-review quality after fixes
4. Only mark APPROVED when all HIGH items resolved and tests pass

/review --max-fix-iterations 5

1. Run spec verification commands:
   bash

   npm run test:run
   npm run typecheck

   typescript

   exarchos_orchestrate({
     action: "check_tdd_compliance",
     featureId: "<featureId>",
     taskId: "<taskId>",
     branch: "<branch>"
   })

2. If all pass: proceed to APPROVED transition
3. If any fail: return to NEEDS_FIXES with spec regression noted in issues array

1. Classify as "cross-task integration"
2. Create fix task specifying ALL affected tasks
3. Dispatch fix to implementer with context from all affected tasks
4. Mark original tasks as blocked until cross-task fix completes

Key format: The review key MUST be kebab-case

reviews["quality-review"]

, not camelCase

reviews.qualityReview

. The guard matches on the exact key string.

action: "set", featureId: "<id>", updates: {
  "reviews": { "quality-review": { "status": "pass", "summary": "...", "issues": [...] } }
}

action: "set", featureId: "<id>", phase: "synthesize"

@skills/workflow-state/references/phase-transitions.md

• review

  →

  synthesize

  requires guard

  all-reviews-passed

  — all

  reviews.{name}.status

  must be passing

• review

  →

  delegate

  requires guard

  any-review-failed

  — triggers fix cycle when any review fails

• Static analysis passes
• All HIGH-priority issues fixed
• No security vulnerabilities
• Test quality acceptable
• Code is maintainable
• State file updated with review results

exarchos_orchestrate({ action: "prepare_review", featureId: "<id>" })

• catalog

  — structured check dimensions with grep patterns, structural thresholds, and heuristic instructions

• findingFormat

  — the TypeScript interface for submitting findings

• pluginStatus

  — which companion plugins are configured in

  .exarchos.yml

• grep checks: Run the

  pattern

  against files matching

  fileGlob

• structural checks: Evaluate against the

  threshold

  (e.g., nesting depth, function length)
• heuristic checks: Use judgment guided by the

  description

findingFormat

pluginFindings

check_review_verdict

status

exarchos_workflow({ action: "set", featureId: "<id>", updates: {
  reviews: { "quality-review": { status: "pass", summary: "...", issues: [] } }
}, phase: "synthesize" })

/synthesize

exarchos_workflow({ action: "set", featureId: "<id>", updates: {
  reviews: { "quality-review": { status: "fail", summary: "...", issues: [{ severity: "HIGH", file: "...", description: "..." }] } }
}})

/delegate --fixes

Gate events: Do NOT manually emit

gate.executed

events via

exarchos_event

. Gate events are automatically emitted by the

check_review_verdict

orchestrate handler. Manual emission causes duplicates.

Guard shape: The

all-reviews-passed

guard requires

reviews.{name}.status

to be a passing value (

pass

,

passed

,

approved

,

fixes-applied

). Flat strings like

reviews: { "quality-review": "pass" }

are silently ignored and will block the

review → synthesize

transition.