Skip to content
TrustedSkillsbeta
Back to all skills

Review Clean Code

Checked
heyvhuang·vlatest·backend·MIT

Analyzes backend code for style inconsistencies, potential bugs, and areas needing refactoring, suggesting improvements.

Repository

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 heyvhuang/ship-faster --skill review-clean-code -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

heyvhuang

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 heyvhuang/ship-faster at 64047d24e0.

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

Commit
64047d24e0
Manifest
skills/review-clean-code/SKILL.md
Scanned
6 files, 1,330 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

The review-clean-code skill enables AI agents to analyze codebases and identify areas requiring refactoring to improve maintainability. It specifically detects issues like overly complex functions, missing documentation, and inconsistent naming conventions across your project.

When to use it

  • Before merging a large pull request to ensure new logic adheres to established style guides.
  • During a codebase migration to spot legacy patterns that hinder modernization efforts.
  • When onboarding new developers to quickly highlight areas needing clarity or simplification.
  • As part of a CI/CD pipeline to automatically flag technical debt before deployment.

Key capabilities

  • Identifies complex logic blocks and suggests breaking them into smaller functions.
  • Detects missing comments, docstrings, or inline explanations for non-obvious code.
  • Flags inconsistent variable naming, formatting errors, and redundant imports.
  • Highlights potential security vulnerabilities related to poor coding practices.

Example prompts

  • "Review the auth-service module and list three specific areas where the code could be simplified."
  • "Analyze my recent changes in the payment-handler file for missing documentation or unclear variable names."
  • "Scan the entire project for functions exceeding 50 lines of code and suggest refactoring strategies."

Tips & gotchas

This skill focuses on readability and structure rather than functional correctness; ensure your agent tests logic separately. For best results, provide context about your team's specific style guide or coding standards alongside the request.