pr-review-community-overlay

Reviews ArcKit community-overlay pull requests against a checklist of recurring blocker classes.

2.2k|279|Updated Oct 14, 2025
One-click install
npx skills add https://github.com/tractorjuice/arc-kit --skill pr-review-community-overlay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-community-overlay
Source: https://github.com/tractorjuice/arc-kit/tree/main/.claude/skills/pr-review-community-overlay
Command: npx skills add https://github.com/tractorjuice/arc-kit --skill pr-review-community-overlay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing large community-contributed jurisdictional overlay PRs to ArcKit is error-prone: the same five failure classes (missing Document Control headings, un-overridden UK classification lines, mis-invoked document ID generators, stale converter outputs, unregistered regimes) recur across contributions and are easy for human reviewers to miss.

Core Features & Use Cases

  • Five blocker-class checks: Encodes B1–B5 verification with exact grep/bash commands and working precedents from merged PRs (#441, #432).
  • Integration and per-command checklists: Validates doc-types registration, pages allow-list, dual-template parity, recipe schema, frontmatter validity, handoff resolution, and UK terminology leakage.
  • Structured review output: Produces a verdict with BLOCKERS, IMPORTANT, MINOR, and POSITIVE sections plus a pre-merge fix sequence, posted via gh pr comment.
  • Use Case: A contributor opens a PR adding an au-vic-* overlay with 15 new commands and templates; run this Skill to systematically catch classification-rendering bugs and stale converter outputs before merge.

Quick Start

Review pull request number 441 which adds a new community jurisdictional overlay and post the structured findings as a PR comment.

Frequently Asked Questions about pr-review-community-overlay

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review an ArcKit community overlay pull request?

Check out the PR branch, then run the five blocker checks: Document Control heading presence, classification override instructions, generate-document-id.mjs invocation signature, converter drift via git status, and REGIMES/REGIME_LABELS registration. Finish with the integration and per-command checklists before posting a structured review.

What are the common blockers in jurisdictional overlay PRs?

Five recurring classes: templates missing the ## Document Control heading, commands not overriding the UK classification line, generate-document-id.mjs called with a single positional argument, stale converter outputs after rebasing, and new regime codes missing from the REGIMES array and REGIME_LABELS object.

When should this review checklist not be used?

Skip it for official-baseline command changes, plugin infrastructure, hooks, and agents, which have their own review surfaces. It is designed specifically for community overlay PRs adding or extending xx-* jurisdictional command bundles and recipes.

Why does converter drift happen in overlay PRs?

Authors often run scripts/converter.py at branch creation but not after rebasing onto main, so generated variants regress to older canonical commands. Re-run the converter on the PR branch and check git status; any output means stale generated files.

How is the review posted to GitHub?

The review is posted with gh pr comment using a heredoc body so the markdown renders correctly. The output always contains a verdict line, BLOCKERS, IMPORTANT, MINOR, and POSITIVE sections, plus a recommended pre-merge fix sequence.