agentleFS
Sign inStart free
LucaDominiciLucaDominici/arbiter/.claude/skills/codebase-audit/SKILL.md

codebase-audit

Skill0 starsChanged 54 days agoApache-2.0View on GitHub

Use when running a comprehensive codebase verification. Dispatches parallel agents across disjoint scopes to check invariant compliance, dead code, test coverage gaps, and naming consistency.

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use cloud-api-recipe-authoring, codebuddy-ide-mcp-upgrade and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • TencentCloudBaseSkill

    cloud-api-recipe-authoring

    Author or revise a cloud-api-operations recipe (config/source/skills/cloud-api-operations/references/recipes/). Encodes why the long tail of control-plane capabilities is deliberately NOT wrapped as MCP/CLI tools, the API-first admission test for whether a capability deserves a recipe, the negative and positive lists, the fixed recipe structure, the writing rules distilled from writing-for-agents, the user-facing copy red lines, and the product regeneration/verification pipeline. Also routes contributors (and their agents) to the contribution flow and the pre-PR self-test protocol in references/contributing.md. Use when adding a recipe, judging whether a scenario belongs in the recipe set, updating the recipes index, re-checking existing recipes against the admission test, or onboarding someone who wants to submit one.

    Also in 3 projects that use this

  • TencentCloudBaseSkill

    codebuddy-ide-mcp-upgrade

    升级 CodeBuddy IDE（genie 扩展）内置的 CloudBase MCP，以及 MCP 发版时同步 IDE 侧白名单。当用户提到「更新 IDE 里的 MCP」「内置 MCP 版本太老」「IDE 集成的 CloudBase 功能不足」「改工具白名单 toolWhiteList」「把新 bundle 打进 CodeBuddy」「白名单漂移」「MCP 发版要同步什么」时使用。覆盖：解包定位内置 bundle 与内嵌配置、重新构建 mcp bundle、生成新的工具白名单与系统提示词、安全注入 IDE 并备份、用 MCP 协议验证工具清单、人工端到端验收、一键回滚。

    Also in 3 projects that use this

  • frostneySkill

    native-nostalgia-stack

    Applies the user's FreePascal toolchain and its build, formatting, hook, and test contracts while leaving project-specific mechanics local. Use when scaffolding or working in a FreePascal project that follows this toolchain.

    Also in 3 projects that use this

  • frostneySkill

    software-engineering-excellence

    Applies the user's engineering standards during substantial technical work: preserve scope, use current evidence, delegate independent parts, and complete authorized outcomes. Use during substantial implementation, debugging, refactoring, or multi-part delivery work.

    Also in 3 projects that use this

  • withpiperSkill

    roadmap-review

    Audit roadmap health — issues, dependency order, spec coverage, doc freshness. Use when speccing a new initiative. Use when /phase-plan output looks suspicious. Use before /roadmap-create reruns.

    Also in 3 projects that use this

  • zaxbysauceSkill

    pr-review-fix

    Codex adapter for addressing pull request review feedback in opencode-swarm. Use when the user asks to fix PR review comments, requested changes, reviewer findings, CI-review notes, or a pasted review summary with low false-positive tolerance.

    Also in 3 projects that use this

  • +6 more from TencentCloudBase

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 28 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before a major release

    line 20
  2. Distinctive:

    After a large refactor

    line 21
  3. Distinctive:

    Run scopes in parallel when possible.

    line 46
  4. Distinctive:

    Read-only. No edits during audit.

    line 85
  5. Distinctive:

    Do not fix issues inline — create task briefs for fixes.

    line 86
  6. Very specific:

    When the requested scope is product-complete, code-quality lanes are only inputs.

    line 90
  7. Very specific:

    Use FEATURE_MATRIX IDs for SUPPORTED rows.

    line 111
  8. Very specific:

    Every FEATURE_MATRIX capability must appear exactly once.

    line 113

“Common” is measured: kept by at least 6 in 10 of the 28 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Codebase Audit

Purpose: Systematic whole-codebase verification using parallel read-only agents.

When to Use

  • Before a major release
  • After a large refactor
  • Periodic health checks
  • Onboarding to an unfamiliar codebase

Audit Scopes

Divide the codebase into disjoint scopes and delegate each to a codebase-scanner agent:

ScopeWhat to Check
Dead codeUnused exports, unreachable functions, commented-out blocks
Naming consistencyConventions followed (camelCase, snake_case per layer)
Test coverage gapsSource files without a corresponding test file
Error handlingUnchecked errors, swallowed exceptions, missing fallbacks
Type safetyany usage, missing return types on public functions

Execution

For each scope, delegate to codebase-scanner:

Delegate to codebase-scanner:
  "Find all <scope> issues in src/"

Run scopes in parallel when possible.

Output Format

## Codebase Audit Report

**Date:** <date>
**Scope:** Full / Partial (<modules>)

### Dead Code

- <file:line — description>

### Naming Inconsistencies

- <file:line — convention violated>

### Test Coverage Gaps

- <source file without test>

### Error Handling Gaps

- <file:line — description>

### Type Safety Issues

- <file:line — description>

### Summary

- Total issues found: <N>
- Critical: <N>
- Recommended actions: <list>

Constraints

  • Read-only. No edits during audit.
  • Do not fix issues inline — create task briefs for fixes.

Product-complete mode

When the requested scope is product-complete, code-quality lanes are only inputs. Freeze the subject SHA, inventory every in-scope public/emitted entrypoint, then add this metadata and marked table to the report:

<!-- PRODUCT_AUDIT
scope: product-complete
subject_sha: <40-char SHA>
entrypoint_denominator: <count derived from rows>
readiness_verdict: PASS|FAIL|NO_DATA|N/A
docs_verdict: PASS|FAIL|NO_DATA|N/A
behavior_verdict: PASS|FAIL|NO_DATA|N/A
-->
<!-- PRODUCT_COVERAGE_START -->

| capability_id | classification | entrypoints | owner | config | proof | external_overlap | coverage | verdict |
| ------------- | -------------- | ----------- | ----- | ------ | ----- | ---------------- | -------- | ------- |

<!-- PRODUCT_COVERAGE_END -->

Use FEATURE_MATRIX IDs for SUPPORTED rows; use capability N/A only for INTERNAL or RETIRED. Coverage is VERIFIED, SOURCE_TRACED, SAMPLED, NEEDS_REVALIDATION, UNCOVERED, or N/A. Every FEATURE_MATRIX capability must appear exactly once. A VERIFIED row's proof must be its .arbiter/evidence/rtm/<REQ-NNN>.json envelope with verdict PROVEN and subject_sha equal to the report's frozen subject; prose and authored transcripts are not proof. Validate the completed report with:

node scripts/check-feature-matrix.mjs --product-report <report.md>

Counts come from rows. Presence, markers, authored transcripts, and historical evidence cannot produce a behavior PASS.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free