Skip to content
TrustedSkillsbeta
Back to all skills

Code Review

Checked
htlin222·vlatest·backend·MIT

Automates Python/Java backend code reviews, identifying potential bugs, style issues, and security vulnerabilities for improved quality.

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 htlin222/dotfiles --skill code-review --full-depth -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

htlin222

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 htlin222/dotfiles at b7604b0cf6.

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

Commit
b7604b0cf6
Manifest
claude.symlink/archived-skills/code-review/SKILL.md
Scanned
1 file, 229 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. It analyzes provided code snippets, identifies potential issues like style violations and bugs, and suggests improvements based on best practices. The agent can also be instructed to focus on specific areas of concern within the code.

When to use it

  • Before submitting a pull request: Ensure your changes meet coding standards before sharing them with others.
  • Learning a new codebase: Quickly understand the style and conventions used in an existing project.
  • Refactoring legacy code: Identify potential problems and areas for improvement during refactoring efforts.
  • Pair programming alternative: Get automated feedback on your code as you write it, similar to having a pair programmer.

Key capabilities

  • Automated code analysis
  • Style violation detection
  • Bug identification
  • Suggestion of improvements
  • Focus on specific areas of concern

Example prompts

  • "Review this Python function for potential errors and style issues: [code snippet]"
  • "Can you check this JavaScript file for security vulnerabilities?"
  • "Analyze this C++ code and suggest ways to improve its performance."

Tips & gotchas

The quality of the review depends on the clarity and completeness of the provided code. For best results, provide complete files or functions rather than isolated snippets.