address-review

Categorize PR feedback and verify changes against project conventions.

20|4|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/nbramia/LifeOS --skill address-review-nbramia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: address-review
Source: https://github.com/nbramia/LifeOS/tree/main/.agents/skills/address-review
Command: npx skills add https://github.com/nbramia/LifeOS --skill address-review-nbramia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Address PR review feedback efficiently by providing an independent verification process that confirms changes align with project standards and reviewer intent.

Core Features & Use Cases

  • Categorize feedback: automatically classify each comment as Action Required, Recommended, or Minor.
  • Independent verification: read relevant files, diffs, and tests to validate the suggested changes.
  • Audit-ready reports: produce a concise rationale and decision log suitable for PR comments or documentation.

Quick Start

Review PR #$ARGUMENTS and run the independent verification workflow to identify and resolve conflicting feedback.

Frequently Asked Questions about address-review

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

FAQPage Schema
How do I address pull request feedback efficiently?

Address pull request feedback efficiently by categorizing comments as Action Required, Recommended, or Minor, then independently verifying suggested changes against files and tests to produce an audit-ready decision log.

How do I verify code review recommendations before applying them?

Verify code review recommendations by inspecting relevant files and diffs, comparing changes against project conventions and tests, and documenting the justification for chosen actions before committing updates.

What is independent PR feedback verification?

Independent PR feedback verification is a process that gathers repository review comments, analyzes action items, and validates suggested changes by inspecting diffs and tests to ensure safe, auditable PR guidance.

Does PR review verification work without external dependencies?

PR review verification works without external dependencies, running a standalone workflow that reads repository diffs, tests, and project conventions to categorize feedback and generate a concise report.

What's the best way to resolve conflicting PR review comments?

The best way to resolve conflicting PR review comments is to apply independent verification, inspecting the underlying files and tests to determine which recommendations align with project conventions before escalating unresolved issues.

When should I escalate PR feedback instead of resolving it directly?

Escalate PR feedback when independent verification of files, diffs, and tests cannot confirm that suggested changes align with project conventions, ensuring unresolved issues are documented in the final report.