dkarter/dotfiles/address-bot-pr-comments
Claude Code and agent skill by dkarter/dotfiles
- community
Checking that the SKILL.md file is still in the repository.
Review and address unresolved pull request comments authored by bots, not humans. Use when asked to evaluate automated PR review feedback, fix valid findings, explain rejected findings, reply to bot threads, and resolve completed threads.
Install
npx vskill@latest install dkarter/dotfiles/address-bot-pr-commentsSKILL.md
Address Bot PR Comments
Review unresolved bot-authored threads on the pull request identified by $ARGUMENTS, or the pull request for the current branch when no argument is provided.
Workflow
- Identify the pull request and fetch its unresolved review threads and any existing reply comments.
- Filter by the comment author. Process only comments clearly authored by a bot or automation account; do not act on human-authored comments unless explicitly requested by me.
- Verify every finding against the current code and repository guidance. Do not assume automated feedback is correct.
- Classify each finding:
- Fix valid issues with the smallest correct change.
- Reject invalid, obsolete, or inapplicable findings with a brief factual
reason.
- Leave ambiguous findings unresolved if they require human input.
- Only when a valid finding requires a major architectural change or many
code changes, stop before editing. Load the explain-simply skill, explain the issue and impact, then use the available user-question tool to ask whether to proceed. Continue only with explicit approval. Do not interrupt routine or small fixes.
- Run focused validation for each change, followed by the relevant broader
checks when practical.
- Commit fixes in small logical commits, ideally one commit per finding or
tightly related group. Use conventional commit messages and push once after all local work is complete.
- Reply briefly to every processed bot thread:
- For fixed findings, summarize the change and include the commit SHA.
- For rejected findings, explain why no change was made.
- For findings needing human input, state the unresolved question.
- Resolve a thread only after posting the reply and only when the finding is
fixed or conclusively rejected. Never resolve a thread that still requires human input.
Prefer GitHub MCP for pull request operations when available and gh as the fallback. Finish with a concise summary of fixed, rejected, and unresolved findings plus the validation performed.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingagents/skills/address-bot-pr-comments/SKILL.md
Popularity
- Repository stars
- 128
- Repository forks
- 14
- 7-day trend score
- 29
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/dkarter/dotfiles/address-bot-pr-comments)