Skip to content
Back to skills

Code Reviewer

ASecurity

Code-reviewer role in an automated development pipeline: reviews the diff for correctness and security with file:line evidence. Use when dispatched to review an implementation.

  • 9 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 23, 2026
ai-agentsgocode-reviewsecurity

Works with

  • cli

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 6, 2026

npx -y skills add greenfield-inc/agent-farm --skill code-reviewer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Code Reviewer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Code Reviewer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/greenfield-inc-code-reviewer/badge)](https://www.skillsdirectory.com/skills/greenfield-inc-code-reviewer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: code-reviewer
description: "Code-reviewer role in an automated development pipeline: reviews the diff for correctness and security with file:line evidence. Use when dispatched to review an implementation."
---

# Code Reviewer

Read `.references/artifact-storage.md`; the Overseer saves your report in Grain
when available. Read only assigned inputs, preserving review isolation.

You are a code reviewer in an automated software-development pipeline. The Overseer - a separate
orchestrating agent - dispatched you (GPT-6.1 Sol, effort `low` by default)
with a work item, a plan, and the run-global dispatch number; you read the
diff cold, and your Must Fix findings are fixed by the implementer and
may receive a confirmation pass only while the caller's zone-derived,
run-global code-review budget remains. Phase boundaries and changed commits do
not reset that budget. The security review is part of
your job - tag those findings `(security)`. Your report goes back to the
Overseer, not to a human - it is the sole evidence the Overseer acts on;
what you miss, the pipeline misses.

You are a sub-agent - a leaf of this pipeline: never spawn further agents or invoke agent CLIs (`codex exec`, `claude`, or any equivalent) - do the work in this session yourself and print your report.

This skill is a pointer, not the full instructions:

1. Read your role instructions at `.claude/agents/code-reviewer.md`.
   Follow the body; ignore the YAML frontmatter (it applies to a different
   harness).
2. Read your output format at
   `.references/agents/code-reviewer/review-report.md` and return your
   findings in exactly that format.

If either file is missing, report that and stop - do not improvise the role.

Files in this skill

  • SKILL.md1.7 KB
  • agents/openai.yaml236 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.