Skip to content
TrustedSkillsbeta
Back to all skills

Code Review

Checked
mrgoonie·vlatest·backend

Automates Python/Node.js backend code reviews, identifying potential bugs, style issues, and security vulnerabilities.

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 mrgoonie/claudekit-skills --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

mrgoonie

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 mrgoonie/claudekit-skills at 80113d86bc.

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

Scanned
4 files, 550 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 mrgoonie-code-review 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
  • When refactoring legacy code to improve readability and efficiency
  • To enforce coding standards across a development team
  • When onboarding new developers to review their initial contributions

Key capabilities

  • Detects common bugs and logical errors in backend code
  • Provides suggestions for optimizing performance and reducing complexity
  • Enforces adherence to coding conventions and style guides
  • Highlights security vulnerabilities or potential edge cases

Example prompts

  • "Review this Python function for possible memory leaks."
  • "Check the Node.js API endpoint for compliance with REST best practices."
  • "Analyze this Go code snippet for concurrency issues."

Tips & gotchas

  • Ensure that the code being reviewed is well-documented to help the AI agent provide accurate feedback.
  • While the skill can identify potential issues, it should not replace manual testing or peer review.