pr-review
Find and fix code issues before publishing a PR. Single-pass review with auto-fix. Use when reviewing code changes before submission or auditing existing code for bugs/security. Don't use when running a coding agent to write code (use coding-agent) or checking GitHub CI status (use github).
Why use this skill?
Use the OpenClaw pr-review skill to automatically audit code, find security vulnerabilities, and fix bugs before you publish your pull requests.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/glucksberg/pr-reviewWhat This Skill Does
The pr-review skill is a specialized, single-pass automated code auditing tool designed for OpenClaw. It performs high-velocity analysis of your source code to identify bugs, security vulnerabilities, reliability bottlenecks, and performance issues before they ever reach a production environment. Unlike heavy agentic workflows that rely on complex orchestration or multi-step chains, pr-review delivers a concise, thorough report and auto-fixes in one cohesive pass, making it the ideal "gatekeeper" for your pull requests.
Installation
To integrate this skill into your environment, execute the following command in your terminal:
clawhub install openclaw/skills/skills/glucksberg/pr-review
Once installed, the skill becomes immediately available to analyze local code repositories and Git branches.
Use Cases
- Pre-PR Analysis: Review pending code changes against the
mainormasterbranch to ensure logic, security, and standards compliance before hitting the 'submit' button. - Security Auditing: Systematically scan legacy codebases for common vulnerabilities, such as injection flaws, insecure defaults, or exposed sensitive information.
- Refactoring Support: Validate specific files or directories after a major refactor to catch regression errors, null pointer exceptions, or asynchronous race conditions that might have been introduced.
- Quality Assurance: Ensure that new code adheres to established project conventions defined in
CONTRIBUTING.mdor existing linting configurations.
Example Prompts
- "Review the current diff against main and provide a summary of identified issues and potential fixes."
- "Perform a security audit on the
src/api/authdirectory to ensure no vulnerabilities exist in the login flow." - "Run a comprehensive code audit on all
.tsfiles in the repository and list the top 3 performance concerns."
Tips & Limitations
- Context Awareness: The skill automatically scans project files like
.eslintrc,package.json, andCLAUDE.mdto understand your specific coding style and environment. - Scope Management: For large projects, avoid running an audit on the root if the file count exceeds 50; instead, use file patterns or directory-specific paths to keep feedback cycles fast.
- Safety: Always review the auto-fix suggestions. While the model is highly capable, human oversight is recommended for critical system paths or complex logic changes.
- Exclusions: The tool automatically ignores
node_modules,dist,coverage, and.gitto focus exclusively on your source logic.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-glucksberg-pr-review": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-read, file-write
Related Skills
issue-prioritizer
Prioritize GitHub issues by ROI, solution sanity, and architectural impact. Use when triaging or ranking issues to identify quick wins, over-engineered proposals, and actionable bugs. Don't use when managing forks (use fork-manager) or general GitHub queries (use github). Read-only — never modifies repositories.
fork-manager
Manage forks with open PRs - sync upstream, rebase branches, track PR status, and maintain production branches with pending contributions. Supports automatic conflict resolution via --auto-resolve flag (spawns AI subagents to resolve rebase conflicts). Use when syncing forks, rebasing PR branches, building production branches that combine all open PRs, reviewing closed/rejected PRs, or managing local patches kept outside upstream. Requires Git and GitHub CLI (gh).
pr-ship
Pre-ship risk report for OpenClaw PRs. Dynamically explores the codebase to assess module risk, blast radius, and version-specific gotchas. Scores each finding by severity (🟢/🟡/🔴). Updated frequently with the latest OpenClaw version context — run `clawhub update pr-ship` regularly to stay current.
cross-ref
Cross-reference GitHub PRs and issues to find duplicates and missing links. Spawns parallel Sonnet subagents to semantically analyze the last N PRs and issues, finding PRs that solve the same problem (duplicates) and issues resolved by open PRs but not yet linked. Groups findings into thematic clusters, scores them by actionability, and offers rate-limited commenting or bulk actions (close, label). Use this skill when the user wants to find duplicate PRs, link issues to PRs, clean up a repo's cross-references, or audit PR/issue relationships. Also useful when the user says things like "find related PRs", "which PRs fix this issue", "are there duplicate PRs", "link issues and PRs", or "audit cross-references".
anti-pattern-czar
Detect and fix TypeScript error handling anti-patterns with state persistence and approval workflows. Use when scanning a codebase for silent error failures, empty catches, promise swallowing, or unlogged errors. Supports five modes — scan (detect all issues), review (interactive fix session), auto (batch fix with guardrails), resume (continue from last session), report (show progress). Triggers on phrases like 'scan for anti-patterns', 'fix error handling', 'find empty catches', 'anti-pattern czar', or 'check error handling'.