review-pr
The review-pr skill analyzes GitHub pull requests for bugs, security issues, performance problems, and missing tests by fetching diffs and changed files, then creates pending review comments highlighting only issues requiring fixes while skipping generated or vendored code. Use this skill when a user requests code review of a pull request by number, URL, or branch reference.
git clone --depth 1 https://github.com/fcakyon/claude-codex-settings /tmp/review-pr && cp -r /tmp/review-pr/plugins/github-dev/skills/review-pr ~/.claude/skills/review-prSKILL.md
# Review PR Review a pull request for bugs, regressions, missing tests, and risky 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 1. **Preferred execution** - If subagents are available, use `github-dev:pr-reviewer` and pass the PR reference. - Otherwise follow the manual steps below. 2. **Parse PR reference** - If a PR number or URL is provided, extract owner, repo, and PR number. - If not, auto-detect the PR from the current branch with `gh pr view --json number,headRefName`. 3. **Fetch PR data** - Use `gh pr diff <number>` for the full diff. - Use `gh pr view <number> --json files` for the changed file list. - Skip generated or vendored files such as `.lock`, `.min.js`, `.min.css`, `dist/`, `build/`, `vendor/`, `node_modules/`, `_pb2.py`, and images. 4. **Review focus** - Only report issues that require fixes. - Only review PR changes, never pre-existing issues in unchanged code. - Prioritize bugs, security issues, breaking changes, performance issues, edge cases, and missing tests. - Combine related issues that share the same root cause. - Keep the list short and high signal. 5. **Review comment rules** - Only create pending PR comments, never submit or confirm the review automatically. - Use `gh` for GitHub operations. - Start comments in lowercase, keep them short, avoid end punctuation when possible. - Use simple language for both bot-facing and human-facing comments. ## Output Format If issues are found, report them in descending severity with file references and a final recommendation of `NEEDS_CHANGES`. If no issues are found, return `APPROVE - No fixes required`.
Agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Manages MongoDB Atlas Stream Processing (ASP) workflows. Handles workspace provisioning, data source/sink connections, processor lifecycle operations, debugging diagnostics, and tier sizing. Supports Kafka, Atlas clusters, S3, HTTPS, and Lambda integrations for streaming data workloads and event processing. NOT for general MongoDB queries or Atlas cluster management. Requires MongoDB MCP Server with Atlas API credentials.
This skill should be used when user asks to "query Azure resources", "list storage accounts", "manage Key Vault secrets", "work with Cosmos DB", "check AKS clusters", "use Azure MCP", or interact with any Azure service.
This skill should be used when user asks to "clean gone branches", "remove deleted local branches", "prune branches removed from remote", or explicitly invokes "clean-gone-branches".
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or explicitly invokes "commit-staged".
This skill should be used when user asks to "create a PR", "make a pull request", "open PR for this branch", "submit changes as PR", "push and create PR", or explicitly invokes "create-pr".