Skip to content
Agentmart
Submit a tool

code-review-discipline

Use when requesting code review, reviewing completed work, receiving review feedback, evaluating reviewer suggestions, or deciding whether a change is ready…

Skill by fabiocantone

IndexedMIT
Write a review

Chalk Labs

Need help deploying code-review-discipline?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

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/fabiocantone-code-review-discipline

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 when requesting code review, reviewing completed work, receiving review feedback, evaluating reviewer suggestions, or deciding whether a change is ready after implementation

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-discipline

What's inside

Skill name
code-review-discipline
Description
Use when requesting code review, reviewing completed work, receiving review feedback, evaluating reviewer suggestions, or deciding whether a change is ready after implementation
License
MIT
Instructions
61 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Code Review Discipline

## Overview

Code review is a verification surface, not a social ritual. Use it to catch correctness, maintainability, security, testing, and documentation gaps before work is considered complete.

## Requesting Review

When asking another agent or reviewer to review work, provide:

- Goal and non-goals.
- Relevant plan or requirements.
- Files changed or diff range.
- Key decisions and constraints.
- Sources and known limitations.
- Verification already run.
- Specific review focus.

Ask the reviewer to return findings ordered by severity:

- `Blocking`: correctness, data loss, security, broken build, missing required verification.
- `Important`: likely regression, brittle design, missing test for changed behavior, confusing ownership.
- `Minor`: style, naming, small cleanup.

## Receiving Review

Before implementing feedback:

1. Read all items.
2. Restate unclear items or ask for clarification.
3. Verify each claim against the codebase.
4. Accept, reject, or defer with technical reasoning.
5. Fix one logical group at a time.
6. Re-run relevant verification.

Do not blindly implement external suggestions. Push back when a suggestion breaks existing behavior, conflicts with a recorded decision, violates YAGNI, or cannot be verified.

## Required Review Output

When completing a review pass, report:

```markdown
## Review Result

| Severity | Finding | Evidence | Decision | Verification |
| --- | --- | --- | --- | --- |
|  |  |  | accept/reject/defer |  |

Residual risk:
```

If no issues are found, say that explicitly and state remaining test gaps.

## Completion Criteria

- Review findings are grounded in file paths, diffs, tests, or docs.
- Blocking and Important findings are fixed or explicitly accepted by the user as deferred.
- Verification is fresh after fixes.
- Durable decisions or recurring review lessons are added to memory when relevant.

From fabiocantone/codersteroids, MIT.

More from fabiocantone/codersteroids

Signals

Stars
0
Forks
0
Open issues
1
Last commit (this folder)
May 26, 2026 (5 months ago)
Last release
May 27, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from fabiocantone

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get code-review-discipline running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying code-review-discipline?

CallGet help
Cite this page

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