Run commands visible
What a first-developer audit returns.
This sample shows the written DX pass: first-run path, install and docs gaps, proof boundaries, first fixes, and the stop rule for one public repo. It uses public repo metadata and docs only.
Sample only. Real DX audits use the buyer's public repo, docs, public demo, and safe local/test inputs. No private repo access, secrets, credentials, customer data, payment data, account access, or calls.
README characters
Root docs/example dirs
First fixes returned
Executive Summary
Status: red. The repo can be evaluated, but a stranger does not get a clear first-run path, install command, troubleshooting route, or data boundary from the visible docs. Fix those before asking outsiders to trust the demo or contribute.
First Developer Path
| Signal | Observed |
|---|---|
| Visible scripts | build, test, lint, typecheck, dev |
| Docs/examples/demo dirs | None visible at repo root |
| License | Visible |
| Contributing guide | Missing |
DX Findings
- README does not expose a clear first-run path. Fix: add a short quickstart from clone/install to a working example.
- Install command is not obvious. Fix: add the exact install command a stranger should run.
- No docs/examples/demo directory is visible at the repo root. Fix: add a minimal example or demo path.
CONTRIBUTING.mdis missing. Fix: add local development and contribution notes for outside reviewers.- Troubleshooting path is not visible. Fix: add a short troubleshooting or known-limits section.
- Data and secret boundary is not visible. Fix: state what data the tool needs and what should never be sent.
What This Proves
- A stranger can see whether the repo explains what it is, how to install it, how to run it, and how to verify it.
- The audit separates missing proof from subjective taste.
- The output is scoped enough to hand to a maintainer or founder without a meeting.
Generated By
npm run service:dx-demo npm run service:fulfill -- --issue <public-dx-intake> --payment-verified npm run service:delivery-draft -- --report <customer-report> --buyer-email <buyer>