code-reviewer_skill

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

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

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

  • SKILL.md732 B

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

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.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational