mj-agent-flow-review-respond

Classifies PR review comments and drafts modification plans with reply templates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Handling review feedback on your own pull request is chaotic: comments mix bugs, style nits, requirement changes, and CI failures, and some touch high-risk surfaces like API contracts, schemas, or prompt definitions that demand human sign-off. This Skill fetches PR reviews via the GitHub CLI, triages every comment, and produces a structured response plan so nothing is missed or silently changed. ## Core Features & Use Cases - Comment classification: Categorizes each review comment into bug, suggestion, style, architecture, requirement, test, or CI failure, with P0/P1/P2 priority levels. - Impact assessment: Evaluates effects on linked Plan/SPEC/ADR documents plus mj-agent-specific high-risk surfaces (in-source canonical skills, biz_catalog, SQL guardrail, system.md version), escalating to HITL pause when requirement, API, schema, permission, or user-visible behavior is touched. - Reply drafting: Generates per-comment reply drafts (accept, push-back with technical reasoning, clarify, defer-to-followup, CI-fix) plus a modification plan with target files, commit shape, and retest commands. - Use Case: After a reviewer requests changes on your mj-agent PR and mypy fails in CI, run this Skill to get a per-comment table, a High-risk HITL question for the API change, and ready-to-paste reply drafts. ## Quick Start Ask the assistant to process the review comments on your current mj-agent pull request and draft responses for each comment.

Frequently Asked Questions about mj-agent-flow-review-respond

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

FAQPage Schema
How do I respond to review comments on my GitHub pull request?▼

Fetch the PR feedback with gh pr view --json reviews,comments, then classify each comment by type and priority, draft a modification plan per comment, and write reply drafts. This Skill automates that triage and outputs a per-comment table with replies you paste manually.

How to triage PR review feedback by priority?▼

Classify each comment into bug, suggestion, style, architecture, requirement, test, or CI failure, then assign P0 for must-fix items like bugs and CI failures, P1 for requirement clarifications and test gaps, and P2 for style or optional improvements.

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

Responding to reviews means processing feedback on your own PR and drafting replies, while reviewing a PR means auditing someone else's code for architecture compliance. This Skill handles only the response direction; use a PR review skill for auditing others' work.

When should a review comment trigger human approval before changes?▼

Comments touching requirements, public API signatures, database schemas, permissions, or user-visible behavior require explicit human sign-off. In mj-agent, changes to in-source canonical skills, biz_catalog, SQL guardrails, or system.md version also force a HITL pause.

Does this Skill automatically reply to reviewers or commit fixes?▼

No. It only outputs reply drafts, modification plans, and retest commands. You must manually paste replies to GitHub, apply code changes, and create commits through separate workflow steps.