Skip to content
Agentmart
Submit a tool

code-review

Use after a feature, before merge or PR, or when the user asks for a review.

Skill by sardul3

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/sardul3-code-review

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use after a feature, before merge or PR, or when the user asks for a review. Spawn the code-reviewer agent on the diff, not this session's chat history.

Use cases: agent-building

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/code-review

What's inside

Skill name
code-review
Description
Use after a feature, before merge or PR, or when the user asks for a review. Spawn the code-reviewer agent on the diff, not this session's chat history.
License
MIT
Instructions
25 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Code review

Review the **work product**, not the author's chain of thought.

## When

- After a non-trivial feature or bugfix
- Before commit/PR when the user wants a check
- When stuck and a second pass would help

## How

1. `git diff` (or named SHAs) is the scope unless the user names files.
2. Spawn the **code-reviewer** agent with: what changed, what it should do, base/head if known.
3. Act on critical/major findings. Do not rubber-stamp.

## Do not

- Ask the reviewer to re-implement
- Paste secrets
- Treat style nits as blockers unless the project rules say so

If a finding is a missing durable convention, flag it for the parent to apply via `agent-memory`. The reviewer does not Write metadata files.

From sardul3/dev-conductor, MIT.

More from sardul3/dev-conductor

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Aug 30, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/sardul3/dev-conductor
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from sardul3

Cite this page

code-review skill. Agent Mart. https://agentmart.dev/skills/sardul3-code-review (last updated 2026-10-24)