kurojs/enderdots/pr-review
Claude Code and agent skill by kurojs/enderdots
- community
Checking that the SKILL.md file is still in the repository.
Review GitHub PRs and Issues with structured analysis for open source projects. Trigger: When user wants to review PRs (even if first asking what's open), analyze issues, or audit PR/issue backlog. Key phrases: "pr review", "revisar pr", "qué PRs hay", "PRs pendientes", "issues abiertos", "sin atención", "hacer review".
Install
npx vskill@latest install kurojs/enderdots/pr-reviewSKILL.md
The same SKILL.md was published earlier as kurojs/enderdots/pr-review.
When to Use
ALWAYS use this skill when user mentions "pr review", "revisar PRs", or asks about pending PRs/issues - even if they first ask what's pending. This skill handles the FULL flow: listing → analyzing → reviewing.
Specific triggers:
- User wants to review PRs (even if first asking what's open)
- Analyze issues or contributions
- Audit PR/issue backlog
- Check what needs attention
Key phrases: "pr review", "revisar", "qué hay pendiente", "sin atención", "PRs abiertos", "issues abiertos", "hacer review", "necesito revisar"
Review Process
Phase 1: Gather Information
Phase 2: Read Current Codebase
Before reviewing diffs, always read the current code to understand context:
- Main entry points
- Files being modified
- Related modules
Phase 3: Analyze Each PR
For each PR, evaluate these factors:
| Factor | What to Check | |
|---|---|---|
| Code Quality | Clean code, no duplication, proper error handling | |
| Tests | Are there tests? Do they cover the changes? | |
| Breaking Changes | Does it break existing functionality? | |
| Conflicts | Will it conflict with other open PRs? | |
| Commit Hygiene | Clean history, no test files, proper messages | |
| Documentation | README updated if needed, comments where necessary |
Critical Patterns
Red Flags (DO NOT MERGE)
- [ ] Test/debug files committed (
test.js,console.log, etc.) - [ ] Variables declared but never used
- [ ] Code duplication instead of refactoring
- [ ] Broken indentation or syntax errors
- [ ] Config files with personal/local settings
- [ ] Hardcoded secrets or credentials
- [ ] Breaking changes without migration path
Yellow Flags (Request Changes)
- [ ] Too many commits (should squash)
- [ ] Missing validation for dependencies (e.g.,
jq,curl) - [ ] Potential conflicts with other PRs
- [ ] Incomplete feature (e.g., variable declared but not used)
- [ ] Fallback code with bugs (e.g., not escaping newlines)
Green Flags (Good to Merge)
- [x] Small, focused changes
- [x] Tests included
- [x] Clean commit history (1-3 commits)
- [x] Documentation updated
- [x] No conflicts with other PRs
- [x] Solves a real issue
Decision Matrix
Output Format
For Issues
For PRs
Review Comments
Language Rules
Reply in the same language the author used in their PR/issue:
- PR written in Spanish → Reply in Spanish
- PR written in English → Reply in English
Comment Structure
{Concrete fix}
Examples:
- Spanish PR → "¡Hola Juan! Gracias por el PR, el análisis está muy bien hecho 👏"
- English PR → "Hey John! Thanks for the PR, the analysis is well done 👏"
Commands
Conflict Detection
When reviewing multiple PRs, check for conflicts:
- Same files modified - Check if PRs touch the same files
- Dependent features - PR A adds feature, PR B extends it
- Version bumps - Multiple PRs changing VERSION
- Provider patterns - New providers need to be added to all switch/case statements
Common Conflict Pattern: Provider Addition
When a PR adds timeout/wrapper logic with hardcoded providers:
Flag this - any PR adding new providers will conflict.
Merge Order Strategy
When multiple PRs have dependencies:
- Independent, small PRs first - Quick wins, no conflicts
- Infrastructure PRs second - Timeout, error handling, etc.
- Feature PRs third - New providers, modes, etc.
- Large refactors last - Most likely to have conflicts
Checklist Before Merging
- [ ] All tests pass (if CI exists)
- [ ] No red flags in code
- [ ] No conflicts with recently merged PRs
- [ ] Author's branch is up to date with main
- [ ] Review comments addressed (if any)
Security
- Security scanPassed, 90 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 repositoryChecking.config/opencode/skills/pr-review/SKILL.md
Popularity
- 7-day trend score
- 0
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/kurojs/enderdots/pr-review)