بنقرة واحدة
github-pr
GitHub PR utilities for code review workflows
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
GitHub PR utilities for code review workflows
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generate a project tree annotated with context.md notes to help future sessions, (auto-call at session start)
Generate a project tree annotated with context.md notes to help future sessions, (auto-call at session start)
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Automated PR code review with multi-agent analysis
Capture solved problems as searchable documentation with pattern detection. This skill auto-triggers when users confirm a fix worked ("that worked", "it's fixed", "working now") or manually via /compound command.
List and get Linear issues via CLI (read-only operations)
| name | github-pr |
| description | GitHub PR utilities for code review workflows |
| version | 0.1.0-beta |
| license | MIT |
| compatibility | opencode |
CLI tools for GitHub pull request operations. Designed to support automated code review workflows. Requires the GitHub CLI (gh) to be installed and authenticated.
brew install gh
gh auth login
Determines if a PR should be reviewed by checking various conditions.
bun .opencode/skill/github-pr/check-review-needed.js [pr-number]
Arguments:
pr-number - PR number (optional, defaults to current branch's PR)Output: JSON object with:
shouldReview - boolean indicating if review should proceedreason - explanation for the decisionprNumber - the PR number checkedConditions checked:
Examples:
# Check current branch's PR
bun .opencode/skill/github-pr/check-review-needed.js
# Check specific PR
bun .opencode/skill/github-pr/check-review-needed.js 123
Finds AGENTS.md (or CLAUDE.md) files relevant to a PR's changes.
bun .opencode/skill/github-pr/list-guideline-files.js [pr-number] [--json]
Arguments:
pr-number - PR number (optional, defaults to current branch's PR)Options:
--json - Output as JSON array with file contentsSearch locations:
Priority: If both AGENTS.md and CLAUDE.md exist in the same directory, AGENTS.md takes precedence.
Examples:
# List guideline files for current PR
bun .opencode/skill/github-pr/list-guideline-files.js
# Get full content as JSON
bun .opencode/skill/github-pr/list-guideline-files.js 123 --json
JSON Output Format:
[
{
"path": "AGENTS.md",
"content": "# Project Guidelines\n..."
},
{
"path": "src/components/AGENTS.md",
"content": "# Component Guidelines\n..."
}
]
Posts a review comment on a specific line or line range in a PR.
bun .opencode/skill/github-pr/post-inline-comment.js <pr-number> --path <file> --line <n> --body <text>
Arguments:
pr-number - PR number (optional if on a PR branch)Options:
--path <file> - File path to comment on (required)--line <n> - Line number to comment on (required)--start-line <n> - Start line for multi-line comments (optional)--body <text> - Comment body in markdown (required)Suggestion blocks: Include a suggestion block for small fixes that can be committed directly:
Fix the error handling:
```suggestion
try {
await authenticate();
} catch (e) {
handleAuthError(e);
}
```
Important: Suggestions must be complete. The author should be able to click "Commit suggestion" without needing additional changes elsewhere.
Examples:
# Single line comment
bun .opencode/skill/github-pr/post-inline-comment.js 123 \
--path src/auth.ts \
--line 67 \
--body "Missing error handling for OAuth callback"
# Multi-line comment (lines 65-70)
bun .opencode/skill/github-pr/post-inline-comment.js 123 \
--path src/auth.ts \
--line 70 \
--start-line 65 \
--body "This authentication block needs refactoring"
These tools wrap the GitHub CLI (gh). For operations not covered by these utilities, use gh directly:
# View PR details
gh pr view 123 --json title,body,state,isDraft,files
# Get PR diff
gh pr diff 123
# View PR comments
gh pr view 123 --comments
# Post a regular comment
gh pr comment 123 --body "Comment text"
# View file at PR head
gh api repos/{owner}/{repo}/contents/{path}?ref={branch}
--json flag when you need to process output programmatically