mj-agent-doc-review

Reviews pull requests for documentation completeness against Meta v2.1 quality gate checklists.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull requests in the mj-agent project must satisfy a multi-framework documentation quality gate (Meta v2.1, Code_Side v1.1, Agent_Side v1.1), and manually verifying INDEX.md sync, CLAUDE.md tri-track sync, cross-reference integrity, and PR description structure is error-prone and slow. ## Core Features & Use Cases - PR-scope documentation checklist: Classifies changed files via git diff, then checks A1-A14 quality gate items across code-side, agent-side, and engineering-workflow tracks. - Cross-reference and sync validation: Detects broken wikilinks, missing INDEX.md entries, stale updated fields, and CLAUDE.md tri-track desync, including in-source canonical SKILL.md back-scans. - §4.7 dual-section PR description check: Verifies the PR body separates objective local verification from AI self-check content without mixing. - Use Case: Before merging a docs-touching PR, run this skill to produce a structured A1-A14 checklist with PASS/WARN/FAIL verdicts and an overall Approve or Changes Requested judgment. ## Quick Start Ask the assistant to review the current pull request's documentation completeness against the A1-A14 quality gate and output the PR documentation checklist.

Frequently Asked Questions about mj-agent-doc-review

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

FAQPage Schema
How do I check PR documentation completeness before merging?▼

Run this skill against the PR diff to classify changed files, verify INDEX.md and CLAUDE.md synchronization, scan for broken wikilinks, and produce an A1-A14 checklist with an overall Approve or Changes Requested verdict.

What is the difference between doc-review and doc-validate skills?▼

Doc-review operates at PR scope, orchestrating holistic checks across all changed files and quality gate items. Doc-validate performs per-file validation and is sub-called by doc-review during Phase 4 for each documentation change.

Does this skill review code architecture in pull requests?▼

No. Architecture and design review of others' PRs belongs to the git-review-pr skill, and responding to review comments belongs to flow-review-respond. This skill only checks documentation completeness and quality gate compliance.

What is the dual-section PR description requirement?▼

Per Meta v2.1 §4.7, PR descriptions must separate a local verification section containing objective repeatable checks like pytest runs from an AI self-check section covering generated-content credibility. Mixing items across sections triggers a WARN; missing sections trigger FAIL.

When are ADR or SPEC documents required for a PR?▼

New modules, APIs, or data flows require SPEC creation; bug fixes changing interfaces require SPEC updates; architecture, data boundary, or CI/CD changes require an ADR. The skill flags these triggers during its §12 pre-check phase.