bonyuta0204

pr-architecture-review

0
0
# Install this skill:
npx skills add bonyuta0204/agent-skills --skill "pr-architecture-review"

Install specific skill from multi-skill repository

# Description

Review pull requests with emphasis on code formatting/style consistency and architecture adherence (clean/onion/DDD, layering rules). Use when given a PR URL and asked to checkout locally, read repo docs (CLAUDE.md, AGENTS.md, .windsurf/rules, README, architecture docs), compare with similar files, and produce review feedback rather than bug hunting.

# SKILL.md


name: pr-architecture-review
description: Review pull requests with emphasis on code formatting/style consistency and architecture adherence (clean/onion/DDD, layering rules). Use when given a PR URL and asked to checkout locally, read repo docs (CLAUDE.md, AGENTS.md, .windsurf/rules, README, architecture docs), compare with similar files, and produce review feedback rather than bug hunting.


PR Architecture Review

Overview

Perform a local PR checkout, collect repository conventions, inspect diffs and adjacent code, and produce review feedback focused on formatting/style and architecture alignment.

Workflow

  1. Resolve repo and PR
  2. Parse the PR URL (assume GitHub). Identify owner/repo and PR number.
  3. Ensure you are in the local repo. If it is missing, ask the user for the local path or permission to clone.
  4. Prefer scripts/checkout_pr.sh <pr-url> [remote] or gh pr checkout <number> when available.
  5. Fallback: git fetch origin pull/<number>/head:pr-<number> then git checkout pr-<number>.

  6. Gather conventions

  7. Read CLAUDE.md, AGENTS.md, .windsurf/rules/* or .windsurfrules (if present), README, and docs/architecture or ADRs if present.
  8. Extract: architecture style, layer boundaries, file placement rules, naming conventions, formatting/linters, review comment language.

  9. Inspect changes

  10. Use git status -sb, git diff --stat, and git diff <base>...HEAD or gh pr diff.
  11. For each changed file, open the file and 1-2 similar files in the same feature or directory to compare patterns.
  12. Validate: file placement, dependency direction, layer boundaries, naming, public API shape, formatting/lint alignment.
  13. Do not run heavy tests unless the user asks.

  14. Produce review

  15. Use the checklist in references/review-checklist.md.
  16. Prioritize architecture or convention violations first, then style/formatting issues.
  17. Include file:line references and concise, actionable guidance.
  18. If no issues, say so and list what was checked.
  19. Ask before posting comments to a PR.

Resources

  • scripts/checkout_pr.sh for PR checkout.
  • references/review-checklist.md for the review template and checklist.

# Supported AI Coding Agents

This skill is compatible with the SKILL.md standard and works with all major AI coding agents:

Learn more about the SKILL.md standard and how to use these skills with your preferred AI coding agent.