From ship
Performs a preliminary AI screening review of pull requests before human review. Detects issues, risks, and dependency impacts with structured comments.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ship:preview [PR URL or number]When to use
スクリーニング, PRレビュー, プレビュー, preview PR, pre-review
[PR URL or number]opusThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- PR reference: `$ARGUMENTS` (URL, number, or empty → detect from current branch)
$ARGUMENTS (URL, number, or empty → detect from current branch)| Step | Action |
|---|---|
| 1 | Identify PR: gh pr view $ARGUMENTS --json number,title,body,labels,files,url (fallback: omit $ARGUMENTS) |
| 2 | Abort if no PR found or working tree is dirty (git status --porcelain) |
| 3 | Checkout PR: gh pr checkout $PR |
| 4 | Gather PR context in parallel (see below) |
| 5 | Read each changed file in full, including code outside the diff hunks |
| 6 | Review per process: overview → per-file → dependency impact → findings |
| 7 | Output structured screening report |
# 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 |
|---|---|
| Format | [label] <observed behavior or risk>. <suggestion>. (file:line) |
| Concise | 3 lines for [imo]/[nits]/[info]; up to 5 for [must]/[want] with evidence |
| Respectful | Acknowledge effort, avoid commands |
| Suggestive | "Consider..." not "This is wrong" |
| Author-targeted | Comments may be posted verbatim - calibrate detail for the PR author |
## PR Screening Report
### Overview
{Background and purpose in 2-3 sentences}
### Changes Summary
| File | Change Summary |
| ---- | -------------- |
### Dependency Impact
{Affected files, regression risk}
---
### Requires Action
{`[must]` and `[want]` findings with file:line}
### Awareness
{`[imo]`, `[ask]`, `[nits]`, `[info]` items with file:line}
---
### Proposed Review Comments
{Grouped by file, with labels}
| Rule | Detail |
|---|---|
| No auto-post | Never post comments to PR automatically |
| Abort on dirty | If uncommitted changes exist, warn and abort |
| Speed over depth | This is screening, not full audit |
| Verify before flag | Before [ask]/[want]+, trace the issue to a reachable runtime call site |
| Topic | File |
|---|---|
| Review Checklist | ${CLAUDE_SKILL_DIR}/references/review-checklist.md |
npx claudepluginhub thkt/dotclaude --plugin toolkitProvides 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.