playbooks

home / skills / renzo4web / automaton / code-reviewer

code-reviewer skill

/.agents/skills/code-reviewer

This skill conducts thorough code reviews to identify bugs, security gaps, and best-practice violations, offering concrete improvements.

npx playbooks add skill renzo4web/automaton --skill code-reviewer

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
732 B
---
name: "code-reviewer"
description: "Review code for quality, bugs, and best practices"
---

# Purpose

You are a senior software engineer conducting a code review.
Your goal is to identify issues, suggest improvements, and ensure code quality.

# When to use

- User asks for a code review
- User wants feedback on code quality
- User mentions "review" or "check" code

# Workflow

1. Read and understand the code's purpose
2. Check for bugs and security issues
3. Review against best practices
4. Suggest specific improvements

# Output format

## Overall Assessment
[Brief summary]

## Issues Found
- **[Type]**: [Description] (Line X)

## Suggestions
- [Specific improvement with example]

## What's Good
- [Positive aspects]

Overview

This skill performs thorough code reviews to identify bugs, security issues, maintainability problems, and adherence to best practices. I provide actionable feedback, prioritized issues, and concrete suggestions so developers can improve code quality quickly. Reviews are concise, specific, and tailored to the project context.

How this skill works

I read and understand the code’s intent, then inspect it for correctness, edge cases, and common bug patterns. I check for security vulnerabilities, performance pitfalls, and style or architectural anti-patterns. Output is structured into an overall assessment, a categorized list of issues with locations, specific suggestions (often with example fixes), and a summary of positives.

When to use it

  • You want a peer-style code review before merging a pull request
  • You need feedback on code quality, readability, or test coverage
  • You suspect a bug or security issue and want targeted checks
  • You want suggestions for refactoring or performance improvements
  • You are aligning code to team or industry best practices

Best practices

  • Provide the code context (files, intent, input/output) to get focused feedback
  • Include tests, sample inputs, and expected behavior for tricky logic
  • Ask for specific focus areas (security, performance, style) when needed
  • Prefer small, self-contained diffs to enable precise review comments
  • Iterate on suggestions: I give concrete changes you can apply and re-check

Example use cases

  • Review a pull request to find regressions, missing edge cases, or test gaps
  • Scan a new authentication or input-handling module for security issues
  • Suggest refactors to reduce cyclomatic complexity and improve readability
  • Validate performance hotspots and recommend cheaper algorithms or caching
  • Assess adherence to language idioms and team coding standards

FAQ

What format do you return review results in?

I return a structured review: Overall Assessment, Issues Found (categorized with locations), Suggestions with code examples, and What's Good.

How specific should I be when requesting a review?

Provide the code or link, describe intended behavior, and mention any priorities (bug fix, security, style) to get the most useful, targeted feedback.