Agent skill

Style Audit

by jiangzhe in jiangzhe/doradb

Audit branch-diff Rust files, or explicitly requested file/directory Rust targets, for Doradb coding style using deterministic tooling and concise read-only review.

Apache-2.0Auto-check passedDevelopment

Install Style Audit

skills CLI
$ npx skills add jiangzhe/doradb --skill style-audit -a claude-code

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

GitHub CLI
$ gh skill install jiangzhe/doradb style-audit --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/jiangzhe/doradb.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/style-audit .claude/skills/style-audit && 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-audit
GitHub stars
121
Token cost
~951 tokens
SKILL.md length
435 words
Files
2
Skills in repo
10
Repo updated
First seen
Licence
Apache-2.0

At a glance

Audit branch-diff Rust files, or explicitly requested file/directory Rust targets, for Doradb coding style using deterministic tooling and concise read-only review.

  • Works in 6 steps: Treat the verifier as authoritative for… → If formatting or clippy fails, stop and… → If verifier diagnostics exist, report a… → …
  • Asked to check coding style
  • SKILL.md covers Required Flow, Report Format and Fallback
  • Calls cargo

What it does

Style Audit is an agent skill from jiangzhe/doradb. Audit branch-diff Rust files, or explicitly requested file/directory Rust targets, for Doradb coding style using deterministic tooling and concise read-only review. Use when asked to check coding style, run a style audit/style auditor, validate task-branch Rust changes during $task-resolve, or report style violations in branch-modified files.

Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development. It works with Rust. The repository describes itself as: DoraDB - Async Rust storage engine. The licence is Apache-2.0.

When your agent uses it

  • Asked to check coding style
  • Run a style audit/style auditor
  • Validate task-branch Rust changes during $task-resolve
  • Report style violations in branch-modified files

Example prompts

  • “/style-audit”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Treat the verifier as authoritative for mechanical checks
  2. If formatting or clippy fails, stop and report that gate failure. Do not continue with manual style review.
  3. If verifier diagnostics exist, report a concise summary grouped by file and rule.
  4. If no branch-diff or forced-path Rust files exist, report that no Rust style audit was needed.
  5. After mechanical gates pass, follow the test-audit skill's
  6. Do not edit files, run cargo fmt, run cargo clippy --fix, stage files, or otherwise mutate tracked repository state.

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • cargo

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

  • Network

    No URLs in SKILL.md.

    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.

Context cost

Style Audit loads about 951 tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 435 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~89
When it runs · the whole SKILL.md, loaded when a task matches
~951

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 jiangzhe/doradb at commit 78c6c3d, republished under its Apache-2.0 licence (© jiangzhe). 435 words, ~951 tokens.

Download SKILL.mdSave it as .claude/skills/style-audit/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
style-audit
description
Audit branch-diff Rust files, or explicitly requested file/directory Rust targets, for Doradb coding style using deterministic tooling and concise read-only review. Use when asked to check coding style, run a style audit/style auditor, validate task-branch Rust changes during $task-resolve, or report style violations in branch-modified files.

Style Audit Workflow

Use this skill to audit current-branch Rust files or explicitly requested Rust file/directory targets without modifying the repository.

Required Flow

  1. Run the deterministic verifier first:
bash
tools/style_audit.rs

Default mode audits working-tree Rust files changed by the current branch against merge-base(origin/main, HEAD) so already committed branch changes are included.

Use --diff-base <rev> only when a different branch base is needed:

bash
tools/style_audit.rs --diff-base <rev>

Use tools/style_audit.rs --force-path <file-or-dir> only when the user explicitly asks to check a specific unstaged file or directory. Directory targets check only direct .rs children and do not recurse.

  1. Treat the verifier as authoritative for mechanical checks:
    • default mode checks branch-diff .rs files against origin/main;
    • --diff-base <rev> working-tree Rust files changed against merge-base(<rev>, HEAD);
    • --force-path working-tree targets when explicitly requested;
    • branch-diff modes run cargo fmt --all -- --check;
    • forced-path mode runs rustfmt --edition 2024 --check <forced files>;
    • cargo clippy --workspace --all-targets -- -D warnings;
    • delegated tools/test_audit.rs check --force-path for exactly the selected files after formatting and Clippy pass; every source-visible test in each file needs literal, nonempty Purpose: and Expected: documentation above other attributes, even when only production code changed;
    • Rust style structure checks.
    • top-level private #[cfg(test)] use imports must move into the #[cfg(test)] module that directly uses them.
  2. If formatting or clippy fails, stop and report that gate failure. Do not continue with manual style review.
  3. If verifier diagnostics exist, report a concise summary grouped by file and rule.
  4. If no branch-diff or forced-path Rust files exist, report that no Rust style audit was needed.
  5. After mechanical gates pass, follow the test-audit skill's Semantic Review for assertions, deterministic setup, and overlapping scenarios. Reuse the exact selected files and source snapshot plus the fresh target/test-audit/ inventory. Start at that review section; do not rerun the auditor or select a new scope.
  6. Do not edit files, run cargo fmt, run cargo clippy --fix, stage files, or otherwise mutate tracked repository state.
Show full SKILL.md (120 more words)Show less

Reports are ignored derived artifacts. Source comments are authoritative; do not edit inventories as approvals. documented means structurally valid only. Child contract violations and extraction/execution errors fail the verifier.

Report Format

Keep the output short:

  • state pass/fail;
  • include the number of Rust files checked and whether they were branch-diff or forced-path targets;
  • list each violation as path:line rule - message;
  • summarize assertion/overlap findings and retained conditional or lifecycle coverage, with actionable source locations;
  • include fmt/clippy command output only when that gate fails, trimmed to the actionable part.

Fallback

If tools/style_audit.rs cannot run because required local tooling is missing, report the tooling failure and inspect branch-diff or explicitly requested Rust files manually only when the user explicitly asks for a best-effort fallback.

© jiangzhe, 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 in .agents/skills/style-audit of jiangzhe/doradb.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 78c6c3d

Compare with similar skills

Style Audit 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 Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Style Audit this skilljiangzhe/doradb121—~951Automated safety check: PassApache-2.0
Migrate Core Code to Submodulestinyhumansai/openhuman42k—~2.6kAutomated safety check: PassGPL-3.0
OpenLogi macOS Permissions TriageAprilNEA/OpenLogi23k—~2.5kAutomated safety check: NotesApache-2.0
Rust Best Practicesfarm-fe/farm5.6k3 repos~1.1kAutomated safety check: PassMIT
RTK Rust Design Patternsrtk-ai/rtk83k—~1.9kAutomated safety check: PassApache-2.0
Release Skillsnexmoe/eve4213 repos~3.3kAutomated safety check: PassNone

Similar skills

  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    42k GitHub stars~2.6k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check: notes
  • Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.

    5.6k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Describes seven Rust design patterns for the RTK CLI filter modules, with when to use each, RTK examples, and notes on when a pattern is overkill.

    83k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Release Skills

    nexmoe/eve

    Universal release workflow. An agent skill from nexmoe/eve.

    421 GitHub starsUsed in 3 repos~3.3k tokens
    DevelopmentAuto-check passed
  • Pnpm Engine

    teambit/bit

    Work on the pnpm Rust engine (@pnpm/napi, the pacquet crates) that bit install runs through.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from jiangzhe/doradb

All 10 skills in this repo
  • Backlog

    jiangzhe/doradb

    Manage backlog todo documents in docs/backlogs with deterministic tooling.

    121 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed
  • Issue Rfc

    jiangzhe/doradb

    Create and list GitHub Issues for Doradb RFC documents with deterministic scripts.

    121 GitHub stars~519 tokensUpdated yesterday
    Auto-check passed
  • Issue Task

    jiangzhe/doradb

    Create and list GitHub Issues for Doradb task documents with deterministic scripts.

    121 GitHub stars~719 tokensUpdated yesterday
    Auto-check passed
  • Rfc Create

    jiangzhe/doradb

    Design and formalize Doradb RFC documents through evidence-gated research, materially different architectural proposals, two review rounds, and explicit draft and formalization approvals.

    121 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Rfc Resolve

    jiangzhe/doradb

    Resolve completed or superseded Doradb RFC programs after implementation tasks, tests, review, and verification are complete.

    121 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed
  • Task Prune

    jiangzhe/doradb

    Inspect and optionally remove completed Doradb task worktrees and their local branches with deterministic safety checks.

    121 GitHub stars~551 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Style Audit

What does Style Audit do?

Audit branch-diff Rust files, or explicitly requested file/directory Rust targets, for Doradb coding style using deterministic tooling and concise read-only review. Style Audit is an agent skill from jiangzhe/doradb. Audit branch-diff Rust files, or explicitly requested file/directory Rust targets, for Doradb coding style using deterministic tooling and concise read-only review.

When should I use Style Audit?

Style Audit fits situations like: asked to check coding style; run a style audit/style auditor; validate task-branch Rust changes during $task-resolve; report style violations in branch-modified files.

How do I install Style Audit in Claude Code?

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

How do I install Style Audit in Codex?

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

Can I use Style Audit 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 jiangzhe/doradb --skill style-audit -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-audit, .gemini/skills/style-audit, .github/skills/style-audit and .opencode/skills/style-audit in your project.

What does Style Audit need to run?

Going by SKILL.md and its folder, Style Audit needs the command-line tools its instructions call (cargo).

Does Style Audit access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Style Audit 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 Audit use?

Style Audit 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 Audit use?

About 951 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Style Audit?

Skills that share tags, products or a category with Style Audit: Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Rust Best Practices (farm-fe/farm, 5.6k stars) and RTK Rust Design Patterns (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Style Audit?

jiangzhe (a GitHub user) maintains it in jiangzhe/doradb, which has 121 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 9, 2026.

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