Favicon of requesting-code-review

requesting-code-review Skill

AI Agent SkillJavaScriptOpen source

Use when completing tasks, implementing major features, or before merging to verify work meets requirements Published by openai in plugins.

Decision snapshot

Is this a fit?

Best for

Developers using plugins, Includes SKILL.md, Reusable instructions

Works with

Compatibility not yet detected.

Access

Permission behavior not yet detected.

Setup

Copy skill directory

Project health

12 days ago

Considerations

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

What is requesting-code-review Skill?

Use when completing tasks, implementing major features, or before merging to verify work meets requirements Published by openai in plugins. 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
93/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
  • Developers using plugins

Declared skill metadata

  • Source file: plugins/superpowers/skills/requesting-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 requesting-code-review Skill

  • Use it for developers using plugins.

Built with

JavaScriptCopy skill directory

Editorial notes

Source

  • Creator: openai
  • Repository: openai/plugins
  • Skill file: plugins/superpowers/skills/requesting-code-review/SKILL.md

What it does

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Skill instructions

Requesting Code Review Dispatch a code reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. Core principle: Review early, review often. When to Request Review Mandatory: - After each task in subagent-driven development - After completing major feature - Before merge to main Optional but valuable: - When stuck (fresh perspective) - Before refactoring (baseline check) - After fixing complex bug How to Request 1. Get git SHAs: bash BASESHA=$(git rev-parse HEAD~1) or origin/main HEADSHA=$(git rev-parse HEAD) 2. Dispatch code reviewer subagent: Dispatch a general-purpose subagent, filling the template at code-reviewer.md Placeholders: - {DESCRIPTION} - Brief summary of what you built - {PLANORREQUIREMENTS} - What it should do - {BASESHA} - Starting commit - {HEADSHA} - Ending commit 3. Act on feedback: - Fix Critical issues immediately - Fix Important issues before proceeding - Note Minor issues for

Verified compatibility and discovery

Frequently asked questions

What is requesting-code-review?

requesting-code-review is a open-source AI agent skill with Copy skill directory. Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Who is requesting-code-review best for?

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

How do I install requesting-code-review?

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

Is requesting-code-review actively maintained?

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

Share:

Stars
5,411
Forks
776
Last commit
12 days ago
Last verified
Sep 6, 2026
Metadata fetched
Sep 6, 2026
Repository age
6 months
License
Unknown

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 requesting-code-review