Skip to content
TrustedSkillsbeta
Back to all skills

Code Review

Checked
duc01226·vlatest·backend·MIT

Automates backend code reviews, identifying potential bugs, style issues, and security vulnerabilities based on duc01226's standards.

Install on your platform

This skill no longer installs under the name code-review. duc01226/easyplatform has no skill named "code-review" any more. It was renamed, moved or deleted upstream.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-20. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

duc01226

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 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 duc01226/easyplatform at b62343ca0c.

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

Scanned
8 files, 4,032 lines
Copies in repo
2 — 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

What it does

This skill provides automated code review capabilities, identifying potential bugs and style issues within a codebase. It analyzes submitted code against established coding standards and best practices to improve code quality and maintainability. The tool aims to reduce the time spent on manual reviews while enhancing overall project robustness.

When to use it

  • Before merging pull requests: Automatically check new code contributions for errors before integration.
  • During refactoring efforts: Ensure that changes adhere to coding standards and don't introduce regressions.
  • For onboarding new developers: Provide immediate feedback on their code style and potential issues.
  • To enforce consistent coding styles across a team: Automate the application of project-specific guidelines.

Key capabilities

  • Automated bug detection
  • Style guide enforcement
  • Code standard checks
  • Identification of potential regressions

Example prompts

  • "Review this Python code for PEP 8 compliance."
  • "Analyze this JavaScript file and identify any potential security vulnerabilities."
  • "Check this Go function for common performance bottlenecks."

Tips & gotchas

The effectiveness of the skill depends on having well-defined coding standards or style guides. Providing these guidelines upfront will improve the accuracy and relevance of the code review results.