Skip to content
TrustedSkillsbeta
Back to all skills

Code Standards

Checked
redpanda-data·vlatest·backend

Enforces consistent coding styles across projects, improving readability and collaboration by automatically suggesting and applying code formatting rules.

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 redpanda-data/console --skill code-standards -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

redpanda-data

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 redpanda-data/console at 0d2c900a21.

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

Commit
0d2c900a21
Manifest
frontend/.claude/skills/code-standards/SKILL.md
Scanned
4 files, 329 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

This skill, Code Standards, helps AI agents write code that is accessible, performant, type-safe, and maintainable. It enforces consistent coding styles across projects by automatically suggesting and applying formatting rules. The tool uses Biome to enforce specific checks like noExplicitAny and the use of top-level regex. It also provides guidance on console logging practices for production code.

When to use it

  • When encountering linting errors that need fixing.
  • To address code formatting issues within a project.
  • During code reviews where style guideline adherence is important.
  • When seeking clarification or examples of coding style guidelines.

Key capabilities

  • Enforces rules defined in the rules/ directory.
  • Uses Biome to enforce specific type safety and regex usage.
  • Provides commands for fixing (bun x ultracite fix), checking (bun x ultracite check), and diagnosing setup issues (bun x ultracite doctor).
  • Offers guidance on appropriate console logging practices, discouraging console.log in production.

Example prompts

  • "Fix the formatting errors in this code."
  • "Check if this component adheres to React functional component standards."
  • "What are the guidelines for using async/await?"

Tips & gotchas

  • Most issues can be automatically fixed with the bun x ultracite fix command.
  • Avoid suppressing console warnings with biome-ignore; instead, remove unnecessary logging statements.
  • Detailed coding style guidance is available in the rules/ directory.