Code Review Checklist

Name: Code Review Checklist
Author: curiositech

Listed

curiositech·vlatest·backend·MIT

Automates backend code reviews using a customizable checklist to ensure quality, security, and adherence to best practices.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add curiositech/some_claude_skills --skill code-review-checklist -a claude-code

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

curiositech

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 5 Oct 2026

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 curiositech/some_claude_skills at 6713fc7a64.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: 6713fc7a64
Manifest: .claude/skills/code-review-checklist/SKILL.md
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 helps identify potential bugs, security vulnerabilities, and style inconsistencies. The checklist covers aspects like error handling, edge cases, and adherence to coding standards.

When to use it

Reviewing pull requests before merging into the main branch.
Performing a thorough review of newly written or modified code segments.
Ensuring compliance with specific project coding guidelines.
Onboarding new developers by providing them with a standardized review process.

Key capabilities

Provides a comprehensive checklist for code reviews.
Covers various aspects of code quality (error handling, security, style).
Helps identify potential bugs and vulnerabilities.
Promotes adherence to coding standards.

Example prompts

"Review this Python code snippet for potential errors and suggest improvements."
"Generate a checklist for reviewing this JavaScript function, focusing on edge cases."
"Analyze this Go code and ensure it follows best practices for error handling."

Tips & gotchas

The skill assumes basic familiarity with the programming language being reviewed. While comprehensive, the checklist might need to be adapted based on specific project requirements or domain expertise.