agentleFS
HainrixzHainrixz/claude-db/skills/audit/SKILL.md

audit

Skill22 starsChanged 5 months agoMITView on GitHub

Audit a database schema, ORM model, or migrations for design and performance — produces two independent 0-100 scores (Design & Integrity + Performance & Scale) plus a prioritized, evidence-backed report. Read-only; never writes or migrates. Use when the user asks to audit, analyze, review, check, or score a database, schema, data model, migrations, indexes, keys, referential integrity, types, constraints, query patterns, partitioning, or connection pooling — for Postgres, MySQL, Mongo, DynamoDB, Cassandra, pgvector, ClickHouse, Neo4j, and friends.

194 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use delight, teach-impeccable 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.
  • HK-hubSkill

    delight

    Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful. Use when the user asks to add polish, personality, animations, micro-interactions, delight, or make an interface feel fun or memorable.

    Also in 32 projects that use this

  • HK-hubSkill

    teach-impeccable

    One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.

    Also in 19 projects that use this

  • zwy123zwySkill

    normalize

    将用户随意输入的提示词规范化为结构清晰、便于大模型执行的标准化提示词。适用于需要整理、统一提示词格式时调用。

    Also in 19 projects that use this

  • SkillPilotCHSkill

    level-up

    Eine Automatisierung pro Woche finden, scopen, shippen. Output landet als proposed-Eintrag in cadence.md mit konkreten Implementations-Schritten.

    Also in 12 projects that use this

  • ww-w-aiSkill

    pm-discovery

    PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.

    Also in 3 projects that use this

  • +7 more from HK-hub

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 175 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If multiple datastores were detected, the worst-of-across-stores roll-up per axis with the flooring store named, plus the per-store …

    line 20

“Common” is measured: kept by at least 6 in 10 of the 175 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
<!-- Copyright (c) 2026 Enrique Rocha (@soyenriquerocha) · tododeia.com · id er-f37b7121 -->

/claude-db:audit

A full, read-only database audit. Never writes files, never mutates the database — even at Tier 1/2 it runs only read-only verification queries.

$ARGUMENTS = <path|connection-target> [flags]. The target is a repo path (schema/ORM/migration files) and, optionally, a live database via $DATABASE_URL for Tier-1/2 verification. If no target is given and no schema/ORM/migration artifacts are found in the working directory, do not fabricate a pass: say so plainly and suggest /claude-db:start (guided wizard, zero artifacts) or /claude-db:design (greenfield).

What to do

  1. Invoke the db-orchestrator skill with the target and flags. It detects the stack (scripts/detect-stack.mjs — paradigm/engine/ORM/platform), parses the schema (scripts/parse-schema.mjs / parse-orm-python.py), records the data tier reached (0/1/2), dispatches the read-only auditor subagents in parallel, merges findings, and runs db-score.
  2. Present:
    • The two scores — Design & Integrity and Performance & Scale — each with a band (A–F) and a one-line interpretation. Show the uncapped computed alongside any capped:true (a fail+severity:5 on that axis caps it at F). Never blend the two.
    • A per-category breakdown for each score (value, weight, active?), the detected paradigm/engine, the tier reached, and the count of needs_api checks (score confidence — never a silent pass).
    • If multiple datastores were detected, the worst-of-across-stores roll-up per axis with the flooring store named, plus the per-store breakdown.
    • A prioritized action list sorted by impact: each item with status, severity, evidence (evidence.observed quoting real DDL/query with secrets redacted), recommendation, fixability (auto/proposed/advisory), and expected_impact (axis + confidence + magnitude, banded high|medium|low — never a fabricated %/latency/row-count).
  3. End by offering: "Run /claude-db:fix to apply the safe, reversible changes (you confirm each one), /claude-db:migrate to lint a migration, or /claude-db:next to see what to tackle first."

Two scores, never blended. Every finding conforms to schema/finding.schema.json with reproducible evidence. Respond in the user's language (EN/ES).

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.