Skip to content
TrustedSkillsbeta
Back to all skills

Code Review Ai Ai Review

Listed
sickn33·vlatest·backend·MIT

Helps with code review, AI as part of developing backend services and APIs workflows.

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 sickn33/agentic-awesome-skills --skill code-review-ai-ai-review -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

sickn33

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 sickn33/antigravity-awesome-skills at 5a4cdd9df8.

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

Scanned
0 files
Copies in repo
3 — all of them scanned
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

The code-review-ai-ai-review skill enables AI agents to automatically analyze and critique source code submissions. It identifies potential bugs, security vulnerabilities, and style inconsistencies to improve overall code quality before merging.

When to use it

  • Before integrating a pull request into the main branch to catch errors early.
  • During continuous integration pipelines to enforce coding standards automatically.
  • When onboarding new developers who need immediate feedback on their implementation patterns.
  • To reduce manual review time for large-scale codebases with repetitive logic.

Key capabilities

  • Automated syntax and logic error detection across multiple programming languages.
  • Identification of security flaws such as injection vulnerabilities or unsafe data handling.
  • Consistency checks against defined style guides and architectural patterns.
  • Generation of actionable feedback reports highlighting specific lines requiring attention.

Example prompts

  • "Review the attached Python script for potential race conditions and memory leaks."
  • "Analyze this JavaScript module for security vulnerabilities before we deploy it to production."
  • "Check if this Rust implementation follows our project's concurrency guidelines and formatting rules."

Tips & gotchas

Ensure your repository includes a .editorconfig or specific linting configuration files so the AI understands your team's style preferences. While the tool catches many issues, always verify critical logic changes manually as AI may miss complex business rule nuances.