ben-architect-review

Reviews pull requests against architectural principles and drafts GitHub review comments.

3|5|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/BenSheridanEdwards/ArchitectPlaybook --skill ben-architect-review-bensheridanedwards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ben-architect-review
Source: https://github.com/BenSheridanEdwards/ArchitectPlaybook/tree/main/ben-architect-review
Command: npx skills add https://github.com/BenSheridanEdwards/ArchitectPlaybook --skill ben-architect-review-bensheridanedwards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing pull requests for architectural risk is time-consuming and inconsistent, and it is easy to miss lifecycle timing bugs, state invariant violations, or integration boundary issues hidden in a diff. This Skill applies a fixed set of architectural review principles to a pull request and produces a calibrated approve, comment, or request-changes decision with concrete inline comments. ## Core Features & Use Cases - Principles-based PR inspection: Reads the pull request description, diff, existing discussion, and CI status, then traces the change through lifecycle timing, state invariants, integration boundaries, and test coverage. - Calibrated decision ladder: Classifies the outcome as approve, approve with notes, comment only, request changes, or needs deeper thought, with explicit rules separating blockers from taste. - Safe GitHub posting: Drafts the review body and inline comments, prints a chat summary, and only posts a pending review or submits it after explicit user confirmation. - Use Case: Given a pull request that claims to fix an end-to-end locator issue, the Skill checks whether CI actually reaches the browser assertion, flags the gap as a blocker, and drafts a request-changes review with the smallest fix. ## Quick Start Ask the assistant to run /ben-architect-review on a specific pull request URL and wait for the drafted review summary before confirming whether to post it as pending or submit it on GitHub.

Frequently Asked Questions about ben-architect-review

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

FAQPage Schema
How do I review a pull request for architectural issues?

Run /ben-architect-review with the pull request URL. It inspects the diff, CI status, and discussion, traces the change through lifecycle, state, and integration risks, then drafts a decision with inline comments before asking whether to post it.

How does the skill decide between approve and request changes?

It requests changes only for concrete user-visible, state, security, accessibility, release, or product-constraint failure modes. Real but non-blocking risks become comments or approval notes, and style or naming preferences are never blockers.

Does it post GitHub reviews automatically?

No. It always prints a review package summary first and asks whether to post a pending review or submit. It never submits an approval, request-changes, or public comment without explicit user confirmation.

Can I force a specific review decision like approve or request changes?

Yes, pass --decision=approve, --decision=request-changes, or --decision=comment with the pull request URL. The skill drafts toward that shape unless the evidence contradicts it, in which case the evidence wins.

What is the difference between ben-architect-review and the architecture audit skill?

ben-architect-review judges one specific pull request and drafts GitHub review comments. The architecture-audit skill scans an entire codebase for module-boundary, coupling, and convention problems independent of any pull request.

What happens if the pull request head changes after the review is drafted?

The skill re-checks the head commit before posting or submitting. If it changed, it stops, refreshes the diff, and re-runs the relevant review steps rather than posting a stale review.