Code Review
CheckedAutomates Python code reviews focusing on style, security vulnerabilities, and potential performance bottlenecks using established best practices.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add steveclarke/dotfiles --skill code-review -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
steveclarke
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.
Automated safety checks
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 steveclarke/dotfiles at 1e468cbcab.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 1e468cbcab
- Scanned
- 1 file, 341 lines
About this skill
What it does
This skill provides automated code review capabilities, identifying potential issues and suggesting improvements. It analyzes code for style inconsistencies, common errors, and adherence to best practices. The goal is to improve code quality and reduce the burden on human reviewers.
When to use it
- Before submitting a pull request: Ensure code meets standards before wider team review.
- During onboarding of new developers: Provide immediate feedback on coding style.
- For repetitive tasks or boilerplate code: Quickly identify potential errors in standardized sections.
- To enforce consistent coding practices across a project.
Key capabilities
- Automated code analysis
- Style consistency checks
- Error detection
- Best practice adherence suggestions
Example prompts
- "Review this Python file for style and common errors."
- "Analyze this JavaScript function and suggest improvements."
- "Check this Go code against the established project guidelines."
Tips & gotchas
The effectiveness of the review depends on having clear, well-defined coding standards or best practices. Without these, the skill's suggestions may be less relevant or helpful.