Skip to content
TrustedSkillsbeta
Back to all skills

Code Review Checklist

Checked
groupzer0·vlatest·backend·MIT

Automates backend code review checklists, ensuring adherence to groupzer0's standards for security, performance, and maintainability.

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 groupzer0/vs-code-agents --skill code-review-checklist -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

groupzer0

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 groupzer0/vs-code-agents at c28eb5fe2c.

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

Scanned
4 files, 467 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 comprehensive checklist to guide code reviews, ensuring thoroughness and consistency. It helps identify potential issues related to security, performance, maintainability, and adherence to coding standards. The checklist covers aspects like error handling, input validation, and test coverage.

When to use it

  • Reviewing pull requests from other developers on a backend project.
  • Performing self-reviews before submitting code for approval.
  • Ensuring new team members understand the codebase's quality standards.
  • Automating parts of the review process to improve efficiency and reduce human error.

Key capabilities

  • Provides a structured checklist for code reviews.
  • Covers security, performance, maintainability, and coding standards.
  • Includes checks for error handling, input validation, and test coverage.

Example prompts

  • "Review this pull request using the code review checklist."
  • "Generate a code review checklist for this file: src/user_authentication.py."
  • "What are some potential security vulnerabilities in this code snippet?"

Tips & gotchas

This skill is most effective when used with clear coding standards and guidelines already established within the project. While it provides a detailed checklist, it's not a substitute for human judgment and understanding of the specific codebase.