Skip to content
TrustedSkillsbeta
Back to all skills

Code Review

Listed
simhacker·vlatest·backend·MIT

Simhacker's simhacker-code-review identifies potential vulnerabilities and inefficiencies in backend code through automated security analysis.

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 simhacker/moollm --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

simhacker

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    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 simhacker/moollm at 8f6d840b2f.

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

Commit
8f6d840b2f
Manifest
skills/code-review/SKILL.md
Scanned
0 files
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 bugs and style issues within a given codebase. It analyzes code for common errors like incorrect variable usage, logic flaws, and adherence to coding standards. The tool aims to improve code quality and reduce the risk of introducing defects during development.

When to use it

  • Reviewing pull requests before merging into a main branch.
  • Identifying potential vulnerabilities in open-source projects.
  • Ensuring new team members adhere to established coding conventions.
  • Automating repetitive code review tasks, freeing up human reviewers for more complex issues.

Key capabilities

  • Automated bug detection
  • Style guide enforcement
  • Code quality analysis
  • Identification of potential vulnerabilities

Example prompts

  • "Review this Python script for errors and style violations: [paste code here]"
  • "Analyze this JavaScript file and suggest improvements to its efficiency: [paste code here]"
  • "Check this C++ function for memory leaks and security issues: [paste code here]"

Tips & gotchas

The effectiveness of the review depends on the quality and clarity of the provided codebase. Ensure the code is well-formatted and includes sufficient context for accurate analysis.