ワンクリックでManusで任意のスキルを実行

pr-review-integration

スター7

フォーク1

更新日2026年1月13日 04:47

Review pull requests by integrating GitHub operations with Linear issue tracking. Use when: (1) Validating PR changes against Linear issue requirements, (2) Checking if PR addresses all acceptance criteria from Linear issues, (3) Creating comprehensive PR reviews that link code changes to project requirements, (4) Identifying gaps between PR changes and issue requirements, or (5) Posting review findings to both GitHub PRs and Linear issues. Combines GitHub CLI operations with Linear MCP functions for end-to-end PR review workflows.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

lambda-curry

lambda-curry/devagent

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

PR Review Integration

Review pull requests by integrating GitHub operations with Linear issue tracking. Validate code changes against project requirements and provide comprehensive reviews.

Prerequisites

GitHub CLI (gh) installed and authenticated
Linear MCP server configured and available
Access to both GitHub repository and Linear workspace

Complete PR Review Workflow

Step 1: Extract Context from PR

Get PR details:

gh pr view <pr-number> --json title,body,author,state,baseRefName,headRefName

Get changed files:

gh pr view <pr-number> --json files --jq '.files[].path'

Get PR diff:

gh pr diff <pr-number>

Extract Linear issue references:

gh pr view <pr-number> --json body --jq '.body' | grep -oE 'LIN-[0-9]+'

Step 2: Fetch Linear Issue Requirements

Get issue details:

mcp_Linear_get_issue({
  id: "LIN-123", // extracted from PR
  includeRelations: true // get related/blocking issues
})

Extract requirements from issue:

Parse issue description for acceptance criteria
Check labels for feature tags
Review comments for additional context
Check relatedTo and blocks for dependencies

Step 3: Analyze PR Changes

Review code changes:

gh pr diff <pr-number>
gh pr diff <pr-number> -- path/to/file
gh pr view <pr-number> --json files --jq '.files[] | "\(.path): +\(.additions) -\(.deletions)"'

Check PR status:

gh pr checks <pr-number>
gh pr view <pr-number> --json mergeable,mergeStateStatus

Step 4: Validate Against Requirements

Compare PR changes to issue requirements:

Check Feature Completeness:
- Does PR implement all acceptance criteria?
- Are all required features present?
- Are edge cases handled?
Check Code Quality:
- Follows project standards (AGENTS.md, Cursor rules)
- Proper error handling
- Tests included (if required)
- Documentation updated
Check Dependencies:
- Related issues addressed?
- Blocking issues resolved?
- Integration points considered?
Identify Gaps:
- Missing requirements
- Incomplete implementations
- Additional work needed

Step 5: Document Review Findings

Option A: GitHub PR Comment

gh pr comment <pr-number> --body "
## PR Review Summary

### ✅ Requirements Met
- [Requirement 1] - Implemented in [file]
- [Requirement 2] - Complete

### ⚠️ Gaps Identified
- [Gap 1] - Missing from issue LIN-123
- [Gap 2] - Needs additional work

### 📝 Code Quality
- Follows project standards
- [Additional notes]

### 🔗 Related Issues
- LIN-123 (main issue)
- LIN-124 (related)
"

Option B: Linear Issue Comment

mcp_Linear_create_comment({
  issueId: "LIN-123",
  body: `
## PR Review: #${prNumber}

### Status: ${reviewStatus}

### Requirements Coverage
${requirementsChecklist}

### Code Quality
${qualityNotes}

### Next Steps
${nextSteps}
  `
})

Option C: Update Linear Issue

mcp_Linear_update_issue({
  id: "LIN-123",
  state: "In Review", // or appropriate status
})

Best Practices

Always link PRs to Linear issues for traceability
Extract issue IDs early to fetch requirements
Validate against requirements first, then code quality
Document gaps clearly with specific file/line references
Update Linear issues with review findings
Use consistent review format for readability
Handle edge cases gracefully (no issue, multiple issues, etc.)

Reference Documentation

Review Patterns: See patterns.md for detailed patterns, edge cases, and checklist templates
GitHub CLI Operations: .codex/skills/github-cli-operations/SKILL.md - GitHub CLI patterns
Linear MCP Integration: .codex/skills/linear-mcp-integration/SKILL.md - Linear MCP functions

このリポジトリの他の Skills

同じリポジトリ

ai-rules-cli

lambda-curry/devagent

Use ai-rules CLI to manage and synchronize AI coding rules across multiple AI assistants (Cursor, Claude Code, GitHub Copilot, Opencode, etc.). Use when: (1) Setting up ai-rules in a new project, (2) Updating AI coding guidelines and best practices, (3) Generating platform-specific rule files from source, (4) Checking if generated files are in sync with source files, (5) Managing multi-agent rule consistency, or (6) Adding new rules or modifying existing ones. Requires ai-rules CLI installed. The ai-rules/ directory serves as the single source of truth for all AI coding guidelines.

2026-03-247

coderabbit-cli

lambda-curry/devagent

Use CodeRabbit CLI to perform automated code review and iterative improvement in an AI agent workflow. Use when: (1) After generating non-trivial code (new features, refactors, algorithms), (2) Improving code quality, maintainability, or readability before submission, (3) Validating code changes against best practices, (4) Exploring unfamiliar languages, patterns, or domains, or (5) Creating a self-reviewing coding loop. Requires CodeRabbit CLI installed and authenticated. Not for trivial changes (typos, formatting-only) or rapid prototyping without quality constraints.

2026-03-247

skill-creator

lambda-curry/devagent

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

2026-01-237

worktree-setup-hook

lambda-curry/devagent

Post-checkout git hook for automatic worktree setup. Use when: (1) Setting up automatic configuration for new git worktrees, (2) Creating post-checkout hooks that detect new worktrees and run setup tasks, (3) Configuring worktrees to automatically copy env files and install dependencies

2026-01-147

git-workspace

lambda-curry/devagent

"Work with git worktrees and workspaces for concurrent development. Use when: (1) Creating new workspaces with \`git worktree add\`, (2) Listing existing worktrees with \`git worktree list\`, (3) Removing worktrees with \`git worktree remove\`, (4) Pruning stale worktree metadata with \`git worktree prune\`, (5) Managing multiple checked-out branches simultaneously, (6) Migrating uncommitted work between workspaces, or (7) Any git workspace/worktree operation. Requires Git 2.5+ for worktree support."

2026-01-147

create-slash-command

lambda-curry/devagent

Create new slash commands for DevAgent workflows. Use when you need to create a new command file in .agents/commands/ and symlink it to .cursor/commands/ for Cursor IDE integration. This skill handles the complete command creation workflow including file generation, symlink creation, and structure validation.

2026-01-137