Skip to content
TrustedSkillsbeta
Back to all skills

Code Review Checklist

Checked
htooayelwinict·vlatest·backend

Automates backend code reviews using a customizable checklist, ensuring consistency and identifying potential issues efficiently.

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 htooayelwinict/claude-config --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

htooayelwinict

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 htooayelwinict/claude-config at 69fb54bd96.

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

Scanned
2 files, 217 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 code review processes. It ensures thoroughness and consistency in evaluating code changes, covering aspects like functionality, style, security, and documentation. The skill aims to improve the overall quality of the codebase by identifying potential issues early on.

When to use it

  • Reviewing pull requests from other developers before merging into a main branch.
  • Evaluating automated code contributions or generated code snippets.
  • Ensuring adherence to coding standards and best practices within a project.
  • Performing security audits of new or modified code.

Key capabilities

  • Provides a structured checklist for code review.
  • Covers functionality, style, security, and documentation aspects.
  • Aims to improve overall code quality.

Example prompts

  • "Review this pull request: [link to pull request]"
  • "Can you perform a code review of this file? [file content]"
  • "Generate a checklist for reviewing backend API changes."

Tips & gotchas

The skill's effectiveness relies on providing the AI agent with sufficient context, such as the codebase or specific files being reviewed. It is designed to augment human review, not replace it entirely; always validate the AI’s findings.