Skip to content
TrustedSkillsbeta
Back to all skills

Code Quality Auditor

Checked
caomeiyouren·vlatest·backend·MIT

This tool analyzes your backend code for potential issues, boosting reliability and maintainability by identifying bugs & style violations.

Repository

Install on your platform

This skill no longer installs under the name code-quality-auditor. SKILL.md is marked internal, so the skills CLI hides it.

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

Repository install instructions

What we know about this skill

Publisher

caomeiyouren

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 caomeiyouren/momei at 02346816ce.

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

Commit
02346816ce
Manifest
.github/skills/code-quality-auditor/SKILL.md
Scanned
4 files, 393 lines
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

The Code Quality Auditor skill analyzes backend code changes to identify potential issues and ensure adherence to coding standards, security protocols, and testing requirements. It provides a structured review process, generating reports with conclusions (Pass or Reject), problem severity levels (blocker, warning, suggest), and detailed evidence of verification steps taken. The tool helps improve code reliability, maintainability, and overall quality by systematically identifying bugs and style violations across various file types including documentation, configuration files, and agent/skill definitions.

When to use it

  • Before merging code changes into a main branch.
  • During code review processes for new features or bug fixes.
  • To ensure compliance with coding standards and security guidelines.
  • When verifying the quality of documentation, scripts, configuration files, and skill definitions.
  • For release preparation to catch potential issues before deployment.

Key capabilities

  • Contextual Review: Reads git diffs, change file lists, Todo acceptance points, and existing verification results to understand the scope of changes.
  • Minimum Verification Enforcement: Determines minimum validation requirements based on a "Verification Matrix" and enforces necessary commands (e.g., pnpm lint, pnpm typecheck).
  • Structured Assessment: Uses a "Review Checklist" to cover correctness, security, responsibility boundaries, test coverage, and documentation consistency.
  • Evidence Generation & Tracking: Generates evidence records and tracks changes across multiple review rounds.
  • Problem Classification: Categorizes issues as blocker (critical), warning (potential risk), or suggest (improvement).

Example prompts

  • "Analyze the code changes in this git diff for quality issues."
  • "Review these files [list of file paths] and provide a Code Quality Auditor report."
  • “Perform a review gate on my latest commit, ensuring all minimum verification requirements are met.”

Tips & gotchas

  • Prerequisites: The AI agent needs access to the codebase's git repository.
  • Minimum Verification is Key: The skill will reject code that doesn’t meet the defined "Verification Matrix" even if no immediate errors are found.
  • Evidence is Essential: A “Pass” conclusion can only be given when all blocker issues are resolved and minimum verification requirements are met, with clear evidence provided.