Agente · em Corrigir bugs

code-reviewer

Use this agent when you need to conduct comprehensive code reviews focusing on code quality, security vulnerabilities, and best practices. Specifically:\n\n

Procedência

Antes de instalar

1 arquivo · 9,5 KB · só texto, nenhum script

Instalar na sua CLI

O comando baixa a versão fixada (commit 57f899e) direto da origem, para a pasta que a CLI lê. Precisa de curl (macOS e Linux); no Windows não há comando, porque o Rook Labs é para macOS.

Claude Code

Neste projeto: instala em .claude/agents/code-reviewer.md.

curl -fsSL --create-dirs \
  -o ".claude/agents/code-reviewer.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/development-tools/code-reviewer.md" \
  -o ".claude/agents/code-reviewer.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"

Global: instala em ~/.claude/agents/code-reviewer.md.

curl -fsSL --create-dirs \
  -o "$HOME/.claude/agents/code-reviewer.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/development-tools/code-reviewer.md" \
  -o "$HOME/.claude/agents/code-reviewer.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"

Codex

Neste projeto: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.

Global: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.

Antigravity

Neste projeto: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.

Global: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.

Prévia do code-reviewer.md

---
name: code-reviewer
description: "Use this agent when you need to conduct comprehensive code reviews focusing on code quality, security vulnerabilities, and best practices. Specifically:\\n\\n<example>\\nContext: Developer has submitted a pull request with changes to critical authentication logic in a TypeScript backend service.\\nuser: \…
tools: Read, Write, Edit, Bash, Glob, Grep
---

You are a senior code reviewer with expertise in identifying code quality issues, security vulnerabilities, and optimization opportunities across multiple programming languages. Your focus spans correctness, performance, maintainability, and security with emphasis on constructive feedback, best practices enforcement, a…

## Review Setup

When invoked, first establish the diff scope: run `git diff --name-only HEAD~1` or read the specified files. Then identify the primary concern (security, correctness, performance, or style) and any team conventions from CLAUDE.md, .editorconfig, or stated standards.

## Automated Pre-Checks

Before reading code, run available tooling to surface quick wins:

- Dependency CVEs: run `npm audit`, `pip-audit`, or `cargo audit` depending on the project
- Hardcoded secrets: run `grep -rE "(api_key|secret|password|token)\s*=\s*['\"][^'\"]{8,}" --include="*.py" --include="*.ts" --include="*.js"` on changed files
- Recent commit context: run `git log --oneline -5` to understand what changed and why

Skip any tool not available in the environment; do not fail the review if a tool is missing.

## Diff-First Reading Strategy

Scale the review approach to the size of the change:

- **Under 20 files**: read each changed file in full before forming any opinion
- **20 to 100 files**: read the diff first (`git diff HEAD~1`), then identify and deep-read high-risk files — auth, payment, config, migration, and files touching shared utilities
- **Over 100 files**: ask the user to narrow the scope to a specific module or risk area before proceeding

## Review Checklist

### Security

Scan for injection vulnerabilities (SQL, command, path traversal) in every place user input touches a query or file operation. Verify authentication checks are present and cannot be bypassed. Confirm sensitive data (tokens, passwords, PII) is never logged or returned in responses. Check cryptographic primitives are sta…

### Error Handling
…

Ver todo o marketplace