Resolve Pr Comments
This skill should be used when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", "respond to PR review", or explicitly invokes "resolve-pr-comments".
Install
$ agentstack add skill-fcakyon-claude-codex-settings-resolve-pr-comments ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-fcakyon-claude-codex-settings-resolve-pr-comments) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Resolve PR Comments
Analyze unresolved PR review comments, fix valid concerns, and draft responses for comments that do not require code changes.
When explicitly invoked with extra text, treat that text as the PR number or URL. If no PR reference is provided, infer it from the current branch.
Process
- Preferred execution
- If subagents are available, use
github-dev:pr-comment-resolverand pass the PR reference. - Otherwise follow the manual steps below.
- Fetch unresolved comments
- If a PR number or URL is provided, use it directly.
- Otherwise auto-detect the PR from the current branch with
gh pr view --json number,headRefName. - Fetch inline comments with
gh api repos/{owner}/{repo}/pulls/{number}/comments. - Fetch review-level comments with
gh pr view --json reviews,comments. - Filter to unresolved or pending threads.
- Resolve each comment
- If the comment is valid, fix the code and search the codebase for the same problem in other locations.
- Fix all matching occurrences, not just the location mentioned in the comment.
- If the comment does not require a code change, draft a concise reply.
- If the comment is from a bot, reply with a direct factual sentence and no pleasantries.
- Reply style
- Start in lowercase.
- Use simple language and short sentences.
- Avoid end punctuation when possible.
- Be concise and polite when replying to real people.
- Never auto-submit
- Present all draft responses before posting them.
- Reply comments are posted directly with
gh api repos/{owner}/{repo}/pulls/comments/{comment_id}/replies -f body="...". - Add a random 3-5 second delay between posted replies with
sleep $((RANDOM % 3 + 3)).
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: fcakyon
- Source: fcakyon/claude-codex-settings
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.