Generate policy-aligned PR review JSON from GitHub diffs or local git changes.
npx skills add https://github.com/abeyuya/skills --skill compose-review
Please help me install this Agent Skill. Skill: compose-review Source: https://github.com/abeyuya/skills/tree/main/plugins/pr-review/skills/compose-review Command: npx skills add https://github.com/abeyuya/skills --skill compose-review
PR diffs and local branch changes often require consistent, policy-driven review comments that are hard to assemble quickly and in the right schema for downstream posting.
comments[] array with normalized file/line targeting and labeled guidance intended for a structured PR-review workflow.Use Case: For a GitHub PR, generate a complete review body and inline comment set (or a “no issues” response) based on diff content and existing thread/CI context, ready for the orchestrator to post.
Ask the agent to generate a policy-aligned PR review JSON for the current PR diff and return the result as a single un-fenced JSON text.
High-intent search queries and answers about installing and using this skill.
You generate structured inline comments by reading PR diffs and producing a single JSON object with a comments array, using normalized file and line targeting for the GitHub PR review workflow.
Yes, local git branch comparisons can be used to create policy-driven code review output by applying diff-mode selection and referencing project instruction files like REVIEW.md or CLAUDE.md.
The best way to enforce a consistent JSON schema for automated PR diff analysis is to read style references and project instructions, returning a single final JSON object that matches the required schema.
Yes, it supports merging findings from one available external host review skill in read-only mode, combining those results with its own review while avoiding duplicate or out-of-diff remarks.
When errors occur during code review generation, the process handles them by returning only a simple JSON object containing an error message, ensuring downstream parsing does not break.
You do not strictly need a REVIEW.md file; the process searches for the first matching project instruction file among REVIEW.md, AGENTS.md, or CLAUDE.md to decide review priorities.
delaanthonioReview local code changes with the CodeRabbit CLI.
naruseniaPost PR review findings as GitHub inline comments.
Othmane-KhadriAnalyze Claude Code and YALC skill registries to plan a conflict-free integration.
ian-pascoeInspect and control live Hunk diff review sessions via CLI.