Address PR review comments systematically. Use when responding to code review feedback on a pull request.
Scanned 5/27/2026
Install via CLI
openskills install saffron-health/libretto---
name: address-review
description: Address PR review comments systematically. Use when responding to code review feedback on a pull request.
---
Address PR review comments systematically.
## Process
1. **Get review comments**: Use `gh api graphql` to fetch all review threads and comments for the PR. (If a PR number is not provided in the input, look up the PR for the current branch).
2. **Analyze comments**: Review all the feedback to understand what changes are needed
3. **Address each comment systematically**: For each review comment:
- Make the requested code changes
- Verify the changes fix the issue raised
- Add explanatory comments if the reviewer requested clarification
- Test changes to ensure they don't break existing functionality
4. **Quality assurance**: Run type-check, build, and lint to ensure all changes are correct
5. **Commit and push**: Stage and commit all changes with an appropriate message and push.
6. **Mark comments resolved**: Query PR review threads with `gh api graphql` to get thread IDs and outdated status. Resolve all addressed threads using `mutation { resolveReviewThread(input: {threadId: "THREAD_ID"}) { thread { isResolved } } }`. Always resolve outdated threads.
## Implementation Pattern
```
// Query review threads:
gh api graphql -f query='query { repository(owner: "owner", name: "repo") { pullRequest(number: N) { reviewThreads(first: 100) { nodes { id isResolved isOutdated comments { nodes { body } } } } } } }'
// Resolve thread:
gh api graphql -f query='mutation { resolveReviewThread(input: {threadId: "THREAD_ID"}) { thread { isResolved } } }'
```
## Notes
- Only address reviews from human users; ignore bot reviews (e.g., Claude) unless explicitly requested
- Use sub-agents to handle independent review comments in parallel when possible
- Always verify changes don't introduce new issues
- If a review comment requires clarification, document the approach taken
- Focus on the specific issues raised rather than making additional changes
- Mark outdated comments as resolved automatically since they no longer apply to current code
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.
Python backend development expertise for FastAPI, security patterns, database operations, Upstash integrations, and code quality. Use when: (1) Building REST APIs with FastAPI, (2) Implementing JWT/OAuth2 authentication, (3) Setting up SQLAlchemy/async databases, (4) Integrating Redis/Upstash caching, (5) Refactoring AI-generated Python code (deslopification), (6) Designing API patterns, or (7) Optimizing backend performance.
Drive the full internationalization journey for a project — detect the stack, recommend a library, set up the chosen library, wrap existing strings, and optionally connect a translation platform. Use when the user asks to add or configure i18n, internationalization, localization, multi-language support, or translations — including when they explicitly mention LinguiJS, Lingui, next-intl, "wrap strings", "find hardcoded text", "make my app translatable", or "set up translations". Triggers on g...
PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.