dotfiles

Category: Tools & Productivity | Uploader: ikuwow | Downloads: 0 | Version: v1.0（Latest）

Perform a self-review of a PR before requesting human review. TRIGGER when user invokes /pr-selfcheck, when the git workflow reaches the self-review step after PR creation, or as a required gate before running `gh pr ready`. Accepts a PR number as an argument.

Changelog: Source: GitHub https://github.com/ikuwow/dotfiles

Directory Structure

Current level: tree/main/claude/skills/pr-selfcheck/

📄 SKILL.md 1.6 KB

SKILL.md

---
description: Perform a self-review of a PR before requesting human review. TRIGGER when user invokes /pr-selfcheck, when the git workflow reaches the self-review step after PR creation, or as a required gate before running `gh pr ready`. Accepts a PR number as an argument.
model: sonnet
---

# PR Self-Check

Perform a self-review of the specified PR to catch issues before a human reviewer sees it.

## Steps

1. Retrieve PR metadata:
   `gh pr view <number> --json title,body,url,additions,deletions,files`
2. Retrieve the diff:
   `gh pr diff <number>`
3. For each URL found in the PR body, verify accessibility with WebFetch.
   If a URL is unreachable (network error, 403, etc.), report it as "unverifiable" rather than a must-fix.
4. Analyze the PR against the review criteria below.
5. Output the result in the format described below.

## Review Criteria

Evaluate the PR against the Review Criteria defined in `pr-guidelines.md`.

## Output Format

```
## PR Self-Check Result

### Must Fix
- (Critical issues: broken links, title/content mismatch, missing rationale for important changes)

### Should Fix
- (Recommended improvements: missing source URLs, unclear scope description)

### Nice to Have
- (Minor polish: wording, formatting)

### Verdict
PASS | NEEDS_IMPROVEMENT
```

If there are no items for a severity level, write "None."

## Important Notes

- This is a single-pass check. Do not re-run the check after fixes.
- Focus on the PR as a communication artifact for human reviewers, not on code correctness (CI covers that).
- When in doubt, prefer "Should Fix" over "Must Fix" to avoid blocking on subjective issues.

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

dotfiles

Directory Structure

SKILL.md

Report

Notice