pr-address-feedback

Triages and resolves PR-Agent and SonarQube review feedback on GitHub pull requests.

8|3|Updated Jun 8, 2019
One-click install
npx skills add https://github.com/e-picsa/picsa-apps --skill pr-address-feedback-e-picsa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-address-feedback
Source: https://github.com/e-picsa/picsa-apps/tree/main/.agent/skills/pr-address-feedback
Command: npx skills add https://github.com/e-picsa/picsa-apps --skill pr-address-feedback-e-picsa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automated review bots like PR-Agent and SonarQube generate a mix of genuine bug reports, false positives, and stylistic suggestions that conflict with project conventions. Manually sorting through this feedback, deciding what to fix, and avoiding endless re-review loops consumes significant developer time and risks pushing untested changes. ## Core Features & Use Cases - Feedback Triage Matrix: Fetches PR comments, inline review comments, and CI check status via the GitHub CLI, then categorizes each finding as Accept & Fix, Push Back, or Escalate based on project standards like AGENTS.md, .pr_agent.toml, and sonar-project.properties. - Freshness Verification: Compares the reviewed commit SHA against the current branch HEAD to detect outdated feedback or in-progress reviews before acting on them. - Local Verification & Conditional Push: Runs Nx affected tests and lint checks locally before committing, and requires explicit user approval before pushing to remote. - Use Case: A developer opens a pull request and receives ten PR-Agent suggestions plus three SonarQube findings. The skill inspects all feedback, pushes back on suggestions violating Angular 21 Signal conventions, fixes the two genuine null-safety bugs, verifies locally, and asks before pushing. ## Quick Start Ask the AI to review and address the automated feedback on the current branch's open pull request.

Frequently Asked Questions about pr-address-feedback

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

FAQPage Schema
How do I address PR-Agent review comments automatically?▼

Use the GitHub CLI to fetch PR comments and inline review comments, then triage each finding against project conventions. Accept genuine bug fixes, push back on suggestions violating project standards, and verify changes locally with tests before pushing.

How to handle SonarQube false positives in pull requests?▼

Check whether the flagged rule is suppressed in sonar-project.properties, such as typescript:S2933 for readonly injected services. If the rule is intentionally ignored, push back with a technical rationale instead of changing the code.

Does PR-Agent re-run automatically after pushing new commits?▼

No, PR-Agent does not re-run automatically on push when handle_push_trigger is set to false. You must manually comment /review or /improve on the PR thread in GitHub and wait for the workflow to complete.

How do I check if PR review feedback is outdated?▼

Compare the commit SHA in the review's persistent comment metadata, such as head_sha or resolved_head_sha, against the current branch HEAD from git rev-parse. If the reviewed SHA is older, the feedback may not reflect the latest code.

When should I push back on automated code review suggestions?▼

Push back when suggestions violate project conventions, such as recommending @Input decorators instead of Angular Signal inputs, inline styles instead of Tailwind classes, or cosmetic renames excluded by .pr_agent.toml configuration.