Skip to content
TrustedSkillsbeta
Back to all skills

Code Review Checklist

Listed
erichowens·vlatest·backend·MIT

Automates code reviews using Erich Owens' established checklist, ensuring consistency and identifying potential backend issues.

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 curiositech/some_claude_skills --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

erichowens

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    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 erichowens/some_claude_skills at 6713fc7a64.

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

Scanned
0 files
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 structured code review checklist to ensure higher quality and more maintainable code. It guides the AI agent through key areas like functionality, error handling, security, and performance. The resulting reviews are designed to be thorough and actionable for developers.

When to use it

  • Before merging pull requests: Use this skill to automatically generate a checklist of items to review before integrating new code into a codebase.
  • During onboarding of new team members: Provide a consistent and standardized code review process for new developers joining the team.
  • For complex or critical features: Ensure thoroughness in reviewing changes related to important functionality.
  • To improve overall code quality: Regularly apply this skill to all code reviews to foster a culture of continuous improvement.

Key capabilities

  • Provides a structured checklist for code review.
  • Covers areas like functionality, error handling, and security.
  • Generates actionable feedback for developers.
  • Promotes consistent code quality across projects.

Example prompts

  • "Review this pull request: [link to pull request]"
  • "Generate a code review checklist for this file: [file path]"
  • "Perform a security-focused code review on this function: [function name]"

Tips & gotchas

This skill is most effective when provided with access to the codebase being reviewed. The quality of the review depends heavily on the clarity and completeness of the code itself.