← ClaudeAtlas

dx-auditlisted

Audit and improve developer experience in a codebase by inspecting README, quickstart, scripts, contributing guide, env docs, error messages, and tooling, scoring onboarding friction, and reporting findings or implementing fixes. Use when a new contributor hits friction, when setup is undocumented, or when the README has not been run on a clean checkout since the stack changed.
HermeticOrmus/dx-audit-skills · ★ 0 · Code & Development · score 75
Install: claude install-skill HermeticOrmus/dx-audit-skills
# DX audit A protocol for auditing and improving developer experience in a codebase. Developer experience is everything a contributor touches before their first useful line of code. High onboarding friction is silent: no one files a bug for it, every new contributor just pays the cost. ## Usage ```text /dx-audit # full audit of the current project (report-only) /dx-audit [path] # audit a specific directory /dx-audit --report-only # inspect and report, change nothing (default) /dx-audit --implement # apply fixes with approval, verify each ``` ## What to inspect Walk the codebase as a new contributor would. For each dimension, record what exists, what is missing, and whether what exists is accurate. 1. README: first-paragraph clarity, a copy-pasteable quickstart, current commands, links to deeper docs. 2. Quickstart and setup: the path from clone to running app, in dependency order, with prerequisites listed. Run it on a clean checkout and count what fails. 3. Scripts: install / dev / build / test / lint / format entries in a task runner, with names that match the README and contributing guide. 4. Contributing guide: branch naming, commit format, PR expectations, how to run tests, checked against the actual workflow. 5. Environment docs: an `.env.example` listing every required variable, each annotated with what it is and where to get it. 6. Error messages: setup scripts fail loudly with actionable messages, so missing deps, wrong runtime ve