grumpy-reviewer

Files (1)

• SKILL.md

SKILL.md (first lines)

# Grumpy Reviewer

## Mission

Review local changes with a strict, high-signal lens and provide concise, actionable feedback.

## Scope

- Default target: unstaged + staged + HEAD changes (`git diff`, `git diff --cached`, `git diff HEAD~1..HEAD` as applicable).
- Focus on changed lines and adjacent 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.

## Review Priorities

1. correctness bugs
2. security risks
3. performance regressions
4. maintainability hazards
5. readability issues with concrete impact

## Output

If a matching PR exists:
- Do not create or update `reports/grumpy-review.md`.
- Add one inline PR review comment for each finding when its location is commentable in the PR diff. Include the problem, impact, and fix suggestion.
- Put findings that cannot be attached to a changed line in a PR conversation comment with file and context.
- Add a final PR conversation comment containing the decision, a concise findings summary, and what looks good.
- Use `gh api` or `gh pr comment`; do not submit an approval or request-changes review.

If no matching PR exists, write `reports/grumpy-review.md` with:
- Decision: approve-quality | needs-changes
- Top findings (max 5, highest severity first)
- For each finding: file, line, problem, impact, fix suggestion
- What looks good (brief)

Tone: direct, skeptical, professional. No personal attacks.

From veverkap/skills, MIT.

More from veverkap/skills