A finishing skill for checking a completed software change before it is merged. It reviews the code changes, runs tests and lint checks, checks acceptance requirements, and updates the project's task records.

It is for reviewing finished coding work, recording review results, marking requirements as verified, and identifying outside blockers such as missing access or approval.

It helps catch defects, missing requirements, and incomplete documentation before a change is treated as ready to ship.

ss-review — Skill for Codex by bonnguyenitc

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add bonnguyenitc/specship --skill ss-review

Clone the repo

git clone --depth 1 https://github.com/bonnguyenitc/specship

Made for: Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bonnguyenitc/specship/ss-review/github.svg)](https://agentmods.dev/skills/bonnguyenitc/specship/ss-review)

Your own site

<a href="https://agentmods.dev/skills/bonnguyenitc/specship/ss-review"><img src="https://agentmods.dev/badge/skills/bonnguyenitc/specship/ss-review/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bonnguyenitc/specship/ss-review"><img src="https://agentmods.dev/badge/skills/bonnguyenitc/specship/ss-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,885 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00074	$0.02885
Opus 5	$0.00037	$0.01443
Sonnet 5	$0.00015	$0.00577
Haiku 4.5	$0.00007	$0.00288

Measured 11d ago against content hash 395225e81cdb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

ss-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/ss-review/SKILL.md · 118 lines

How it starts

The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Review

Goal: take a change from "code written" to "ready to ship" — verified correct, clean, and consistent with the spec, before it's committed.

When to use

Implementation is finished (ideally via the ss-coding skill).
You're asked to review, wrap up, finalize, or check if a change is merge-ready.
Final stage of the workflow: spec → plan → coding → review (+ debug).

Shared task state

Part of the task pipeline — see ../WORKFLOW.md for the full contract.

Hydrate: resolve the active TASK-<ID>, read tasks/TASK-<ID>/task.md, spec.md, plan.md, docs/onboarding/how-to-code.md, and the diff.
Checkpoint: write review.md and tick verified AC# in spec.md; update task.md — set review artifact changes-requested/approved, set stage: done + status: done only when approved, bump updated:, append a Pipeline Log line carrying your agent label (format: ../WORKFLOW.md → Agent handoff).
Blocked? If the review can't complete because of an external dependency (a staging env, access, or sign-off it's waiting on), set status: blocked, note it in Blocked by:, and log it; flip back to active when it clears. A blocker defect found in review goes through ss-debug (which sets blocked itself). blocked is involuntary — to set the task aside by choice, use ss-pause-task. See ../WORKFLOW.md → Status values.
Lessons: read tasks/LESSONS.md at hydrate and apply its rules; if you detect a process mistake (in this stage or an earlier one), fix it and append an L# entry there (see ../WORKFLOW.md → Lessons).

Method

0. Load the artifacts

Read the files the earlier stages produced so the review is grounded, not generic:

tasks/TASK-<ID>/spec.md — requirements, acceptance criteria, edge cases.
tasks/TASK-<ID>/plan.md — the intended approach and steps.
docs/onboarding/how-to-code.md + source-structure.md — the code-style and placement rules.

1. Review the diff — independent eyes for bugs, task-grounded eyes for fit

Read the full file on GitHub · 118 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

agents/openai.yaml 299 B

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

11d ago First seen · 118 lines · 74 tokens per session scan A 395225e81cdb

Subscribe to this mod's changes

ss-review is a skill published in the GitHub repository bonnguyenitc/specship (2 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 2,885 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review agent agent-skills agent-workflow claudecode codex coding

bootstrap-repo-analysis

First-time analysis of a repository with no prior reviewer outcomes. Crawl historical merged-PR review feedback with the gh CLI (plus any preloaded samples), extract the team's review norms, and synthesize the initial per-repo review-style prompt. Use this for a cold-start repo; use continual-learning instead once the…

langchain-ai/open-swe · 73 tokens

continual-learning

Nightly refinement of an existing per-repo review-style prompt using this reviewer's own finding outcomes. Read confirmed (resolved-by-commit / thumbs-up) and dismissed (thumbs-down) findings, promote the bug patterns the team actually fixes, demote the false-positive patterns, reconcile against the current prompt…

langchain-ai/open-swe · 89 tokens

secure-code-review

Use this skill when reviewing or writing code that handles user input, authentication, file I/O, network requests, or database queries. Always check for common security vulnerabilities before considering the code complete.

aiming-lab/MetaClaw · 42 tokens

pr-review

Review a GitHub pull request and post one formal review — advance the existing discussion and give precision-first, high-signal feedback. Judgement on the diff, not a build gate — CI validates that it builds, and a targeted probe is allowed as evidence. Use when asked to review a PR or on a cron PR scan.

nearform/lastlight · 69 tokens

coding

Use when five specialized coding agents (linter, perf, refactor, security, test) that enforce quality gates across the development lifecycle. From lint enforcement through performance profiling, refactoring, security auditing, and test coverage. Use when working with coding agents.

oyi77/1ai-skills · 54 tokens

comment-review

A code-comment review tool that checks comments against a project's comment policy. It can also correct comments that do not meet the policy.

openkursar/hello-halo · 64 tokens