{"manifest":{"name":"PR Review Assistant","version":"1.0.0","description":"Generates PR descriptions from branch diffs and performs structured code review with must-fix/suggestion/question/praise categories.","tags":["git","pr","code-review","workflow"],"standard":"agentskills.io","standard_version":"1.0","content_checksum":"1c952839abaff4d30625fbd1795c121a8621bd04a436348c5006f01d80ad9df6","bundle_checksum":null,"metadata":{},"files":[]},"files":{"SKILL.md":"# PR Review Assistant\n\n> **Purpose:** Generate a comprehensive pull request description and perform automated review when creating or reviewing PRs.\n\n---\n\n## Invocation\n\n```\n/pr-review [pr_number] # Review existing PR\n/pr-create # Generate PR description for current branch\n```\n\n---\n\n## PR Description Generation\n\n### Step 1: Analyze the Branch\n\n```bash\ngit log main..HEAD --oneline # All commits\ngit diff main...HEAD --stat # Files changed\ngit diff main...HEAD # Full diff\n```\n\n### Step 2: Generate Description\n\n```markdown\n## Summary\n[2-3 bullet points explaining WHY these changes were made]\n\n## Changes\n- [Grouped by area: API, UI, Database, Config, Tests]\n\n## Testing\n- [ ] Unit tests added/updated\n- [ ] Manual testing completed\n- [ ] Edge cases verified\n\n## Screenshots\n[If UI changes, describe what changed visually]\n```\n\n---\n\n## Review Checklist\n\nWhen reviewing a PR, check:\n\n### Architecture\n- [ ] Changes follow existing patterns in the codebase\n- [ ] No unnecessary abstractions or premature optimization\n- [ ] Module boundaries respected (no circular dependencies)\n- [ ] Database queries use proper indexes\n\n### Safety\n- [ ] No secrets or credentials in code\n- [ ] User input is validated at boundaries\n- [ ] Error handling doesn't leak internal details\n- [ ] Auth checks present on new endpoints\n\n### Quality\n- [ ] Tests cover the happy path and key edge cases\n- [ ] No console.log / print debugging left in\n- [ ] Naming is clear and consistent\n- [ ] Comments explain WHY, not WHAT\n\n### Operations\n- [ ] Database migrations are reversible\n- [ ] No breaking API changes without version bump\n- [ ] Feature flags for risky changes\n- [ ] Monitoring/logging added for new failure modes\n\n---\n\n## Review Comment Format\n\n```\n**[MUST FIX]** src/api/route.ts:42\nMissing auth middleware on this endpoint. Any unauthenticated user can access user data.\n\n**[SUGGESTION]** src/utils/format.ts:15\nConsider using Intl.NumberFormat instead of manual formatting — handles locale differences.\n\n**[QUESTION]** src/hooks/useData.ts:28\nWhy was the cache timeout changed from 5min to 30min? Could this cause stale data issues?\n\n**[PRAISE]** src/lib/validation.ts:50\nNice use of discriminated unions here — makes the error handling much cleaner.\n```\n\n---\n\n## Rules\n\n- Always read the full diff before commenting\n- One MUST FIX blocks the PR; everything else is advisory\n- Praise good code — reviews shouldn't be only negative\n- If unsure about a pattern, ask with QUESTION rather than demanding a change\n\n## Playground\n\n

Input: Git diff snippet

@@ -12,6 +12,8 @@ export async\n   function getUser(id: string) {\n-  const user = await db.query(\n-    `SELECT * FROM users WHERE id='${id}'`)\n+  const user = await db.query(\n+    'SELECT * FROM users WHERE id=$1',\n+    [id])\n   return user

Output: Review Comment

✅ Good catch — SQL injection fix\n\nThe old query interpolated `id` directly\ninto the SQL string. Parameterised\nquery with `$1` is correct.\n\n💡 Suggestion\nAlso add `LIMIT 1` — the query returns\nan array; a future schema change could\nreturn multiple rows silently.\n\n💡 Type guard\nValidate that `id` is a UUID before\nhitting the DB to fail fast.

"}}