Goblin-mode review-pr

{{ ๐›€๐›€๐›€ }} Review a pull request and post a comment

install
source ยท Clone the upstream repo
git clone https://github.com/JasonWarrenUK/goblin-mode
Claude Code ยท Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/JasonWarrenUK/goblin-mode "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/review-pr" ~/.claude/skills/jasonwarrenuk-goblin-mode-review-pr && rm -rf "$T"
manifest: skills/review-pr/SKILL.md
source content
<pull-request-review> <task>Review the pull request identified by `$ARGUMENTS`.</task> <steps> <step num="1">Run `gh pr view $ARGUMENTS` to get PR title, description, and metadata</step> <step num="2">Run `gh pr diff $ARGUMENTS` to get the full diff</step> <step num="3">Research project conventions stored in `CLAUDE.md`, `.claude/**/*` and `docs/*`</step> <step num="4">Write a review comment using the `<format>` below</step> <step num="5">Post it with `gh pr comment $ARGUMENTS --body "..."`</step> </steps> <foci> <focus>Correctness โ€” will this break anything?</focus> <focus>Security โ€” any obvious vulnerabilities?</focus> <focus>Glaring convention violations</focus> <foci> <guidance> <guide>Keep it concise.</guide> <guide>Flag only the most important issues. Skip minor style nits.</guide> <guide>Before critiquing implementation, check whether the dev is following established project practice</guide> </guidance> <format type="md"> # Code Review ## What Works Well <details> <summary><strong>๐ŸŸฃ [strength]</strong></summary>
[Why it's good.]

</details>
## Issues
<details>
<summary><strong>๐Ÿ”ด [Blocking issue title]</strong></summary>

[Description. Code snippet if needed.]

</details>
<details>
<summary><strong>๐ŸŸก [Concern title]</strong></summary>

[Description.]

</details>
<details>
<summary><strong>๐Ÿ”ต [Minor quibble title]</strong></summary>

[Description.]

</details>
</format> <key type="list"> <guide>Omit any severity level that has no entries. Only include ๐ŸŸฃ sections if there's something genuinely worth praising.</guide> <key-item>๐ŸŸฃ Purple: point of excellence โ€” worth calling out</key-item> <key-item>๐Ÿ”ด Red: blocking โ€” must fix before merge</key-item> <key-item>๐ŸŸก Yellow: concern โ€” should fix, won't block</key-item> <key-item>๐Ÿ”ต Blue: minor quibble โ€” nice to have</key-item> </key> </pull-request-review>