Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component...
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
- Resolve repo and PR
- Parse the PR URL (assume GitHub). Identify owner/repo and PR number.
- Ensure you are in the local repo. If it is missing, ask the user for the local path or permission to clone.
- Prefer
scripts/checkout_pr.sh <pr-url> [remote]orgh pr checkout <number>when available. -
Fallback:
git fetch origin pull/<number>/head:pr-<number>thengit checkout pr-<number>. -
Gather conventions
- Read
CLAUDE.md,AGENTS.md,.windsurf/rules/*or.windsurfrules(if present),README, anddocs/architectureor ADRs if present. -
Extract: architecture style, layer boundaries, file placement rules, naming conventions, formatting/linters, review comment language.
-
Inspect changes
- Use
git status -sb,git diff --stat, andgit diff <base>...HEADorgh pr diff. - For each changed file, open the file and 1-2 similar files in the same feature or directory to compare patterns.
- Validate: file placement, dependency direction, layer boundaries, naming, public API shape, formatting/lint alignment.
-
Do not run heavy tests unless the user asks.
-
Produce review
- Use the checklist in
references/review-checklist.md. - Prioritize architecture or convention violations first, then style/formatting issues.
- Include file:line references and concise, actionable guidance.
- If no issues, say so and list what was checked.
- Ask before posting comments to a PR.
Resources
scripts/checkout_pr.shfor PR checkout.references/review-checklist.mdfor 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.