Skip to content
TrustedSkillsbeta
Back to all skills

Code Review Checklist

Checked
jarmen423·vlatest·backend

Automates backend code reviews using a comprehensive checklist focused on security, performance, and maintainability.

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 jarmen423/skills --skill code-review-checklist --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

jarmen423

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 jarmen423/skills at d016f7d2c7.

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

Commit
d016f7d2c7
Manifest
downloaded-skills/security-testing/code-review-checklist/SKILL.md
Scanned
1 file, 433 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 a checklist to guide AI agents through thorough code reviews. It ensures that key aspects of code quality, security, and maintainability are considered during the review process. The agent can use this checklist to identify potential issues and suggest improvements to developers.

When to use it

  • Reviewing pull requests before merging into a main branch.
  • Assessing code contributions from external collaborators.
  • Performing automated checks on newly written code.
  • Ensuring adherence to coding standards within a project.

Key capabilities

  • Provides a structured checklist for code review.
  • Focuses on code quality, security and maintainability.
  • Offers suggestions for improvements based on the checklist items.

Example prompts

  • "Review this pull request using the code review checklist."
  • "Can you perform a code review of this file, focusing on potential security vulnerabilities?"
  • "Apply the code review checklist to these changes and provide feedback."

Tips & gotchas

The effectiveness of this skill depends on providing it with clear context about the codebase's standards and conventions. It is best used in conjunction with human oversight for complex or critical codebases.