Skip to content
Agentmart
Submit a tool

code-review

Review code for correctness, security, maintainability, test coverage, and regression risk with concrete findings and evidence.

Skill by hoskengadu

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/hoskengadu-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

Review code for correctness, security, maintainability, test coverage, and regression risk with concrete findings and evidence.

Use cases: testing, security

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
Review code for correctness, security, maintainability, test coverage, and regression risk with concrete findings and evidence.
License
MIT
Metadata
short-description: Technical code review guidance
Instructions
33 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Code Review

Use this skill when reviewing code, merge requests, or diffs.

## Review Priorities

1. Correctness
2. Security
3. Reliability
4. Maintainability
5. Test coverage
6. Performance only when evidence suggests it matters

## Review Rules

- Focus on confirmed issues first.
- For each finding, explain the impact and point to the evidence.
- Distinguish bugs from style preferences.
- Be precise about behavior, not generic.
- Call out missing tests when they matter to the changed behavior.
- If no findings are present, say so and mention residual risks or gaps.

## Stack Selection

If the technology stack is not explicit, ask whether the review should follow `.NET`, `Java`, or `Python` conventions before giving stack-specific guidance.

When the stack is known, use the matching specialized skill:

- `.NET` review: `code-review-dotnet`
- `Java` review: `code-review-java`
- `Python` review: `code-review-python`

From hoskengadu/software-engineering-skills, MIT.

More from hoskengadu/software-engineering-skills

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Aug 20, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

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

More from hoskengadu

Cite this page

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