PRの変更内容を分析し、後続のコードレビューフェーズに必要な情報を構造化して出力するスキルです。
Works with
軽量モデル（Haiku）での実行を想定しており、CI環境でのコスト最適化に寄与します。
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpr-triageExecute the skills CLI command in your project's root directory to begin installation:
Fetches pr-triage from xtone/ai_development_tools and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate pr-triage. Access via /pr-triage in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
3
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
3
stars
PRの変更内容を分析し、後続のコードレビューフェーズに必要な情報を構造化して出力するスキルです。 軽量モデル（Haiku）での実行を想定しており、CI環境でのコスト最適化に寄与します。
gh pr view <PR番号> --json title,body,headRefName,baseRefName,changedFiles でPR情報を取得gh pr diff <PR番号> --name-only で変更ファイル一覧を取得gh pr diff <PR番号> でコード差分を取得gh pr diff <PR番号> -- <file> で取得.pr-review-state.json が存在するか確認する（前回レビュー状態）.pr-triage.json ファイルに出力する前回のレビュー状態を活用してチェック範囲を最適化する：
.pr-review-state.json の last_reviewed_commit を取得するgit diff <last_reviewed_commit>..HEAD --name-only で前回レビュー以降に変更されたファイルを特定するsurface_issues は前回の状態からそのまま引き継ぐ（"carried_over": true を付与）。再チェックしない。surface_issues と review_comments のうち、該当箇所が修正されたものを resolved_issues に含める.pr-triage.json に "incremental": true、"base_commit"、"changed_since_last_review"、"unchanged_since_last_review"、"resolved_issues" フィールドを追加するresolved_issues のフォーマット：
{
"comment_id": 12345678,
"file": "<ファイルパス>",
"line": 42,
"issue": "<元の問題の説明>",
"resolution": "fixed"
}
.pr-review-state.jsonが存在しない場合は、通常のフルトリアージを実行する。.pr-review-state.jsonが不正な形式（JSONパースエラー等）の場合は、警告を出力してフルトリアージを実行する。破損した状態ファイルに基づいてインクリメンタルモードを実行してはならない。
以下の条件に該当する場合のみ、対応するリファレンスを required_references に含める：
typescript-best-practices.mdauthorization-review-general.mdauthorization-review-postgres-rls.mdskill-review.mdgithub-pr-review-actions.md（常に含める）差分を確認し、以下の問題を検出する（該当するもののみ）：
any 型の使用（TypeScript）var キーワードの使用（TypeScript/JavaScript）.pr-triage.json に以下のJSON構造で出力すること：
{
"pr_number": 123,
"incremental": false,
"base_commit": "<前回レビュー時のコミットSHA（インクリメンタル時のみ）>",
"summary": "<変更の概要（1-2文）>",
"files": {
"added": ["<追加ファイルパス>"],
"modified": ["<変更ファイルパス>"],
"deleted": ["<削除ファイルパス>"]
},
"changed_since_last_review": ["<前回から変更があったファイル（インクリメンタル時のみ）>"],
"unchanged_since_last_review": ["<前回から変更がないファイル（インクリメンタル時のみ）>"],
"languages": ["<検出された言語>"],
"frameworks": ["<検出されたフレームワーク>"],
"change_categories": {
"has_auth_changes": false,
"has_db_changes": false,
"has_rls_changes": false,
"has_api_changes": false,
"has_test_changes": false,
"has_config_changes": true,
"has_skill_changes": true
},
"required_references": ["<必要なリファレンスファイル名>"],
"surface_issues": [
{
"severity": "Minor|Suggestion",
"file": "<ファイルパス>",
"line": 15,
"issue": "<問題の説明>",
"suggestion": "<改善案>",
"carried_over": true
}
],
"resolved_issues": [
{
"comment_id": 12345678,
"file": "<ファイルパス>",
"line": 42,
"issue": "<元の問題の説明>",
"resolution": "fixed"
}
],
"diff_summary": "<差分の要約（200文字以内）>",
"estimated_complexity": "low|medium|high",
"focus_areas": ["<レビュー時の注目ポイント>"]
}
重要:
.pr-triage.json の出力に集中してください。Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
pr-triage fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
pr-triage is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend pr-triage for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: pr-triage is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: pr-triage is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: pr-triage is focused, and the summary matches what you get after install.
Keeps context tight: pr-triage is the kind of skill you can hand to a new teammate without a long onboarding doc.
pr-triage has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added pr-triage from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
pr-triage has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 75