PR screening review before human review. Use when: スクリーニングレビュー, PRレビュー支援, レビュー前チェック, PR screening, pre-review.
From shipnpx claudepluginhub thkt/dotclaude --plugin toolkitThis skill is limited to using the following tools:
references/review-checklist.mdProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Calculates TAM/SAM/SOM using top-down, bottom-up, and value theory methodologies for market sizing, revenue estimation, and startup validation.
| Step | Action | Purpose |
|---|---|---|
| 1 | Gather PR context | Background and intent |
| 2 | Summarize changes per file | Before/after understanding |
| 3 | Check dependency impact | Regression risk |
| 4 | Produce findings + comments | Reviewer-ready output |
# Metadata
gh pr view --json title,body,labels,files,url $PR
# Diff
gh pr diff $PR
# Existing comments
gh pr view --comments $PR
# Inline comments
gh api repos/{owner}/{repo}/pulls/{number}/comments \
--jq '.[] | {file: .path, user: .user.login, comment: .body}'
Never include author in gh output fields.
| Label | Meaning | Severity |
|---|---|---|
[must] | Requires fix before merge | High |
[want] | Should fix, not blocking | Medium |
[imo] | Personal opinion, take or leave | Low |
[ask] | Question needing clarification | - |
[nits] | Minor style/formatting issue | Low |
[info] | Context sharing, no action | - |
| Rule | Detail |
|---|---|
| Respectful | Acknowledge effort, avoid commands |
| Concise | 3 lines max per comment |
| Suggestive | "Consider..." not "This is wrong" |
| Located | Specify file:line for each comment |
| Topic | File |
|---|---|
| Review Checklist | ${CLAUDE_SKILL_DIR}/references/review-checklist.md |