You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a team delivering with pair I want/pair-process-review to forward its classify-phase resolved risk tier to the verify-quality skill it composes So that the review-composition path gets exact local=CI tier parity instead of degrading to fail-safe 🔴 (full set) when run off-branch — removing the current safe-but-wider over-check on green work in that path
Where: /pair-process-review orchestration (the step that composes verify-quality).
Follow-up from PR #378 (story #259) review. verify-quality resolves the tier from the current-branch PR via no-arg gh pr view, with a $story story-card fallback. When /pair-process-review composes it with only $scope from a context not on the PR branch, gh pr view returns empty and — with no $story — resolution degrades to the fail-safe 🔴 (full set) rather than review's classify-phase tier.
This is the safe over-check direction (never an under-check) and /pair-process-review is non-blocking on verify-quality (its own classify step is the authoritative review-time tier), so the verdict is never wrong — only the local run is wider than necessary. The #259 boundary deliberately kept this fix out of verify-quality's SKILL.md (documented in that skill's Composition Interface note); the change belongs to /pair-process-review.
Acceptance Criteria (draft)
Given/pair-process-review has resolved a tier in its classify phase, when it composes verify-quality, then it passes that tier through so verify-quality runs exactly the review-time tier's suites (no fail-safe 🔴 over-check on that path).
Story Statement
As a team delivering with pair
I want
/pair-process-reviewto forward its classify-phase resolved risk tier to theverify-qualityskill it composesSo that the review-composition path gets exact local=CI tier parity instead of degrading to fail-safe 🔴 (full set) when run off-branch — removing the current safe-but-wider over-check on green work in that path
Where:
/pair-process-revieworchestration (the step that composesverify-quality).Epic Context
Parent Epic: CI/CD gates tag-driven #210
Background
Follow-up from PR #378 (story #259) review.
verify-qualityresolves the tier from the current-branch PR via no-arggh pr view, with a$storystory-card fallback. When/pair-process-reviewcomposes it with only$scopefrom a context not on the PR branch,gh pr viewreturns empty and — with no$story— resolution degrades to the fail-safe 🔴 (full set) rather than review's classify-phase tier.This is the safe over-check direction (never an under-check) and
/pair-process-reviewis non-blocking onverify-quality(its own classify step is the authoritative review-time tier), so the verdict is never wrong — only the local run is wider than necessary. The #259 boundary deliberately kept this fix out ofverify-quality's SKILL.md (documented in that skill's Composition Interface note); the change belongs to/pair-process-review.Acceptance Criteria (draft)
/pair-process-reviewhas resolved a tier in its classify phase, when it composesverify-quality, then it passes that tier through soverify-qualityruns exactly the review-time tier's suites (no fail-safe 🔴 over-check on that path).Status
Draft — non-blocking follow-up. Filed per the #378 review finding.