Review pull requests by compiling project context, CI status, and changed files.
npx skills add https://github.com/gaogg521/1ONE-ClaudeCode --skill pr-review-gaogg521
Please help me install this Agent Skill. Skill: pr-review Source: https://github.com/gaogg521/1ONE-ClaudeCode/tree/main/.claude/skills/pr-review Command: npx skills add https://github.com/gaogg521/1ONE-ClaudeCode --skill pr-review-gaogg521
PR reviews often lack full project context when changes span multiple files and CI checks; this skill consolidates local PR analysis to ensure thorough, context-rich reviews.
Execute a full PR review by providing a PR number to start the workflow on the current repository.
High-intent search queries and answers about installing and using this skill.
Reviewing a pull request locally involves gathering PR metadata, validating CI status, creating an isolated git worktree, and linting changed files to produce a structured review report.
A git worktree creates an isolated working directory for parallel review, allowing you to safely inspect pull request changes without affecting your current local repository branch.
Yes, you can validate CI status to report readiness blockers and lint changed files within the isolated worktree to identify potential code quality issues before merging.
Analyzing cross-cutting code changes involves collecting diffs, changed files, and discussion comments to ensure a comprehensive evaluation of code quality and potential issues.
Yes, you need a local repository clone because the review process operates locally, extracting PR metadata and creating worktrees directly from your cloned repository to compile context.
billyfranklim1Diagnose and recover corrupted Git repository states with staged repairs.
glhewettMerge feature branches into a target branch and push it to remote.
DataRecceReview GitHub pull requests and post comments with test and linter evidence.
LamseyahEliasAnalyze GitHub diffs and generate inline PR review comments.
