Skip to content
TrustedSkillsbeta
Back to all skills

Reviewing Code

Checked
julianobarbosa·vlatest·backend·MIT

This AI analyzes your code for potential issues and improvements, boosting code quality and reducing bugs – a valuable tool for developers.

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 julianobarbosa/claude-code-skills --skill reviewing-code -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

julianobarbosa

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 julianobarbosa/claude-code-skills at 57f5fe8c0d.

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

Scanned
1 file, 41 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

This skill allows an AI agent to review code and provide feedback. It can identify potential bugs, suggest improvements for readability and efficiency, and ensure adherence to coding standards. The agent aims to offer constructive criticism that helps developers refine their work.

When to use it

  • Code Review Assistance: Use this when you need a quick second opinion on your code before submitting a pull request.
  • Learning New Languages/Frameworks: Have the agent review code written in unfamiliar technologies to identify potential pitfalls and best practices.
  • Refactoring Existing Code: Get suggestions for improving the structure and clarity of existing codebase segments.
  • Ensuring Coding Standards: Verify that new or modified code aligns with established team coding conventions.

Key capabilities

  • Bug detection
  • Readability improvement suggestions
  • Efficiency optimization recommendations
  • Coding standards adherence checks

Example prompts

  • "Review this Python function and suggest improvements: [code snippet]"
  • "Can you check this JavaScript code for potential errors?"
  • "Please review the following C++ code and ensure it follows best practices."

Tips & gotchas

The quality of feedback depends on the clarity and completeness of the provided code. Providing context about the project or specific coding standards will improve results.