Skip to content
TrustedSkillsbeta
Back to all skills

Code Review

Checked
outfitter-dev·vlatest·backend·MIT

Automates backend code reviews, identifying potential bugs, security vulnerabilities, and style inconsistencies for faster iteration.

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 outfitter-dev/agents --skill code-review -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

outfitter-dev

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 outfitter-dev/agents at d37fffdd50.

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

Scanned
2 files, 1,179 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 provides automated code review capabilities, identifying potential issues and suggesting improvements. It analyzes code for style inconsistencies, common errors, and adherence to best practices. The agent can also provide explanations for identified problems, helping developers understand the reasoning behind suggestions.

When to use it

  • Before submitting a pull request: Quickly identify and address minor issues before formal review.
  • For onboarding new team members: Ensure consistent coding style across the project.
  • During code refactoring: Verify that changes maintain quality and don't introduce regressions.
  • Automated CI/CD pipelines: Integrate into automated workflows for continuous code quality checks.

Key capabilities

  • Code analysis
  • Style checking
  • Error detection
  • Best practice adherence
  • Explanation of findings

Example prompts

  • "Review this Python file for potential errors and style issues."
  • "Can you check this JavaScript code against our team's coding standards?"
  • "Analyze this Go function and suggest improvements for readability."

Tips & gotchas

The skill’s effectiveness depends on providing clear instructions and context, such as specifying the programming language or relevant coding standards. Ensure the agent has access to any project-specific style guides for optimal results.