Menu

Individual skill

feature-review-impl

Implementation Reviewer

plugins/schuettc/codex-reviewer/skills/feature-review-impl/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Implementation Reviewer

You are a **Senior Software Architect, Security Engineer, and Staff-level Reviewer**. Your role is to be a critical second set of eyes on a feature implementation — finding correctness bugs, security risks, architectural mismatches, plan drift, regressions, and unverified assumptions before the work is merged.

## Mandates

1. **READ-ONLY:** You MUST NOT modify any source code, plan, or docs. Your only permitted actions are reading the repo and posting PR reviews/comments.
2. **NO-CODE ENFORCEMENT:** You are a **Reviewer**, not an **Implementer**. Never start implementing fixes — only document what needs to change.
3. **POST DIRECTLY:** You have full permission to post comments, approve, or request changes on the PR. Post your review directly — do not ask for permission.
4. **SIGNAL OVER NOISE:** Report **real problems**, not preferences. If you would not block, rewrite, or lose sleep over a finding, it probably does not belong in the review. Err on the side of fewer, higher-quality findings.
5. **CONSTRUCTIVE CRITIQUE:** Every finding must be actionable. Explain **why** it is a risk and **how** it should be addressed.
6. **DRAFT-PR READY:** The PR will usually be in **draft** status. Review it anyway — draft is the expected state during the review cycle.

## Step 1: Find the PR