Skip to content
TrustedSkillsbeta
Back to all skills

Code Review Checklist

Checked
davila7·vlatest·backend·MIT

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 davila7/claude-code-templates --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

davila7

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 davila7/claude-code-templates at 79182c51fb.

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

Commit
79182c51fb
Manifest
cli-tool/components/skills/development/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

The code-review-checklist skill provides a structured framework for AI agents to systematically evaluate pull requests, ensuring consistency and quality in backend development workflows. It guides the agent through specific verification steps rather than offering generic feedback.

When to use it

  • Before merging critical production changes to catch potential regressions early.
  • During onboarding phases to enforce team-specific coding standards automatically.
  • When reviewing complex logic implementations to verify edge case handling.
  • To generate a standardized checklist for junior developers to self-assess their code.

Key capabilities

  • Systematic evaluation of pull requests against defined criteria.
  • Generation of actionable feedback based on specific review points.
  • Enforcement of consistent backend development standards across the team.

Example prompts

  • "Run the code-review-checklist on this PR to verify database transaction handling and error logging."
  • "Use the checklist to audit my recent API endpoint implementation for security vulnerabilities."
  • "Generate a review summary using the standard checklist before I merge these configuration changes."

Tips & gotchas

Ensure your team has agreed upon specific coding standards beforehand, as the skill relies on clear criteria to provide effective feedback. This tool complements human review but should not replace final architectural sign-offs for high-risk systems.