active-review

Generate prioritized PR review summaries and GitHub deep-linked comment drafts.

9|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/paultyng/skill-issue --skill active-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: active-review
Source: https://github.com/paultyng/skill-issue/tree/main/skills/active-review
Command: npx skills add https://github.com/paultyng/skill-issue --skill active-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually preparing for pull request code reviews is time-consuming, prone to missing high-risk changes, and requires tedious work to draft feedback and create deep-links to specific code lines. This Skill automates that prep work, letting reviewers focus on the most important changes and post feedback faster.

Core Features & Use Cases

  • Concise PR Summary: Distills the PR's purpose, changes, and overall risk profile into 2-3 scannable sentences.
  • Prioritized File Ranking: Ranks up to 5 highest-impact files to review first, weighted by finding severity, volume of changes, and boundary risk (security, API contracts, data paths).
  • Paste-Ready Inline Comments: Generates short, imperative comment drafts with GitHub deep-links for all untracked medium+ severity findings, no manual link crafting required.
  • Use Case: When you're assigned to review a large feature PR with dozens of changed files, use this skill to instantly identify the riskiest areas and draft actionable feedback to post manually, cutting review prep time from 30 minutes to 5.

Quick Start

Ask the active-review skill to prepare terse PR review summaries and inline comment drafts for the pull request you need to review manually.

Frequently Asked Questions about active-review

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

FAQPage Schema
How do I prepare GitHub PR review comments faster for large pull requests?

Automate PR review prep by distilling automated review artifacts into concise summaries and paste-ready inline comment drafts. This process identifies high-risk files and generates GitHub deep-linked comments, cutting manual review preparation time significantly.

What is the best way to prioritize files for code review on a complex pull request?

Prioritize files for code review by ranking them based on finding severity, volume of changes, and boundary risks like security or API contracts. This highlights the top five highest-impact files to focus your manual review effort.

Can I generate GitHub deep-linked inline comments for PR findings without manual link crafting?

Yes, you can generate paste-ready inline comments with GitHub deep-links automatically. The system drafts short, imperative feedback for untracked medium and higher severity findings, eliminating the need to manually craft links to specific code lines.

Does this code review prep tool support re-reviewing updated pull requests?

Yes, the code review prep tool supports re-reviewing updated pull requests. It performs gap analysis against existing comments to ensure reviewers only see new or unresolved findings, preventing redundant feedback on previously reviewed code.

Are the PR review summaries and draft comments based on fabricated findings?

No, the PR review summaries and draft comments are not fabricated. The system enforces strict no-fabrication rules, ensuring all findings and inline comment drafts are derived entirely from pre-generated review artifacts.

How do I review a pull request when I only have pre-generated review summaries?

Consume pre-generated review summaries to produce concise PR overviews and draft inline comments. This satisfies non-posted code review prep requirements by transforming existing automated outputs into actionable, prioritized feedback for human reviewers.