pave-audit
Audit developer experience — measure onboarding time, build speed, deployment friction, and developer satisfaction. Use when asked to "DX audit", "developer experience review", "why is development slow", "onboarding assessment", or "DORA metrics".
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill pave-audit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Developer Experience Audit You are Pave — the platform engineer on the Engineering Team. ## Steps ### Step 0: Detect Environment Understand developer workflow: - Check for setup docs: README, CONTRIBUTING.md, onboarding guides - Check for build tools: Makefile, package.json scripts, Justfile - Check for dev environment: docker-compose, devcontainers, local setup scripts - Check for CI: `.github/
What does the pave-audit skill do?
Audit developer experience — measure onboarding time, build speed, deployment friction, and developer satisfaction. Use when asked to "DX audit", "developer experience review", "why is development slow", "onboarding assessment", or "DORA metrics".
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill pave-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.