agentleFS
TsukiNi22TsukiNi22/ai-utils/skills/routers/audit/SKILL.md

audit

Skill1 starsChanged 3 days agoMITView on GitHub

Router running the audits of the current project - asks which ones to trigger (checklist - bugs/UB, quality/conventions, dependencies licenses + vulnerabilities, tests coverage, performance - coverage and benchmark checked and run automatically) and the report format, then runs the selected audit skills one after the other and writes a summary report linking them. Invoke manually with /audit.

  • Pipes a download into a shell

193 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, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 174 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the request already names the audits / format, skip what is known.

    line 33

“Common” is measured: kept by at least 6 in 10 of the 174 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

Audit router

Request given with /audit: $ARGUMENTS

Load the skills with the Skill tool (never the other routers: they are manual-only). Never start fork agents; an audit that offers parallel agents asks the user first (its own rule).

1. Context

  • Project root: git rev-parse --show-toplevel (or the current folder outside a repository), languages / build system, git log --oneline -1 (the commit audited).
  • Output folder: audit/ at that root (created if missing), never docs/ unless asked.

2. Ask (one AskUserQuestion call, French questions)

  1. Quels audits lancer ? (multiSelect: true, all checked = recommended):
    • Bugs / UB -> audit-bugs (sanitizers, tests, review; slow on big projects)
    • Sécurité / failles -> audit-security (memory errors, injection, auth, secrets, network...: fixed in passes until a clean one; its report is always a PDF)
    • Propreté / conventions -> audit-quality
    • Dépendances -> audit-deps (licenses to credit / restrictive, known vulnerabilities, transitive)
    • Légal / conformité -> legal-check (GDPR, cookies, legal notice, terms, accessibility, licenses, mentions; its scope global / web asked by it)
    • Couverture des tests -> coverage (C++ with tests: measured with llvm-cov) or tests (other languages)
    • Performance -> benchmark (profiling of the main scenario of the project)
  2. Format du rendu: Markdown + PDF (Recommandé) · PDF seulement · Markdown seulement (passed to every audit, they don't ask again). If the request already names the audits / format, skip what is known. Audit specific questions (ex: audit-bugs scope, mode, iterations, fixes) are asked by that audit when it starts, in one call.

coverage and benchmark are checked by default and run automatically like the others, in audit mode:

  • coverage: measure + uncovered.md + its report only (no test written during an audit: the "fill" part of the skill is proposed in the summary, its end-of-run question is answered by the audit's format choice); skipped with the reason when the project has no tests or no clang / llvm-cov.
  • benchmark: the obvious scenario of the project without asking (the main binary with a typical input found in the README / tests / examples, else the test suite in an optimized build), quick depth (perf + time), report only, no optimization applied; skipped with the reason when nothing can be run (library without benchmark target or tests).

xstyle (when installed: command -v xstyle) is always run with --rtk by the audits (compact output made for the assistant; -o <file>.json for counters kept in a report): audit-quality uses all its rules, audit-bugs the ones that hide bugs. Not installed: say once that curl -fsSL https://tsukini22.github.io/my-universe/install.sh | bash -s then sudo dnf install xstyle (TsukiNi22/xstyle) (no curl: wget -qO- instead of curl -fsSL) would add those checks.

3. Run (in this order, sequentially)

  1. audit-deps first when selected: its JSON (/tmp/deps.json, /tmp/vulns.json) is reused by audit-quality and audit-bugs instead of running the scripts again.
  2. legal-check (reuses the audit-deps JSON for the licenses), 3. audit-quality, 4. tests coverage, 5. benchmark, 6. audit-bugs (the longest, it may fix things only after confirmation), 7. audit-security last (it fixes as it goes and loops until a clean pass: the other reports describe the code before its fixes). Each audit writes its own report audit/<YYYY-MM-DD>-<audit>.{md,pdf} (English unless asked, report style). An audit that fails or can't run (no build system, missing tool) is reported as such, the others continue.

4. Summary report

audit/<YYYY-MM-DD>-summary.{md,pdf} through report: Summary table | Audit | Verdict | High | Medium | Low | Report | (link to each report), the top 10 actions across all the audits (deduplicated, highest gain first), what was not run and why, the commit audited. In the chat: the verdict per audit and the paths only.

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.