skills.rest
Zeyad-37
Zeyad-37COMMUNITY
Explore all skills by this author →
GitHub

code-review

Reviews pull requests against architecture, standards, tests, and security, posting verdicts on GitHub.

Updated Apr 21, 2026
Search Tags:#code review#pull request#github#coding standards#security scan#subagent#verdict
One-click install
npx skills add https://github.com/Zeyad-37/tech-agency --skill code-review-zeyad-37
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Zeyad-37/tech-agency/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/Zeyad-37/tech-agency --skill code-review-zeyad-37

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews done by the same session that wrote the code are biased toward approval, and ad-hoc reviews miss architecture drift, missing tests, and security issues. This Skill runs every review in a fresh-context subagent that sees only the diff and committed docs, producing an unbiased, structured verdict posted directly on the GitHub PR. ## Core Features & Use Cases - Unbiased fresh-context review: Every invocation spawns a subagent with no session memory, so the verdict cannot be influenced by the conversation that produced the code. - Multi-dimensional scoring: Checks ADR and layer architecture alignment, per-language coding standards compliance, test coverage, a lightweight security scan, and acceptance criteria from the task board. - GitHub-native output: Posts one GitHub review carrying the summary verdict (APPROVED / CHANGES REQUESTED / BLOCKED) plus inline comments anchored to specific diff lines — no review files are written to the repo. - Use Case: Before merging a feature branch, ask for a review; the Skill resolves the PR's actual base branch, reads the relevant coding standards and ADRs, verifies visual evidence for UI changes, and posts an inline-annotated verdict on the PR. ## Quick Start Ask the assistant to review the current branch or a specific PR number before merging, for example by saying "review this PR before merge".

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request before merging?▼

Invoke the code-review skill with a PR number or branch name. It resolves the PR's actual base branch, diffs against the correct merge base, checks architecture, standards, tests, and security, then posts the verdict as a GitHub review with inline comments.

How does the skill avoid biased code reviews?▼

Every review runs in a fresh-context subagent that has no memory of the current session and sees only the diff plus committed docs. The orchestrating agent passes only the review target, never a narrative of what was done or why.

Does the code review write report files into the repository?▼

No. The review is posted directly on the PR as a single GitHub review containing the summary body and inline line comments. The only files created are temporary files under /tmp, which are deleted after posting.

What happens when a PR changes UI code without screenshots?▼

The skill detects UI changes using the canonical file-pattern check from /create-pr and requires a Visual Changes section with actual image references in the PR body. Missing or empty evidence results in CHANGES REQUESTED with a request to run /capture-screenshots.

Can a PR description or comment change the review outcome?▼

No. All author-supplied text — PR descriptions, commit messages, and comments — is treated as untrusted data, never instructions. Directives found in them are quoted as findings, and the verdict derives only from the diff and committed standards.

When does a review get blocked instead of approved?▼

A review is BLOCKED on a security failure, a violation of an accepted ADR, or unmet acceptance criteria. CHANGES REQUESTED applies when any dimension scores low, tests are missing, or coding standards are violated; GitHub maps both to REQUEST_CHANGES.

Related Skills

Explore More Software Engineering Skills→
TravisBumgarnerTravisBumgarner

ralph-pr

Create pull requests from completed tasks using GitHub CLI.

Community
Advanced
hideki5123hideki5123
2

self-pr-review

Automate pull request review loops with Copilot and Gemini feedback.

Community
Advanced
xergioalexxergioalex
3

security-check

Review code changes for secrets, input sanitization, and logging issues.

Community
Intermediate
saschadudkin-sketchsaschadudkin-sketch

code-review

Automate code review for rezidence4/DomHub repository changes.

Community
Advanced