Skip to content
TrustedSkillsbeta
Back to all skills

Code Review And Quality

Checked
addyosmani·vlatest·backend·MIT

Analyzes backend code for style, potential bugs, performance bottlenecks, and adherence to best practices.

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 addyosmani/agent-skills --skill code-review-and-quality -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

addyosmani

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 addyosmani/agent-skills at 2686b620fc.

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

Commit
2686b620fc
Manifest
skills/code-review-and-quality/SKILL.md
Scanned
1 file, 379 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 and quality analysis. It can identify potential bugs, security vulnerabilities, and style inconsistencies within a codebase. The agent will provide suggestions for improvement based on established best practices and coding standards.

When to use it

  • Before merging pull requests: Ensure code meets quality standards before integration into the main branch.
  • During code refactoring: Identify potential issues introduced during restructuring efforts.
  • For onboarding new developers: Provide automated feedback on their contributions, promoting consistent coding style and best practices.
  • To proactively improve existing codebases: Regularly scan for common errors and areas needing attention.

Key capabilities

  • Bug detection
  • Security vulnerability identification
  • Style consistency checks
  • Adherence to coding standards
  • Automated feedback and suggestions

Example prompts

  • "Review this pull request: [link to pull request]"
  • "Analyze this file for potential bugs and security vulnerabilities: [file path]"
  • "Check the code in this repository against PEP 8 style guidelines: [repository URL]"

Tips & gotchas

The effectiveness of this skill depends on the clarity and specificity of coding standards provided. It's best used with a well-defined set of rules or guidelines to ensure relevant feedback.