Skip to content
TrustedSkillsbeta
Back to all skills

Code Reviewer

Checked
alirezarezvani·vlatest·backend·MIT

This AI analyzes your backend code for potential bugs, vulnerabilities, and style issues, boosting code quality and reducing errors.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add alirezarezvani/claude-skills --skill code-reviewer -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

alirezarezvani

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned alirezarezvani/claude-skills at 19392f7a08.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
19392f7a08
Manifest
engineering-team/skills/code-reviewer/SKILL.md
Scanned
29 files, 4,602 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The alirezarezvani-code-reviewer skill enables AI agents to analyze and provide feedback on backend code. It identifies potential bugs, performance issues, and style inconsistencies in code written in languages like Python, JavaScript, and Go.

When to use it

  • Before merging a pull request to ensure code quality
  • To review contributions from new team members
  • When refactoring legacy code for maintainability
  • To enforce coding standards across a development team

Key capabilities

  • Detects common bugs and logical errors in backend code
  • Suggests performance improvements and optimization strategies
  • Enforces consistent coding style and best practices
  • Supports multiple backend programming languages

Example prompts

  • "Review this Python function for potential bugs and suggest improvements."
  • "Analyze the JavaScript API endpoint for security vulnerabilities."
  • "Check this Go code for adherence to our team's coding standards."

Tips & gotchas

  • Ensure that the code being reviewed is well-documented, as the skill may struggle with poorly written or ambiguous logic.
  • The skill works best when provided with clear context about project requirements and style guidelines.