Guide · Agent skill
How to use the Team Code Review agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Team Code Review skill (skill name code-review) is a set of written instructions that tells an AI agent how to review Python code against a team's standards. It is aimed at developers who want a consistent first pass on Python pull requests before a person reviews them. This guide explains what a skill is, how to install this one, how to ask for a review, and where its limits are.
Team Code Reviewkyegomez/swarms · Apache-2.0 Download the skill Quick start
- 1Download the ZIP. Get the skill ZIP from this page.
- 2Unzip the folder. Unzip the file so you have a folder containing SKILL.md.
- 3Choose a location. Use ~/.claude/skills/ for personal use or .claude/skills/ inside a project.
- 4Or upload in the Claude apps. Open Settings, go to Capabilities, and upload the skill under Skills.
- 5Ask for a review. Request a review of Python code in plain language and point to the file or change.
- 6Check the findings. Read the list ordered by severity and check each file and line it names.
What the skill makes the agent do
The skill is a single file, SKILL.md, that describes a review checklist with three areas. Correctness: the agent checks that the code does what the pull request says, and looks for off-by-one errors, unhandled None values and swallowed exceptions. Tests: every bug fix should come with a test that fails without the fix. Security: the agent flags SQL built from strings, use of eval, and secrets left in code or logs.
The skill asks for findings as a list ordered from most severe to least severe, with each item pointing to the file and line.
Install the skill from a ZIP file
Download the ZIP for this skill from this page and unzip it. You can install it for yourself across all projects or for a single project.
For a personal install, place the unzipped skill folder in ~/.claude/skills/. For a single project, place it in that project's .claude/skills/ folder.
If you use the Claude apps instead, open Settings, go to Capabilities, and upload the skill under Skills.
- Personal: ~/.claude/skills/
- Project only: .claude/skills/ inside your project
- Claude apps: Settings → Capabilities → Skills
Trigger the skill with a natural request
You do not need a special command. Ask the agent to review code in plain language, and mention that it should follow the team's standards or the code review checklist. The skill's description is about reviewing Python code for bugs, missing tests and security issues, so requests that match that purpose are the ones that should lead the agent to use it.
Point the agent at the change you care about, such as a file, a diff or a pull request description, so it can check the code against what the change says it does.
- Review this Python pull request against the team's standards and list the findings by severity.
- Check this bug fix for missing tests and risky patterns like eval or SQL built from strings.
- Look over this Python change for off-by-one errors and unhandled None values, with file and line for each issue.
What to expect in the output
Expect a list of findings, most severe first. Each finding should name the file and line. Because the skill is a checklist, the same categories are checked each time, which helps when a team wants feedback to follow one standard.
Treat the result as a first pass. It can miss problems, so a person should still review the change.
Requirements and safety notes
The skill lists no requirements. It does not run scripts and does not use the network. It consists of instructions in SKILL.md only.
It is a checklist prompt, not a security scanner or audit. It can miss vulnerabilities and gives no guarantee that code is secure. Do not use it as the only sign-off for security-critical code.
- Runs scripts: no
- Uses network: no
- Files included: SKILL.md
- Licence: Apache-2.0
Tips for better reviews
Give the agent the pull request description or a clear statement of intent, because the first check is whether the code matches what the change says it does.
Include the tests in the change so the agent can check that bug fixes come with a test that fails without the fix.
Use the skill for Python only. Its checks are Python-focused, so it may miss language-specific issues in other languages.
What people use it for
- First-pass review of a Python pull request before a human reviewer looks at it.
- Checking a bug fix for a missing test that would fail without the fix.
- Scanning Python changes for SQL built from strings, eval calls or secrets in code or logs.
- Giving a team consistent review feedback that follows the same checklist each time.
Frequently asked questions
How do I install the code-review agent skill?
Download the ZIP from this page and unzip it. Place the folder in ~/.claude/skills/ for personal use or in a project's .claude/skills/ folder, or upload it in the Claude apps under Settings → Capabilities → Skills.
Does the code-review skill need anything else installed?
The skill lists no requirements. It runs no scripts and uses no network, and it consists of the SKILL.md instructions file.
Is the code-review skill free?
The skill is licensed under Apache-2.0. This page does not list a price, so check the licence terms for how you may use it.
Can I use this skill for languages other than Python?
Not as intended. The skill describes Python-focused checks, so its rules would miss language-specific issues in other languages.
Can the code-review skill replace a security audit?
No. It is a checklist prompt, not a security scanner or audit. It can miss vulnerabilities and gives no guarantee, so it should not be the only sign-off for security-critical code.
How is this different from a linter or static analysis tool?
A linter or scanner applies fixed rules automatically. This skill tells an agent to review code against a written checklist covering correctness, tests and security, and to report findings ordered by severity with file and line.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you are a developer or team working on Python pull requests and want a consistent first-pass review that follows the same checklist each time. Pick something else for non-Python codebases, or for security-critical sign-off that needs a real scanner or audit.
Download the skill