Agent skill

Style Checker

by noumena-labs in noumena-labs/Sipp

Enforces this monorepo's coding style rules by inspecting git diffs, reading .agents/skills/style-checker/references/styleguidance.md, fixing style violations, and reporting the result.

Apache-2.0Auto-check passedDevelopment

Install Style Checker

skills CLI
$ npx skills add noumena-labs/Sipp --skill style-checker -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install noumena-labs/Sipp style-checker --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/noumena-labs/Sipp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/style-checker .claude/skills/style-checker && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
style-checker
GitHub stars
121
Token cost
~1.4k tokens
SKILL.md length
552 words
Files
2 (incl. references)
Skills in repo
2
Repo updated
First seen
Licence
Apache-2.0

At a glance

Enforces this monorepo's coding style rules by inspecting git diffs, reading .agents/skills/style-checker/references/styleguidance.md, fixing style violations, and reporting the result.

  • Works in 6 steps: Inspect the current changes → Read the style guide → Analyze the diff → …
  • The user asks to check style
  • SKILL.md covers Core Rule, Workflow, Reporting and Constraints
  • Calls git, cargo and npm

What it does

Style Checker is an agent skill from noumena-labs/Sipp. Enforces this monorepo's coding style rules by inspecting git diffs, reading .agents/skills/style-checker/references/styleguidance.md, fixing style violations, and reporting the result. Use when the user asks to check style, review codebase style, clean up a diff, verify coding conventions, or before completing any coding task in this repository.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/style_guidance.md`). Compatibility notes: Designed for coding agents working inside a git monorepo with shell access, file read access, and file editing tools.

It sits in Development, covering Monorepo tooling and Plain language and style rules. It works with Git, Rust, llama.cpp and C++. The repository describes itself as: AI inference, packed simply. A blazing-fast, zero-dependency WebGPU runtime to run GGUF models directly in the browser. Features a symmetric API for seamless local execution and… The licence is Apache-2.0.

When your agent uses it

  • The user asks to check style
  • Review codebase style
  • Clean up a diff
  • Verify coding conventions

Example prompts

  • “Use the style-checker skill to enforce this monorepo's coding style rules by inspecting git diffs, reading…”
  • “/style-checker”

Requirements

  • Compatibility (from SKILL.md): Designed for coding agents working inside a git monorepo with shell access, file read access, and file editing tools.
  • Pre-approved tools (allowed-tools): Bash(git:*), Bash(cargo:*), Bash(npm:*), Bash(pnpm:*), Bash(yarn:*), Read, Edit, MultiEdit

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Inspect the current changes
  2. Read the style guide
  3. Analyze the diff
  4. Fix violations directly
  5. Re-check the diff
  6. Run relevant validation

What it can do on your machine

Read from SKILL.md and the folder at commit 32d5373. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(git:*)
    • Bash(cargo:*)
    • Bash(npm:*)
    • Bash(pnpm:*)
    • Bash(yarn:*)
    • Read
    • Edit
    • MultiEdit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • cargo
    • npm
    • pnpm
    • yarn

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, npm, pnpm and yarn, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for coding agents working inside a git monorepo with shell access, file read access, and file editing tools.

    From compatibility in the SKILL.md frontmatter.

Context cost

Style Checker loads about 1.4k tokens when it runs, and up to ~6.9k if it reads all its reference files. Until then it costs about 91 tokens; SKILL.md has 552 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~91
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from noumena-labs/Sipp at commit 32d5373, republished under its Apache-2.0 licence (© noumena-labs). 552 words, ~1,358 tokens.

Download SKILL.mdSave it as .claude/skills/style-checker/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
style-checker
description
Enforces this monorepo's coding style rules by inspecting git diffs, reading .agents/skills/style-checker/references/style_guidance.md, fixing style violations, and reporting the result. Use when the user asks to check style, review codebase style, clean up a diff, verify coding conventions, or before completing any coding task in this repository.
allowed-tools
Bash(git:*), Bash(cargo:*), Bash(npm:*), Bash(pnpm:*), Bash(yarn:*), Read, Edit, MultiEdit
compatibility
Designed for coding agents working inside a git monorepo with shell access, file read access, and file editing tools.

Style Checker

You are an expert code reviewer enforcing this monorepo's local style rules.

Run this skill when asked to check style, review coding conventions, clean up a diff, or before finishing any coding task in this repository.

Core Rule

Always review the changed code against the repository's canonical style guide:

text
.agents/skills/style-checker/references/style_guidance.md

That file is the source of truth. If these instructions conflict with .agents/skills/style-checker/references/style_guidance.md, follow .agents/skills/style-checker/references/style_guidance.md.

Workflow

1. Inspect the current changes

Determine what changed before reviewing style.

Run the narrowest useful git commands, typically:

bash
git status --short
git diff
git diff --cached

Review only changed files and changed lines unless the style guide requires broader context.

Do not perform unrelated cleanup.

2. Read the style guide

Read:

text
.agents/skills/style-checker/references/style_guidance.md

Use it to evaluate the diff. Do not rely only on general language or framework conventions.

3. Analyze the diff

Compare the changed code against .agents/skills/style-checker/references/style_guidance.md.

Pay special attention to these monorepo expectations.

Rust

Check changed Rust code for:

  • Custom library error types, preferably using thiserror, where typed errors are appropriate.
  • No naked unwrap() or expect() in production paths.
  • Intentional error handling or propagation for fallible operations.
  • Appropriate //! or /// documentation for public modules, public types, and important public functions.
  • Consistency with nearby crate conventions for errors, logging, async behavior, and public APIs.
TypeScript

Check changed TypeScript code for:

  • NodeNext-compatible relative imports with explicit .js extensions where required.
  • readonly arrays, tuples, and object shapes where immutability is intended or required by project convention.
  • No newly introduced implicit any.
  • Explicit types at module boundaries and public APIs.
  • No weakening of strictness, type safety, or existing lint expectations.
4. Fix violations directly

If you find a style violation, edit the affected file immediately.

Use the smallest safe fix. Prefer targeted edits over broad rewrites.

Good fixes include:

  • Replacing unwrap() with proper error propagation.
  • Adding or refining a typed error enum.
  • Adding missing .js extensions to TypeScript relative imports.
  • Adding readonly where required.
  • Adding public documentation required by the style guide.
  • Tightening an implicit or overly broad type.

Avoid:

  • Reformatting unrelated code.
  • Renaming symbols for preference only.
  • Refactoring outside the changed area.
  • Applying generic best practices that are not supported by the repo guidance.
Show full SKILL.md (202 more words)Show less
5. Re-check the diff

After editing, inspect the diff again.

Confirm that:

  • The style issue is fixed.
  • The edit is minimal.
  • No unrelated changes were introduced.
  • The code still follows nearby patterns.
6. Run relevant validation

When practical, run the narrowest relevant validation command for the changed files.

Prefer project-specific commands from package scripts, justfiles, makefiles, cargo configs, or repo documentation.

Possible commands include:

bash
cargo fmt
cargo clippy
cargo test
npm run typecheck
npm run lint
npm test
pnpm typecheck
pnpm lint
pnpm test
yarn typecheck
yarn lint
yarn test

Do not run expensive full-repo checks when a narrower check is available.

If validation cannot be run, explain why.

Reporting

At the end, report clearly and briefly.

Include:

  • Whether the style check passed.
  • What style issues were found.
  • What files were changed.
  • What validation commands were run.
  • Any validation that could not be run.

If no issues were found, say exactly:

text
Style check passed; no changes were needed.

If fixes were made, summarize them in plain language.

Example:

text
Style check completed. I fixed two TypeScript style issues in lib/web/src/client.ts: added NodeNext .js import extensions and made the exported config map readonly. I ran pnpm typecheck and it passed.

Constraints

  • Always read .agents/skills/style-checker/references/style_guidance.md before enforcing style.
  • Review the diff, not the whole repository.
  • Fix style violations directly when safe.
  • Keep changes minimal and local to the relevant diff.
  • Do not invent new conventions.
  • Do not ignore the style check before completing coding work.
  • If .agents/skills/style-checker/references/style_guidance.md is missing, report that the canonical style guide could not be found and apply only conservative checks based on nearby code.

© noumena-labs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .agents/skills/style-checker of noumena-labs/Sipp.

  • SKILL.md
  • references/style_guidance.md

Open the folder on GitHubat commit 32d5373

Compare with similar skills

Style Checker next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Style Checker compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Style Checker this skillnoumena-labs/Sipp121—~1.4kAutomated safety check: PassApache-2.0
Run Testsayutaz/piper-plus234—~641Automated safety check: PassMIT
Code RefinerMathews-Tom/armory329—~3.1kAutomated safety check: PassMIT
Check Loanwordayutaz/piper-plus234—~1.1kAutomated safety check: PassMIT
Precheckayutaz/piper-plus234—~647Automated safety check: PassMIT
Check Toolsoaustegard/claude-skills150—~641Automated safety check: PassMIT

Similar skills

  • Run Tests

    ayutaz/piper-plus

    piper-plus の各言語ランタイムのテストを実行します。引数 python/rust/cs/go/js/cpp/all で対象を選択。未指定なら git diff から自動判定。

    234 GitHub stars~641 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Code Refiner

    Mathews-Tom/armory

    Deep code simplification and refactoring preserving behavior across Python, Go, TypeScript, Rust.

    329 GitHub stars~3.1k tokensUpdated 5 days ago
    DevelopmentAuto-check passed
  • Check Loanword

    ayutaz/piper-plus

    ZH-EN code-switching loanword の同期と forward-compat を 1 コマンドで検査。zhenloanword.json を編集したり 5 ランタイムのいずれかに新規エントリを追加する前後に呼ぶ。Python source を canonical とし、Rust×2 / Go / C / WASM / C++ の 6 mirror + Python…

    234 GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Precheck

    ayutaz/piper-plus

    PR 作成前の lint + format + test 一括実行。引数で scope (python/rust/cs/go/js/cpp/all) を指定可能。未指定なら git diff から自動判定。

    234 GitHub stars~647 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Check Tools

    oaustegard/claude-skills

    Validates development tool installations across Python, Node.js, Java, Go, Rust, C/C++, Git, and system utilities.

    150 GitHub stars~641 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Crossbind

    crossbind/crossbind

    A skill your agent uses when a user wants to call C++ or Rust from JavaScript or TypeScript; add a native library such as GDAL, SQLite, OpenSSL, GEOS or PROJ to a browser, Node.js, Cloudflare Worker…

    148 GitHub stars~1.1k tokensUpdated today
    MobileAuto-check passed

More from noumena-labs/Sipp

  • Test Runner

    noumena-labs/Sipp

    Runs the narrowest relevant tests to validate changes. An agent skill from noumena-labs/Sipp.

    121 GitHub stars~854 tokensUpdated 21 days ago
    Auto-check passed

Categories

Questions about Style Checker

What does Style Checker do?

Enforces this monorepo's coding style rules by inspecting git diffs, reading .agents/skills/style-checker/references/styleguidance.md, fixing style violations, and reporting the result. Style Checker is an agent skill from noumena-labs/Sipp.md, fixing style violations, and reporting the result.

When should I use Style Checker?

Style Checker fits situations like: the user asks to check style; review codebase style; clean up a diff; verify coding conventions.

How do I install Style Checker in Claude Code?

Run `npx skills add noumena-labs/Sipp --skill style-checker -a claude-code`. Or copy the skill folder (.agents/skills/style-checker in noumena-labs/Sipp) into .claude/skills/style-checker in your project. Claude Code loads it when a task matches its description.

How do I install Style Checker in Codex?

Run `npx skills add noumena-labs/Sipp --skill style-checker -a codex`. Or copy the skill folder (.agents/skills/style-checker in noumena-labs/Sipp) into .agents/skills/style-checker in your project. Codex loads it when a task matches its description.

Can I use Style Checker in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add noumena-labs/Sipp --skill style-checker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/style-checker, .gemini/skills/style-checker, .github/skills/style-checker and .opencode/skills/style-checker in your project.

What does Style Checker need to run?

Going by SKILL.md and its folder, Style Checker needs the command-line tools its instructions call (git, cargo, npm, pnpm and yarn). Its frontmatter pre-approves these tools: Bash(git:*), Bash(cargo:*), Bash(npm:*), Bash(pnpm:*), Bash(yarn:*), Read, Edit, MultiEdit. Compatibility (from SKILL.md): Designed for coding agents working inside a git monorepo with shell access, file read access, and file editing tools..

Does Style Checker access the network?

SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Style Checker safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Style Checker use?

Style Checker is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Style Checker use?

About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.5k tokens, read only when the agent opens those files.

What are the alternatives to Style Checker?

Skills that share tags, products or a category with Style Checker: Run Tests (ayutaz/piper-plus, 234 stars), Code Refiner (Mathews-Tom/armory, 329 stars), Check Loanword (ayutaz/piper-plus, 234 stars) and Precheck (ayutaz/piper-plus, 234 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Style Checker?

noumena-labs (a GitHub organization) maintains it in noumena-labs/Sipp, which has 121 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 19, 2026.

Source: noumena-labs/Sipp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.