Agent skill

Requesting Code Review

Structured code review workflow for SRTD development. An agent skill from t1mmen/srtd.

MITAuto-check passedDevelopment

Install Requesting Code Review

skills CLI

$ npx skills add t1mmen/srtd --skill requesting-code-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install t1mmen/srtd requesting-code-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/t1mmen/srtd.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/requesting-code-review .claude/skills/requesting-code-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "requesting-code-review" agent skill from https://github.com/t1mmen/srtd/tree/main/.claude/skills/requesting-code-review into .claude/skills/requesting-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requesting-code-review", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/t1mmen/srtd/tree/main/.claude/skills/requesting-code-review

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add t1mmen/srtd --skill requesting-code-review -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install t1mmen/srtd requesting-code-review --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/t1mmen/srtd.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/requesting-code-review .agents/skills/requesting-code-review && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "requesting-code-review" agent skill from https://github.com/t1mmen/srtd/tree/main/.claude/skills/requesting-code-review into .agents/skills/requesting-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requesting-code-review", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add t1mmen/srtd --skill requesting-code-review -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install t1mmen/srtd requesting-code-review --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/t1mmen/srtd.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/requesting-code-review .cursor/skills/requesting-code-review && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "requesting-code-review" agent skill from https://github.com/t1mmen/srtd/tree/main/.claude/skills/requesting-code-review into .cursor/skills/requesting-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requesting-code-review", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/t1mmen/srtd.git --path .claude/skills/requesting-code-review

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add t1mmen/srtd --skill requesting-code-review -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install t1mmen/srtd requesting-code-review --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/t1mmen/srtd.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/requesting-code-review .gemini/skills/requesting-code-review && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "requesting-code-review" agent skill from https://github.com/t1mmen/srtd/tree/main/.claude/skills/requesting-code-review into .gemini/skills/requesting-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requesting-code-review", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install t1mmen/srtd requesting-code-review

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add t1mmen/srtd --skill requesting-code-review -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/t1mmen/srtd.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/requesting-code-review .github/skills/requesting-code-review && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "requesting-code-review" agent skill from https://github.com/t1mmen/srtd/tree/main/.claude/skills/requesting-code-review into .github/skills/requesting-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requesting-code-review", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add t1mmen/srtd --skill requesting-code-review -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install t1mmen/srtd requesting-code-review --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/t1mmen/srtd.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/requesting-code-review .opencode/skills/requesting-code-review && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "requesting-code-review" agent skill from https://github.com/t1mmen/srtd/tree/main/.claude/skills/requesting-code-review into .opencode/skills/requesting-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requesting-code-review", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: requesting-code-review
GitHub stars: 105
Token cost: ~807 tokens
SKILL.md length: 342 words
Files: 2
Skills in repo: 3
Repo updated: Sep 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Structured code review workflow for SRTD development. An agent skill from t1mmen/srtd.

Works in 3 steps: Identify the Change Range → Dispatch the Code Reviewer → Address Feedback by Severity
Tasks that involve Code review
SKILL.md covers When to Request Review, How to Request Review, Responding to Feedback and SRTD-Specific Review Focus, plus 2 more sections
Calls git

What it does

Requesting Code Review is an agent skill from t1mmen/srtd. Structured code review workflow for SRTD development. Use after implementing features, fixing bugs, or before merging to main. Ensures production-readiness through systematic review.

Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `code-reviewer.md`).

It sits in Development, covering Code review and Literature review. It works with Supabase, PostgreSQL and SQL. The repository describes itself as: 🪄 Supabase migrations made magical: Live-reloading SQL + Sane, reviewable diffs + Maintainable templates = Delightful DX. The licence is MIT.

When your agent uses it

Tasks that involve Code review
Tasks that involve Literature review

Example prompts

“/requesting-code-review”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Identify the Change Range
Dispatch the Code Reviewer
Address Feedback by Severity

What it can do on your machine

Read from SKILL.md and the folder at commit 271b138. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Requesting Code Review loads about 807 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 342 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~51
When it runs · the whole SKILL.md, loaded when a task matches: ~807

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from t1mmen/srtd at commit 271b138, republished under its MIT licence (© t1mmen). 342 words, ~807 tokens.

Download SKILL.mdSave it as .claude/skills/requesting-code-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: requesting-code-review
description: Structured code review workflow for SRTD development. Use after implementing features, fixing bugs, or before merging to main. Ensures production-readiness through systematic review.

Requesting Code Review

Review early, review often. Catch issues before they compound across multiple changes.

When to Request Review

Mandatory

After completing a feature or bug fix
Before merging to main
After significant refactoring
When security-sensitive code is modified

Optional (But Recommended)

When stuck on a design decision
After complex debugging sessions
Before deleting or deprecating code

How to Request Review

Step 1: Identify the Change Range

bash

# Get the commits to review
git log --oneline main..HEAD

# Or specific commit range
BASE_SHA=$(git merge-base main HEAD)
HEAD_SHA=$(git rev-parse HEAD)

Step 2: Dispatch the Code Reviewer

Use the code-reviewer reference to conduct the review:

Review the changes from ${BASE_SHA} to ${HEAD_SHA}.

What was implemented: [brief description]
Requirements: [link to issue or spec]

See: .claude/skills/requesting-code-review/code-reviewer.md

Step 3: Address Feedback by Severity

Severity	Action Required
Critical	STOP. Fix immediately before any other work.
Important	Fix before merging or proceeding to next task.
Minor	Note for later. Can merge with these outstanding.

Responding to Feedback

When You Agree

Fix the issue, then request re-review of the fix.

When You Disagree

You may push back IF you have:

Technical justification (not just preference)
Evidence (code, tests, benchmarks)
Clear explanation of trade-offs

Example: "I kept the nested structure because flattening would require N+1 queries. See benchmark in test/perf/nested-vs-flat.ts showing 3x slowdown."

SRTD-Specific Review Focus

When reviewing SRTD code, pay extra attention to:

Service Boundaries

Is state mutation only in StateService?
Is file I/O only in FileSystemService?
Is database access only in DatabaseService?

State Machine Integrity

Are template states transitioning correctly? (UNSEEN → CHANGED → APPLIED/BUILT → SYNCED)
Is hash comparison working correctly?

Build Log Handling

Are both .buildlog.json and .buildlog.local.json updated appropriately?
Is the distinction maintained? (built vs applied)

Error Handling

Are database errors properly categorized?
Is retry logic correct (3 attempts, exponential backoff)?
Are advisory locks used for concurrent access?

Anti-Patterns (Red Flags)

"This change is too simple to review" → Simple changes break production
"I'll fix that in a follow-up" for Critical/Important issues → Fix now
Ignoring review feedback without justification → Explain or fix
Reviewing your own code without fresh eyes → Request external review

Integration with Development Flow

After Each Task

Request review before marking task complete.

Before PR Creation

Run full review to catch issues before they're public.

After CI Feedback

Re-review if CI reveals issues not caught initially.

Files

SKILL.md and 1 other file in .claude/skills/requesting-code-review of t1mmen/srtd.

SKILL.md
code-reviewer.md

Open the folder on GitHubat commit 271b138

Compare with similar skills

Requesting Code Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Requesting Code Review compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Requesting Code Review this skillt1mmen/srtd	105	—	~807	Automated safety check: Pass	MIT	1 mo ago
PR Bot Reviewspgplex/pgconsole	155	—	~2.1k	Automated safety check: Pass	Apache-2.0	1 mo ago
New Lintsupabase/splinter	280	—	~2.9k	Automated safety check: Notes	None	8 days ago
Mz PR ReviewMaterializeInc/materialize	6.4k	—	~1.6k	Automated safety check: Notes	Custom licence	today
SQL Code Reviewtotvs/engpro-advpl-tlpp-skills	141	—	~3.5k	Automated safety check: Pass	MIT	2 days ago
SQL Code Reviewgithub/awesome-copilot	40k	1 repos	~2.2k	Automated safety check: Pass	MIT	today

Similar skills

PR Bot Reviews
pgplex/pgconsole
Triage, verdict, and reply to automated PR review comments from GitHub Copilot and Greptile, then iterate until the bots have nothing left to say.
155 GitHub stars~2.1k tokensUpdated 1 mo ago
DevelopmentAuto-check passed
New Lint
supabase/splinter
Official
Create a new splinter lint — a SQL view that checks for a database anti-pattern.
280 GitHub stars~2.9k tokensUpdated 8 days ago
DevelopmentAuto-check: notes
Mz PR Review
MaterializeInc/materialize
Local code review of current branch vs Materialize standards.
6.4k GitHub stars~1.6k tokensUpdated today
DevelopmentAuto-check: notes
SQL Code Review
totvs/engpro-advpl-tlpp-skills
Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across SQL databases (PostgreSQL, SQL Server, Oracle).
141 GitHub stars~3.5k tokensUpdated 2 days ago
DatabasesAuto-check passed
SQL Code Review
github/awesome-copilot
Official
Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle).
40k GitHub starsUsed in 1 repo~2.2k tokens
DatabasesAuto-check passed
Nubase
OtterMind/Nubase
A skill your agent uses when the user mentions Nubase broadly, wants a backend for an AI-generated app, or needs to deploy/publish generated code online — across Database, Auth, Storage, Assets…
624 GitHub stars~2.2k tokensUpdated 9 days ago
Backend & APIsAuto-check: notes

Questions about Requesting Code Review

What does Requesting Code Review do?

Structured code review workflow for SRTD development. An agent skill from t1mmen/srtd. Requesting Code Review is an agent skill from t1mmen/srtd. Structured code review workflow for SRTD development.

When should I use Requesting Code Review?

Requesting Code Review fits situations like: tasks that involve Code review; tasks that involve Literature review.

How do I install Requesting Code Review in Claude Code?

Run `npx skills add t1mmen/srtd --skill requesting-code-review -a claude-code`. Or copy the skill folder (.claude/skills/requesting-code-review in t1mmen/srtd) into .claude/skills/requesting-code-review in your project. Claude Code loads it when a task matches its description.

How do I install Requesting Code Review in Codex?

Run `npx skills add t1mmen/srtd --skill requesting-code-review -a codex`. Or copy the skill folder (.claude/skills/requesting-code-review in t1mmen/srtd) into .agents/skills/requesting-code-review in your project. Codex loads it when a task matches its description.

Can I use Requesting Code Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add t1mmen/srtd --skill requesting-code-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/requesting-code-review, .gemini/skills/requesting-code-review, .github/skills/requesting-code-review and .opencode/skills/requesting-code-review in your project.

What does Requesting Code Review need to run?

Going by SKILL.md and its folder, Requesting Code Review needs the command-line tools its instructions call (git).

Does Requesting Code Review access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Requesting Code Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Requesting Code Review use?

Requesting Code Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Requesting Code Review use?

About 807 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Requesting Code Review?

Skills that share tags, products or a category with Requesting Code Review: PR Bot Reviews (pgplex/pgconsole, 155 stars), New Lint (supabase/splinter, 280 stars), Mz PR Review (MaterializeInc/materialize, 6.4k stars) and SQL Code Review (totvs/engpro-advpl-tlpp-skills, 141 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Requesting Code Review?

t1mmen (a GitHub user) maintains it in t1mmen/srtd, which has 105 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 5, 2026.

Source: t1mmen/srtd on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Requesting Code Review

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Requesting Code Review

When to Request Review

Mandatory

Optional (But Recommended)

How to Request Review

Step 1: Identify the Change Range

Step 2: Dispatch the Code Reviewer

Step 3: Address Feedback by Severity

Responding to Feedback

When You Agree

When You Disagree

SRTD-Specific Review Focus

Service Boundaries

State Machine Integrity

Build Log Handling

Error Handling

Anti-Patterns (Red Flags)

Integration with Development Flow

After Each Task

Before PR Creation

After CI Feedback

Files

Compare with similar skills

Similar skills

More from t1mmen/srtd

Related

Questions about Requesting Code Review