Favicon of code-review

code-review Skill

AI Agent SkillPowerShellOpen source

Review code changes from multiple perspectives with context bootstrap, depth-tier rigor, and structured findings output. Published by microsoft in hve-core.

Decision snapshot

Is this a fit?

Best for

Security review, Includes SKILL.md, Reusable instructions

Works with

Compatibility not yet detected.

Access

Permission behavior not yet detected.

Setup

Copy skill directory

Project health

2 months ago · MIT license

Considerations

No specific cautions were detected. Review the source and requested permissions before installing.

What is code-review Skill?

Review code changes from multiple perspectives with context bootstrap, depth-tier rigor, and structured findings output. Published by microsoft in hve-core. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.

Trust signal
95/100
Maintenance signal
90/100
Adoption signal
77/100

Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.

Key capabilities

  • Includes SKILL.md support
  • Reusable instructions support
  • Security review
  • Security review use cases

Declared skill metadata

  • Declared license: MIT
  • Source file: .github/skills/coding-standards/code-review/SKILL.md

These fields retain source and confidence evidence from the indexed SKILL.md.

Compatibility and setup

Copy skill directory
  • Install or run with Copy skill directory

When to use code-review Skill

  • Use it for security review.

Built with

PowerShellCopy skill directory

Editorial notes

Source

  • Creator: microsoft
  • Repository: microsoft/hve-core
  • Skill file: .github/skills/coding-standards/code-review/SKILL.md

What it does

Review code changes from multiple perspectives with context bootstrap, depth-tier rigor, and structured findings output.

Skill instructions

Code Review — Skill Entry This SKILL.md is the entrypoint for the Code Review skill. The skill provides a reusable review workflow for orchestrators and perspective subagents that evaluate code changes across functional, standards, accessibility, PR, security, readiness, and full review perspectives. It centralizes change-brief preparation, review depth selection, severity normalization, and output contract details so that review agents stay thin and consistent. Shared principles Review work should stay anchored in evidence and should avoid premature conclusions. Keep the review grounded in file and line evidence, use proportional depth based on risk, read the full diff range before narrowing, and keep factual orientation separate from structured findings. Normative references 1. Output Formats — reporting structure, merged report skeleton, and persisted artifact contract. 2. Severity Taxonomy — severity levels, verdict normalization, and risk classification. 3. Lens Checklists — persp

Verified compatibility and discovery

Frequently asked questions

What is code-review?

code-review is a open-source AI agent skill with Copy skill directory. Review code changes from multiple perspectives with context bootstrap, depth-tier rigor, and structured findings output.

Who is code-review best for?

code-review is best for reusing agent instructions, scripts, and references, security review workflows.

How do I install code-review?

Install or run code-review using Copy skill directory. Check code-review for the latest setup command.

Is code-review actively maintained?

code-review may need a closer maintenance check before production use.

Share:

Stars
1,263
Forks
229
Last commit
2 months ago
Last verified
Aug 27, 2026
Metadata fetched
Aug 27, 2026
Repository age
10 months
License
MIT

Project health auto-fetched from the source repository.

Maintain this resource?

Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.

Alternatives to code-review