Skip to content
TrustedSkillsbeta
Back to all skills

Codebelt Code Style

Checked
codebelt·vlatest·writing

Codebelt Code Style automatically formats your code to adhere to a defined style guide, improving readability and collaboration.

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 codebelt/codebelt-skills --skill codebelt-code-style -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

codebelt

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 codebelt/codebelt-skills at 491fb6075e.

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

Scanned
7 files, 1,207 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 codebelt-code-style skill enforces consistent coding style within a codebase. It analyzes code for adherence to specified rules and suggests or automatically applies corrections. This ensures readability, maintainability, and collaboration efficiency across development teams.

When to use it

  • Code reviews: Automatically check pull requests for style violations before human review.
  • Team onboarding: Quickly standardize the coding style of new team members’ contributions.
  • Refactoring large codebases: Ensure consistent formatting during significant changes.
  • Automated builds: Integrate into CI/CD pipelines to prevent style-related build failures.

Key capabilities

  • Code analysis for style violations
  • Suggestion of corrections
  • Automatic application of fixes (potentially)
  • Support for various programming languages (unspecified in source)

Example prompts

  • "Check this code snippet for PEP 8 compliance."
  • "Apply the Google C++ Style Guide to this file."
  • "Find all instances where variable names don't follow the camelCase convention."

Tips & gotchas

The skill’s effectiveness depends on a clearly defined and agreed-upon coding style guide. Automatic fixes should be carefully reviewed, especially when first implementing the skill, to avoid unintended consequences.