mj-agent-git-review-pr

Reviews other contributors' GitHub pull requests for architecture compliance and data-boundary safety.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/MJ-AgentLab/mj-agent --skill mj-agent-git-review-pr-mj-agentlab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mj-agent-git-review-pr
Source: https://github.com/MJ-AgentLab/mj-agent/tree/main/.claude/skills/mj-agent-git-review-pr
Command: npx skills add https://github.com/MJ-AgentLab/mj-agent --skill mj-agent-git-review-pr-mj-agentlab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing someone else's pull request in the mj-agent repository requires checking module boundaries, in-source canonical SKILL.md and prompt changes, biz_catalog drift, and SQL guardrail red lines—checks that are easy to miss manually. This Skill runs a structured five-stage audit so reviewers can decide whether a PR should be merged on architectural grounds. ## Core Features & Use Cases - Five-stage PR audit: Locates the PR via gh CLI, classifies changed files by mj-agent category, runs fixed checks (branch sync, commit convention) plus dynamically triggered checks (D1-D9) based on what changed. - mj-agent-specific risk lenses: Enforces mandatory stops for in-source SKILL.md canonical changes, system.md version bumps, biz_catalog drift against upstream schema, and SQL guardrail boundary expansion (ADR-006/009). - Human-in-the-loop publishing: Presents a severity-grouped review summary (Critical/Important/Suggestion) and asks before posting a comment to GitHub or merging, with double confirmation required for merges. - Use Case: A teammate asks "评审 PR #65". The Skill fetches the PR, detects it touches src/mj_agent/skills/**/SKILL.md, triggers the mandatory D3 canonical check, flags a missing eval_references update as Critical, and posts a structured review comment after your approval. ## Quick Start Ask the assistant to review PR #65 for architecture compliance in the mj-agent repository.

Frequently Asked Questions about mj-agent-git-review-pr

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

FAQPage Schema
How do I review someone else's pull request on GitHub with an AI assistant?▼

Provide the PR number, URL, or branch name and ask for an architecture review. The Skill uses the gh CLI to fetch PR metadata and diffs, classifies changed files, runs fixed and dynamically triggered checks, and produces a severity-grouped review summary you can approve before posting.

What is the difference between reviewing a PR and responding to review comments?▼

This Skill audits pull requests opened by other contributors for architecture and data-boundary compliance. Responding to reviewer feedback on your own PR is the opposite direction and is handled by the mj-agent-flow-review-respond skill instead.

Can this Skill merge a pull request automatically?▼

No. Merging only happens in the optional Stage 5 when a human explicitly requests it, and it requires two separate confirmation prompts before running gh pr merge with branch deletion. The Skill never merges autonomously.

What checks run when a PR changes SQL guardrail or catalog files?▼

Changes to SQL guardrail or precheck files trigger a mandatory stop checking ADR-006/009 data-boundary red lines. Changes to biz_catalog YAML trigger a drift comparison against the upstream schema using the diff_biz_schema.py script.

What are the prerequisites for running this PR review workflow?▼

You need an authenticated gh CLI, a local mj-agent worktree, and network access to the GitHub remote. The PR must be in OPEN state; closed or merged PRs cause the review to stop immediately.