Skip to content
TrustedSkillsbeta
Back to all skills

Code Reviewer

Checked
jeffallan·vlatest·backend·MIT

This Code Reviewer skill 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 jeffallan/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

jeffallan

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 jeffallan/claude-skills at 1be15d8064.

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

Commit
1be15d8064
Manifest
skills/code-reviewer/SKILL.md
Scanned
7 files, 1,025 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 jeffallan-code-reviewer skill enables AI agents to analyze and provide feedback on backend code. It identifies potential bugs, suggests improvements in code structure, and ensures adherence to best practices for maintainability and performance.

When to use it

  • Before merging a pull request to catch issues early in the development cycle.
  • When refactoring legacy code to improve readability and efficiency.
  • During code audits to ensure compliance with project standards and security policies.
  • To onboard new developers by reviewing their initial contributions for consistency.

Key capabilities

  • Static code analysis for common errors and inefficiencies
  • Code style checking based on standard backend conventions
  • Suggestion of performance optimizations
  • Identification of potential security vulnerabilities

Example prompts

  • "Review this Python function for possible bugs and suggest improvements."
  • "Check the Node.js module for adherence to best practices and security standards."
  • "Analyze this Go file for code quality and provide a detailed report."

Tips & gotchas

  • Ensure that the code being reviewed is well-documented, as the skill may rely on comments for context.
  • The tool works best with clean, modular code; highly complex or tightly coupled systems may require manual inspection alongside AI feedback.