Code Review
dotnet/maui
Deep code review of PR or materialized candidate-patch changes for correctness, safety, and MAUI conventions.
In-depth code review that fans out parallel subagents across review areas — CRITICAL after non-trivial development.
Install Review Areas
$ npx skills add Azure/azqr --skill review-areas -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Azure/azqr review-areas --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Azure/azqr.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/review-areas .claude/skills/review-areas && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "review-areas" agent skill from https://github.com/Azure/azqr/tree/main/.agents/skills/review-areas into .claude/skills/review-areas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-areas", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Azure/azqr/tree/main/.agents/skills/review-areasType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Azure/azqr --skill review-areas -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Azure/azqr review-areas --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azqr.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/review-areas .agents/skills/review-areas && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "review-areas" agent skill from https://github.com/Azure/azqr/tree/main/.agents/skills/review-areas into .agents/skills/review-areas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-areas", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Azure/azqr --skill review-areas -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Azure/azqr review-areas --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azqr.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/review-areas .cursor/skills/review-areas && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "review-areas" agent skill from https://github.com/Azure/azqr/tree/main/.agents/skills/review-areas into .cursor/skills/review-areas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-areas", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Azure/azqr.git --path .agents/skills/review-areas--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Azure/azqr --skill review-areas -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Azure/azqr review-areas --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azqr.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/review-areas .gemini/skills/review-areas && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "review-areas" agent skill from https://github.com/Azure/azqr/tree/main/.agents/skills/review-areas into .gemini/skills/review-areas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-areas", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Azure/azqr review-areasInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Azure/azqr --skill review-areas -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Azure/azqr.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/review-areas .github/skills/review-areas && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "review-areas" agent skill from https://github.com/Azure/azqr/tree/main/.agents/skills/review-areas into .github/skills/review-areas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-areas", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Azure/azqr --skill review-areas -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Azure/azqr review-areas --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azqr.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/review-areas .opencode/skills/review-areas && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "review-areas" agent skill from https://github.com/Azure/azqr/tree/main/.agents/skills/review-areas into .opencode/skills/review-areas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-areas", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
review-areas- GitHub stars
- 796
- Token cost
- ~1.6k tokens
- SKILL.md length
- 676 words
- Files
- 5
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
In-depth code review that fans out parallel subagents across review areas — CRITICAL after non-trivial development.
- Works in 6 steps: Scope → Build a Change Summary → Fan Out → …
- : in-depth review of a pull request
- SKILL.md covers Review Areas, Workflow, Signal Filter and Area Prompt, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Review Areas is an agent skill from Azure/azqr, published by the product's own GitHub organization. In-depth code review that fans out parallel subagents across review areas — CRITICAL after non-trivial development. USE FOR: "in-depth review of a pull request", "code quality check or bug hunt", "review correctness, tests, security, performance and product areas", "review after any non-trivial development phase". DO NOT USE FOR: "plan a new implementation", "explain how existing code works".
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files (for example `evals/eval.yaml`, `evals/tasks/basic-review.yaml` and `evals/tasks/should-not-trigger.yaml`).
It sits in Development, covering Subagents, Pull requests and Code quality. It works with Microsoft Azure. The licence is MIT.
When your agent uses it
- : in-depth review of a pull request
- Code quality check
- Review correctness
- Performance and product areas
Example prompts
- “in-depth review of a pull request”
- “code quality check or bug hunt”
- “review correctness, tests, security, performance and product areas”
- “/review-areas”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 3ccbd65. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Review Areas loads about 1.6k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 676 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Azure/azqr at commit 3ccbd65, republished under its MIT licence (© Azure). 676 words, ~1,593 tokens.
Download SKILL.mdSave it as
.claude/skills/review-areas/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- review-areas
- description
- In-depth code review that fans out parallel subagents across review areas — CRITICAL after non-trivial development. USE FOR: "in-depth review of a pull request", "code quality check or bug hunt", "review correctness, tests, security, performance and product areas", "review after any non-trivial development phase". DO NOT USE FOR: "plan a new implementation", "explain how existing code works".
Skill: Review Areas
Fan out parallel read-only subagents, each assigned a different review area, then synthesize the highest-signal findings. This surfaces issues that a single-pass review misses because each subagent goes deep on its area instead of skimming everything.
Review Areas
Pick 2–4 areas based on the nature of the change. Not every review needs all areas — match the areas to the risk profile.
| Area | When to include | Focus |
|---|---|---|
| Correctness | Always | Logic errors, type safety, race conditions, null/undefined paths, unsafe casts, wrong behavior |
| Tests | When tests exist or should exist | Run tests, check failing/missing coverage, validate assertions match intent |
| Security | Auth, input handling, data flow changes | Input validation, auth checks, injection, data exposure |
| Performance | Hot paths, data structures, async changes | Algorithm complexity, unnecessary allocations, blocking async patterns |
| Product | UI, UX, or user-facing behavior changes | UX implications, feature completeness, accessibility gaps |
Workflow
1 — Scope
- Prefer the active pull request, current git diff, or an explicit file list from the user.
- If there is nothing to review, ask the user to point at a branch, PR, diff, or file set.
2 — Build a Change Summary
Before fanning out, build a concise change summary. Do not paste raw diffs into the subagent prompts — each subagent has tools to read files and inspect changes itself.
The summary should include:
- Intent — what the change is trying to accomplish (from PR description, commit messages, or conversation context).
- Changed files — list each file path with a one-line description of what changed (e.g., "added input validation", "refactored into helper").
- Risk areas — anything risky: new dependencies, auth changes, hot-path modifications, API surface changes.
- How to inspect — branch/PR/commit info so subagents can use their tools.
Keep the summary under ~50 lines. Subagents get better results reading code in context than scanning a wall of diff.
3 — Fan Out
Launch 2–4 parallel subagents using the area prompts below. Each subagent works in isolation — do not share one area's findings with another before synthesis.
Use unnamed subagents (no custom agent needed). Each gets a self-contained prompt with its area, the change summary, and the return format.
4 — Synthesize
When all subagents return:
- Deduplicate findings that overlap across areas (e.g., a correctness bug that also shows up as a missing test).
- Order by severity: breaking > wrong behavior > security > missing coverage > performance > product.
- Apply the signal filter — drop anything that wouldn't block a PR.
- If no blocking issues survive, say so and mention any meaningful testing gaps.
Show full SKILL.md (265 more words)Show less
5 — Save Findings
Always save the synthesized findings to session memory at /memories/session/review.md. This makes them available for follow-up turns, fix planning, and cross-referencing with future reviews.
6 — Fix or Report
- Review-only: if the user said "only review", "just review", or "read-only", stop after reporting.
- Default (review-and-fix):
- For each fixable finding, launch one or more parallel
Exploresubagents to investigate the fix — this is faster and deeper than reading files inline. Give each Explore agent the finding, the relevant file paths, and ask it to return the specific change needed (what to replace, where). - Apply fixes in severity order based on the Explore agents' recommendations.
- After applying, re-check the changed lines and diagnostics to validate.
- Report what was fixed and any remaining items that need the user's input.
- For each fixable finding, launch one or more parallel
Signal Filter
Keep only findings a senior engineer would block a PR for:
- Will fail to compile, type-check, or produce wrong results
- Clear, citable violation of workspace coding standards
- Security vulnerability with a concrete exploit path
- Missing error handling that causes silent failures
Drop: style preferences, linter-catchable issues, pre-existing problems, speculative concerns.
Area Prompt
Each subagent gets this prompt with {AREA} and {FOCUS} filled in from the Review Areas table.
You are a focused code review subagent. Your area is: {AREA}
## What changed
<change summary from step 2: intent, changed files with one-line descriptions, risk areas>
## How to inspect
<branch, PR number, or commit range the subagent can use with its tools>
Focus on: {FOCUS}
Use your tools to read the changed files, check diagnostics, and run focused tests. Do not rely solely on this summary — dig into the code yourself. Read functions end-to-end. Trace inputs through branches and error paths. Check callers when contracts change.
Rules:
- Stay read-only. Do not edit files.
- Only flag issues that would block a PR — things that break, regress, or expose a concrete vulnerability.
- Do not report issues outside your area.
- Do not suggest code edits — describe the problem and why it matters.
- Check loaded workspace instructions and skills before flagging standard violations.
- Keep your response short. No preamble, no style commentary.
Return format:
**Area**: {AREA}
**Findings** (0–5 items, severity order):
- [file:line] One-sentence description. Why it matters.
If nothing blocks approval: "No blocking issues found in {AREA}."Output Shape
Changes Summary (50 words max): What changed, why, and expected impact.
What's Done Well (1–3 items): Acknowledge good patterns worth reinforcing.
Critical Issues (0–5 items, severity order): Each with file references and the area that surfaced it.
Improvements (0–5 items): High-value suggestions that didn't quite reach "blocking" but are worth addressing.
Verdict: Ready / Needs Revisions / Blocked — with a specific next step.
© Azure, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files in .agents/skills/review-areas of Azure/azqr.
- SKILL.md
- evals/eval.yaml
- evals/tasks/basic-review.yaml
- evals/tasks/should-not-trigger.yaml
- evals/trigger_tests.yaml
Open the folder on GitHubat commit 3ccbd65
Compare with similar skills
Review Areas next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Review Areas this skillAzure/azqr | 796 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Code Reviewdotnet/maui | 23k | — | ~8.2k | Automated safety check: Pass | MIT | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence | |
| GitHub Review Iterationprisma/orm | 48k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review Skillawesome-skills/code-review-skill | 2.1k | — | ~2.8k | Automated safety check: Notes | MIT | |
| Cherry Studio PR ReviewCherryHQ/cherry-studio | 53k | — | ~3.9k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
- Official
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
- Official
GitHub Review Iteration
prisma/orm
Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.
Code Review Skill
awesome-skills/code-review-skill
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C/.NET, Kotlin, Swift, Dart…
Cherry Studio PR Review
CherryHQ/cherry-studio
Reviews Cherry Studio branches, pull requests, commits, files and docs against the project's own architecture, naming, API-boundary and UI rules, report-only by default.
Code Reviewer
jewbetcha/opentrace
Comprehensive code review skill for TypeScript, JavaScript, Python, Swift, Kotlin, Go.
More from Azure/azqr
- Official
Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
- Official
Kql Validator
Azure/azqr
Validate KQL (Kusto Query Language) files used in Azure Quick Review (azqr) against their recommendation definitions.
- Official
Azqr Developer
Azure/azqr
Expert guidance for developing and contributing to Azure Quick Review (azqr) - A Go-based CLI tool for Azure resource compliance analysis
- Official
Code Simplifier
Azure/azqr
Analyzes recently modified code and creates pull requests with simplifications that improve clarity, consistency, and maintainability while preserving functionality
Related
Works with
Categories
Questions about Review Areas
What does Review Areas do?
In-depth code review that fans out parallel subagents across review areas — CRITICAL after non-trivial development. Review Areas is an agent skill from Azure/azqr, published by the product's own GitHub organization. In-depth code review that fans out parallel subagents across review areas — CRITICAL after non-trivial development.
When should I use Review Areas?
Review Areas fits situations like: : in-depth review of a pull request; code quality check; review correctness; performance and product areas.
How do I install Review Areas in Claude Code?
Run `npx skills add Azure/azqr --skill review-areas -a claude-code`. Or copy the skill folder (.agents/skills/review-areas in Azure/azqr) into .claude/skills/review-areas in your project. Claude Code loads it when a task matches its description.
How do I install Review Areas in Codex?
Run `npx skills add Azure/azqr --skill review-areas -a codex`. Or copy the skill folder (.agents/skills/review-areas in Azure/azqr) into .agents/skills/review-areas in your project. Codex loads it when a task matches its description.
Can I use Review Areas in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Azure/azqr --skill review-areas -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-areas, .gemini/skills/review-areas, .github/skills/review-areas and .opencode/skills/review-areas in your project.
What does Review Areas need to run?
SKILL.md names no scripts, command-line tools or credentials: Review Areas is instructions for the agent only.
Does Review Areas access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Review Areas safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Review Areas use?
Review Areas is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Review Areas use?
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Review Areas?
Skills that share tags, products or a category with Review Areas: Code Review (dotnet/maui, 23k stars), WooCommerce Code Review (woocommerce/woocommerce, 11k stars), GitHub Review Iteration (prisma/orm, 48k stars) and Code Review Skill (awesome-skills/code-review-skill, 2.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Review Areas?
Azure (a GitHub organization, an official publisher) maintains it in Azure/azqr, which has 796 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 9, 2026.
Source: Azure/azqr on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.