request-code-review

request-code-review is a skill for Claude Code, Codex from CodeInfinity1/Stram. It costs 28 tokens per session (397 once invoked), scanned A, original, MIT.

A review handoff guide for packaging a code change so another person or coding agent can assess it.

In plain words
What is it for?
Use it before requesting a code review or creating a pull request to summarize the scope, tests, risks, assumptions, and focused questions.
Why use it?
It prevents reviewers from having to reconstruct the change, its evidence, risks, and open questions themselves.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Codex.

Good fit Use it before requesting a code review or creating a pull request to summarize the scope, tests, risks, assumptions, and focused questions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/codeinfinity1/stram/request-code-review
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 CodeInfinity1/Stram --skill request-code-review
Clone the repo
git clone --depth 1 https://github.com/CodeInfinity1/Stram

Made for: Claude Code, 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.

agentmods badge for request-code-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/codeinfinity1/stram/request-code-review/github.svg)](https://agentmods.dev/skills/codeinfinity1/stram/request-code-review)
Your own site
<a href="https://agentmods.dev/skills/codeinfinity1/stram/request-code-review"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/request-code-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.

agentmods 80×15 button for request-code-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/codeinfinity1/stram/request-code-review"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/request-code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 397 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00397
Opus 5.5 $0.00011 $0.00159
Sonnet 5.5 $0.00006 $0.00079
Haiku 4.5 $0.00003 $0.00040

Measured 1mo ago against content hash 6c3234023fdd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

request-code-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 1mo 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/software-engineering/request-code-review/SKILL.md · 67 lines

What it actually says

Request Code Review

Purpose

Help the user ask for a useful review. This skill packages a change so reviewers can understand intent, risk, verification, and open questions quickly.

When To Use

Use before PR creation, before asking another agent/human to review, or when preparing a review handoff.

Inputs And Evidence

  • Changed files, commit/diff, test output, design intent, and unresolved questions.
  • Risk areas, approvals, and known limitations.

Tool Map

  • run_shell_command
  • read_file
  • diff_render
  • write_note
  • codex_cli_plan
  • codex_cli_run

Workflow

  1. Inspect diff/status and identify the actual scope.
  2. Summarize what changed and why.
  3. List verification commands and results.
  4. Call out risks, assumptions, and known gaps.
  5. Ask focused reviewer questions.
  6. If delegating review, use Codex delegation only after approval and verify the result.

Native Implementation Boundaries

  • Use native Git/shell, file, diff, and Codex tools.
  • Do not import external reference requesting-code-review scripts.
  • Do not fabricate test results.

Safety And Approval

  • Do not push/open PR unless the user asks.
  • Do not include secrets or unrelated local details in review notes.
  • Preserve dirty worktree boundaries.

Verification

  • Review request should match current diff.
  • Test claims must match command output.
  • Delegated review findings should be verified before action.

Failure Modes

  • Asking reviewers to inspect too broad a scope.
  • Hiding known risks.
  • Summarizing stale changes after additional edits.

References

  • Shortlist item: request-code-review.
  • Related skill: code-review.
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.

  1. 1mo ago First seen · 67 lines · 28 tokens per session scan A 6c3234023fdd

Subscribe to this mod's changes

request-code-review is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 397 once invoked, about $0.0001 per session on Opus 5.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-09-03.

Related

Other skills, from other repositories

omh-verification-gate

This is an OMH verification-gate workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 79 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

omh-refactor-plan

This is an OMH refactor-plan workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 100 tokens

codex-adversarial-review

Use this skill to conduct aggressive, adversarial code reviews on git changes, branches, or PRs to detect critical edge cases, race conditions, security holes, and data loss risks. Triggers: user mentions "adversarial review", "break the code", "find vulnerabilities", "security audit PR", "race condition check", "ship…

WrongStack/WrongStack · 83 tokens

generic-fullstack-code-reviewer

Review full-stack code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md compliance. Enforces TypeScript strict mode, input validation, GPU-accelerated animations, and design system consistency. Use when completing features, before commits, or reviewing pull requests.

travisjneuman/.claude · 64 tokens

pr-review

Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…

nitinjain999/platform-skills · 81 tokens