/review-workflow-enforcement
Enforcement checks to verify all required outputs were produced, and the full list of command options.
$ npx -y skills add athola/claude-night-market --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/review-workflow-enforcement
Context preview
What this command does when you run it.
Enforcement checks to verify all required outputs were produced, and the full list of command options.
Command definition
review-workflow-enforcement.mdPR/MR Review: Mandatory Outputs Enforcement and Options
Enforcement checks to verify all required outputs were produced, and the full list of command options.
> **See Also**: > [Main Command](../../pr-review.md) | > [Workflow Index](review-workflow.md) | > [Phases 1-4](review-workflow-phases-1-4.md) | > [Phases 5-6](review-workflow-phases-5-6.md) | > [Framework](review-framework.md) | > [Configuration](review-configuration.md)
---
Mandatory Outputs Enforcement
**CRITICAL: The /pr-review command is NOT complete unless ALL of these outputs exist:**
| Output | Phase | Verification | |--------|-------|--------------| | Review comment | Phase 4 | `gh pr view --json comments` contains "PR Review" | | Test plan comment | Phase 5 | `gh pr view --json comments` contains "Test Plan" | | PR description | Phase 6 | `gh pr view --json body` is non-empty and contains "Review Summary" |
**Enforcement Check (run at end of review):**
# Validate all mandatory outputs
PR_NUMBER=${1:-$(gh pr view --json number -q '.number')}
REVIEW_EXISTS=$(gh pr view $PR_NUMBER --json comments --jq '[.comments[].body | contains("PR Review")] | any')
TEST_PLAN_EXISTS=$(gh pr view $PR_NUMBER --json comments --jq '[.comments[].body | ascii_downcase | contains("test plan")] | any')
DESCRIPTION_EXISTS=$(gh pr view $PR_NUMBER --json body --jq '.body | length > 0')
echo "=== Mandatory Output Verification ==="
echo "Review comment: $( [[ $REVIEW_EXISTS == "true" ]] && echo "✅" || echo "❌ MISSING" )"
echo "Test plan: $( [[ $TEST_PLAN_EXISTS == "true" ]] && echo "✅" || echo "❌ MISSING" )"
echo "PR description: $( [[ $DESCRIPTION_EXISTS == "true" ]] && echo "✅" || echo "❌ MISSING" )"
if [[ $REVIEW_EXISTS != "true" ]] || [[ $TEST_PLAN_EXISTS != "true" ]] || [[ $DESCRIPTION_EXISTS != "true" ]]; then
echo ""
echo "⚠️ PR review INCOMPLETE - mandatory outputs missing"
echo "Run /pr-review-enforcer $PR_NUMBER to fix"
exit 1
fi
echo ""
echo "✅ All mandatory outputs verified for PR #$PR_NUMBER"**If verification fails, the review is INCOMPLETE. Go back and complete missing phases.**
Options
- `--scope-mode`: Set strictness level (default: standard)
- `strict`: All requirements must be complete
- `standard`: Core requirements required
- `flexible`: MVP implementation acceptable
- `--auto-approve-safe-prs`: Auto-approve PRs with no issues
- `--no-auto-issues`: **Skip automatic issue creation** for out-of-scope items (issues are created by default)
- `--dry-run`: Generate report in conversation without posting to GitHub
- `--local [path]`: Write full report to a local `.md` file instead
of posting to the PR. Default path: `.pr-review/pr-<number>-review.md`. Skips API calls, issue creation, and PR description updates. Unlike `--dry-run`, produces a permanent file.
- `--no-line-comments`: Skip individual line comments, only submit summary review
- `--skip-version-check`: **BYPASS version validation** (maintainer override)
- Use when: intentional version skew, non-release PR touching version files
- Alternative: Add `skip-version-check` label to PR or `[skip-version-check]` in PR description
- **Still runs validation** but marks issues as [WAIVED] instead of [BLOCKING]
- `pr-number`/`pr-url`: Target specific PR (default: current branch)
Read more
PR/MR Review: Mandatory Outputs Enforcement and Options
Enforcement checks to verify all required outputs were produced, and the full list of command options.
> **See Also**: > [Main Command](../../pr-review.md) | > [Workflow Index](review-workflow.md) | > [Phases 1-4](review-workflow-phases-1-4.md) | > [Phases 5-6](review-workflow-phases-5-6.md) | > [Framework](review-framework.md) | > [Configuration](review-configuration.md)
---
Mandatory Outputs Enforcement
**CRITICAL: The /pr-review command is NOT complete unless ALL of these outputs exist:**
| Output | Phase | Verification | |--------|-------|--------------| | Review comment | Phase 4 | `gh pr view --json comments` contains "PR Review" | | Test plan comment | Phase 5 | `gh pr view --json comments` contains "Test Plan" | | PR description | Phase 6 | `gh pr view --json body` is non-empty and contains "Review Summary" |
**Enforcement Check (run at end of review):**
# Validate all mandatory outputs
PR_NUMBER=${1:-$(gh pr view --json number -q '.number')}
REVIEW_EXISTS=$(gh pr view $PR_NUMBER --json comments --jq '[.comments[].body | contains("PR Review")] | any')
TEST_PLAN_EXISTS=$(gh pr view $PR_NUMBER --json comments --jq '[.comments[].body | ascii_downcase | contains("test plan")] | any')
DESCRIPTION_EXISTS=$(gh pr view $PR_NUMBER --json body --jq '.body | length > 0')
echo "=== Mandatory Output Verification ==="
echo "Review comment: $( [[ $REVIEW_EXISTS == "true" ]] && echo "✅" || echo "❌ MISSING" )"
echo "Test plan: $( [[ $TEST_PLAN_EXISTS == "true" ]] && echo "✅" || echo "❌ MISSING" )"
echo "PR description: $( [[ $DESCRIPTION_EXISTS == "true" ]] && echo "✅" || echo "❌ MISSING" )"
if [[ $REVIEW_EXISTS != "true" ]] || [[ $TEST_PLAN_EXISTS != "true" ]] || [[ $DESCRIPTION_EXISTS != "true" ]]; then
echo ""
echo "⚠️ PR review INCOMPLETE - mandatory outputs missing"
echo "Run /pr-review-enforcer $PR_NUMBER to fix"
exit 1
fi
echo ""
echo "✅ All mandatory outputs verified for PR #$PR_NUMBER"**If verification fails, the review is INCOMPLETE. Go back and complete missing phases.**
Options
- `--scope-mode`: Set strictness level (default: standard)
- `strict`: All requirements must be complete
- `standard`: Core requirements required
- `flexible`: MVP implementation acceptable
- `--auto-approve-safe-prs`: Auto-approve PRs with no issues
- `--no-auto-issues`: **Skip automatic issue creation** for out-of-scope items (issues are created by default)
- `--dry-run`: Generate report in conversation without posting to GitHub
- `--local [path]`: Write full report to a local `.md` file instead
of posting to the PR. Default path: `.pr-review/pr-<number>-review.md`. Skips API calls, issue creation, and PR description updates. Unlike `--dry-run`, produces a permanent file.
- `--no-line-comments`: Skip individual line comments, only submit summary review
- `--skip-version-check`: **BYPASS version validation** (maintainer override)
- Use when: intentional version skew, non-release PR touching version files
- Alternative: Add `skip-version-check` label to PR or `[skip-version-check]` in PR description
- **Still runs validation** but marks issues as [WAIVED] instead of [BLOCKING]
- `pr-number`/`pr-url`: Target specific PR (default: current branch)
A plugin marketplace for Claude Code. Install only the plugins you need to run git workflows, code review, spec-driven development, and autonomous agents from inside your Claude Code session.
Other commands on claude-night-market.
- /aggregate-logs
Generate LEARNINGS.md from skill execution logs.
Open command - /analyze-skill
Analyze skill file complexity metrics and generate modularization recommendations for splitting or progressive loading.
Open command - /bulletproof-skill
Harden skills against rationalization and bypass behaviors
Open command - /context-report
Generate context optimization report for skill directories
Open command - /create-command
Create slash commands with brainstorming and best practices
Open command - /create-hook
Create hooks with brainstorming and security-first design
Open command

