addressing-pr-feedback — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited addressing-pr-feedback (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Fetch PR review comments, separate bot suggestions from human feedback, present a summary, then let the user select which comments to address.
git branch --show-currentgh pr list --head <branch> --json number,title,url --jq '.[0]'# Inline review comments (on specific code lines)
gh api repos/{owner}/{repo}/pulls/<PR_NUMBER>/comments
# General PR comments
gh api repos/{owner}/{repo}/issues/<PR_NUMBER>/comments
# Review summaries
gh api repos/{owner}/{repo}/pulls/<PR_NUMBER>/reviewsKey fields:
created_at — display as relative time ("2 hours ago")position — null means outdated (code changed since comment)in_reply_to_id — reply thread, group with parentpath — file the comment is on| Category | Detection | Priority |
|---|---|---|
| Bot | Username contains [bot], ends with bot, or is a known CI tool | Lower — automated suggestions |
| Human | All other usernames | Higher — requires response |
## PR #123: "Add authentication flow"
### Human Reviewers (2 comments) — HIGH PRIORITY
- @alice: 1 comment on src/auth.ts (2 days ago)
- @bob: 1 comment on src/utils.ts (5 hours ago) ⚠️ OUTDATED
### Bot Suggestions (5 comments)
- 3 style/formatting (1 day ago)
- 2 potential improvements (1 day ago) ⚠️ 1 OUTDATEDMark comments as ⚠️ OUTDATED when position is null (code changed since the comment was posted).
Use AskUserQuestion with multiSelect: true:
Which comments do you want me to address?
[ ] @alice: "Consider adding error handling for timeout" (2 days ago)
[ ] @bob: "This function could be simplified" (5h ago) ⚠️ OUTDATED
[ ] bot: "Missing return type annotation" (3 similar, 1 day ago)Group similar bot comments to reduce noise. Show relative timestamps. Mark outdated comments — the user may skip these.
Dumping all comments raw: Always summarize and group first.
Treating all comments equally: Human comments get priority display over bot suggestions.
Open-ended questions: Use checkbox selection, not "which ones do you want me to fix?"
Fixing without asking: Always let the user select which comments to address.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.