Help us improve
Share bugs, ideas, or general feedback.
Reviews backend pull requests for correctness, security, performance, maintainability, and test coverage using GitHub CLI and local repository inspection.
npx claudepluginhub jawwadfirdousi/agent-skills --plugin read-only-gh-pr-reviewHow this skill is triggered — by the user, by Claude, or both
Slash command
/read-only-gh-pr-review:read-only-gh-pr-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Review backend pull requests end-to-end using local code analysis and GitHub CLI API calls. Report only actionable, high-signal findings.
Reviews GitHub pull requests via gh CLI or API, fetching diffs and analyzing files for code quality, security vulnerabilities, performance issues, and best practices violations.
Reviews GitHub pull requests using gh CLI, analyzing diffs for code quality, security, testing, best practices, and providing structured feedback.
Reviews backend PRs for security, performance, code quality, and testing gaps across any stack. Supports GitHub, GitLab MRs, and local git diffs.
Share bugs, ideas, or general feedback.
Review backend pull requests end-to-end using local code analysis and GitHub CLI API calls. Report only actionable, high-signal findings.
SemanticSearch, WebSearch, Grep, LS, Glob, Read, Shell, GitHub CLI.gh command, source the read-only environment script to enable security enforcement:
source "<SKILL_DIR>/scripts/activate-gh-readonly.sh"
Replace <SKILL_DIR> with the absolute path to this skill directory.gh commands directly—they are intercepted by the read-only wrapper.gh auth status. If not authenticated, ask the user to run gh auth login.command gh and other bypass attempts.source "<SKILL_DIR>/scripts/activate-gh-readonly.sh"gh commands in this shell session are now protected.gh auth status, gh api user.-R <OWNER>/<REPO>.gh pr view <PR_NUMBER> [--json <fields>] when PR number is known.gh pr list [flags] and pick the target PR.headRefName).git fetch --prune origin <HEAD_BRANCH>.FETCH_HEAD or check out a local review branch from it.gh pr view <PR_NUMBER> [--json <fields>]gh pr diff <PR_NUMBER> [--patch|--name-only]gh api repos/<OWNER>/<REPO>/pulls/<PR_NUMBER>/files --paginategh api repos/<OWNER>/<REPO>/pulls/<PR_NUMBER>/reviews --paginategh pr checks <PR_NUMBER> [--json <fields>]gh pr view <PR_NUMBER> --commentsgh api repos/<OWNER>/<REPO>/issues/<PR_NUMBER>/comments --paginategh api repos/<OWNER>/<REPO>/pulls/<PR_NUMBER>/comments --paginateRead, Grep) and correlate with diff hunks.gh api repos/<OWNER>/<REPO>/contents/<PATH>?ref=<REF> when exact remote content is needed (content is usually base64 in .content).references/review-checklist.md.file:line, impact, and concrete fix guidance.Use this section order:
Critical Issues (Must Fix)Important Issues (Should Fix)Suggestions (Consider)Good Practices NotedFor each issue, use:
Issue: <brief description>
Location: <file:line>
Severity: <Critical|High|Medium|Low>
Problematic Code: <snippet or precise behavior>
Suggestion: <specific fix>
Example: <optional patch-style snippet>
Use command mappings in references/github-cli-map.md.