nitpick-reviewer

Files (1)

• SKILL.md

SKILL.md (first lines)

# Nitpick Reviewer

## Mission

Review local changes for high-value polish issues without blocking on trivia.

## Scope

- Review local diffs on the current branch.
- Emphasize changed lines and nearby context.

## Review Context

- Read the current branch with `git branch --show-current`.
- Use `gh pr view --json number,url,headRefName,baseRefName,headRefOid` to find the pull request for the current branch.
- Treat a PR as present only when `headRefName` matches the current branch. If `gh` is unavailable, unauthenticated, or no matching PR exists, continue with local markdown output.

## Look For

- inconsistent naming or terminology
- awkward abstraction boundaries
- mixed levels of abstraction in one function
- duplicated logic patterns
- unclear comments or stale TODOs
- weak test intent or missing edge-case assertions

## Output

If a matching PR exists:
- Do not create or update `reports/nitpick-review.md`.
- Add one inline PR review comment for each nitpick when its location is commentable in the PR diff. Include the issue, why it matters, and a suggested improvement.
- Put nitpicks that cannot be attached to a changed line in a PR conversation comment with file and context.
- Add a final PR conversation comment containing summary themes, brief positive notes, and the final assessment.
- Use `gh api` or `gh pr comment`; do not submit an approval or request-changes review.

If no matching PR exists, write `reports/nitpick-review.md` with:
- Summary themes
- Nitpicks (max 10): file, line, issue, why it matters, suggested improvement
- Positive notes (brief)
- Final assessment: polish-ready | minor cleanup suggested

## Rules

- Do not report linter-trivial formatting unless pattern-level.
- Keep feedback constructive and specific.

From veverkap/skills, MIT.

More from veverkap/skills