Bun Audit
- 5 installs
- 5 repo stars
- Updated August 5, 2026
- bjornmelin/dev-skills
bun-audit is a skill that routes to a shared Bun audit engine to scan a repo for Bun-first correctness and apply safe remediations.
About
bun-audit is a router skill over a shared Bun audit/remediation engine. A developer uses it to audit a repo for Bun-first correctness, explain audit findings, list rules, plan safe fixes, apply low-risk remediations, or validate Bun-related changes. It delegates all rule and remediation logic to the bun-dev shared platform and creates rollback artifacts for safe fixes.
- Thin router over a shared Bun audit engine that scans a repo for Bun-first correctness
- Runs audit, explain, list-rules, plan-fixes, apply-safe-fixes, validate, and benchmark commands
- Creates rollback artifacts and stops at plan-fixes when a fix is risky or ambiguous
Bun Audit by the numbers
- 5 all-time installs (skills.sh)
- Ranked #881 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
bun-audit capabilities & compatibility
- Capabilities
- bun dev · code audit · safe remediation · lockfile validation
- Use cases
- code review · refactoring
What bun-audit says it does
Use this skill as a thin router over the shared Bun audit engine in
The shared engine owns audit, fix planning, safe fix application, validate, benchmark, and release-sync.
If a fix is risky or ambiguous, stop at `plan-fixes` and surface the tradeoff.
npx skills add https://github.com/bjornmelin/dev-skills --skill bun-auditAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 5 |
|---|---|
| repo stars | ★ 5 |
| Last updated | August 5, 2026 |
| Repository | bjornmelin/dev-skills ↗ |
What it does
Audit a repository for Bun-first correctness and apply safe, deterministic remediations.
Who is it for?
Auditing a repo for Bun correctness and applying deterministic low-risk fixes.
Skip if: Rewriting Bun rules or remediation logic, which lives in the bun-dev engine.
When should I use this skill?
Auditing a repo for Bun-first correctness, explaining Bun audit findings, planning safe Bun fixes, or validating Bun-related changes.
What you get
A ranked set of Bun findings with safe fix candidates applied and rollback artifacts recorded.
- Bun audit report
- safe fix plan
- applied safe fixes
By the numbers
- 8 commands (audit, explain, list-rules, plan-fixes, apply-safe-fixes, validate, benchmark)
Files
Bun Audit
Use this skill as a thin router over the shared Bun audit engine in ~/.agents/skills/bun-dev/scripts/bun-audit.ts. Do not duplicate rules or remediation logic here.
Commands
audit: runbun ~/.agents/skills/bun-dev/scripts/bun-platform.ts audit --root <repo> --format text.explain <rule-id>: runbun ~/.agents/skills/bun-dev/scripts/bun-platform.ts explain --explain <rule-id>.list-rules: runbun ~/.agents/skills/bun-dev/scripts/bun-platform.ts list-rules.plan-fixes: runbun ~/.agents/skills/bun-dev/scripts/bun-platform.ts plan-fixes --root <repo>.apply-safe-fixes: runbun ~/.agents/skills/bun-dev/scripts/bun-platform.ts apply-safe-fixes --root <repo>.validate: runbun ~/.agents/skills/bun-dev/scripts/bun-platform.ts validate --root <repo> --fail-on warn.benchmark: runbun ~/.agents/skills/bun-dev/scripts/bun-platform.ts benchmark --root <repo>.
Operating Rules
- Treat
bun-devas the source of truth for the engine and rule explanations. - The shared engine owns audit, fix planning, safe fix application, validate,
benchmark, and release-sync.
- Do not run
audit,plan-fixes,apply-safe-fixes,validate,
benchmark, or release-sync in parallel against the same repo root. The shared platform cache uses a single SQLite database under .bun-platform/, and concurrent write access can trigger database is locked.
- By default, creating
.bun-platform/also ensures.bun-platform/is present
in the repo root .gitignore.
- Safe fixes create rollback artifacts under
.bun-platform/rollbacks/. - Keep changes minimal and forward-only.
- If a fix is risky or ambiguous, stop at
plan-fixesand surface the tradeoff.
interface:
display_name: "Bun Audit"
short_description: "Shared Bun audit and safe remediation router"
default_prompt: "Use bun-audit to run the shared bun-dev Bun platform CLI for audit, explain, list-rules, plan-fixes, apply-safe-fixes, validate, and benchmark. Keep bun-dev as the rule source of truth and avoid duplicating engine logic here."
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264kFAQ
Does it apply fixes automatically?
It applies only safe fixes via apply-safe-fixes and stops at plan-fixes when a fix is risky or ambiguous.
Where do rollback artifacts go?
Safe fixes create rollback artifacts under .bun-platform/rollbacks/.