Skip to content
TrustedSkillsbeta
Back to all skills

Code Reviewer

Checked
ovachiever·vlatest·backend

This Code Reviewer analyzes your backend code for potential bugs 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 ovachiever/droid-tings --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

ovachiever

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 ovachiever/droid-tings at 7acd12a754.

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

Commit
7acd12a754
Manifest
skills/code-reviewer/SKILL.md
Scanned
7 files, 841 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

Code Reviewer

What it does

This agent acts as an automated peer reviewer, analyzing submitted code for logic errors, security vulnerabilities, and adherence to best practices. It provides immediate feedback to help developers improve code quality before merging changes into the main branch.

When to use it

  • Before pushing critical updates to a production environment to catch potential bugs early.
  • During pull request workflows to ensure new features align with existing architectural standards.
  • When learning a new language or framework to get instant, expert-level critiques on implementation details.
  • For auditing legacy codebases to identify outdated patterns or security risks.

Key capabilities

  • Identifies logical flaws and runtime errors within the provided code snippets.
  • Flags security vulnerabilities such as injection risks or improper authentication handling.
  • Enforces coding style guides and consistency across different modules.
  • Suggests refactoring opportunities to improve performance and readability.

Example prompts

  • "Review this Python function for memory leaks and suggest optimizations."
  • "Analyze the following React component for potential XSS vulnerabilities."
  • "Critique this database migration script for data integrity issues."

Tips & gotchas

Ensure you provide complete context, including relevant dependencies or configuration files, so the reviewer understands the full environment. While powerful, always verify critical security fixes manually, as AI agents may occasionally miss edge cases specific to your unique business logic.