devex-review

Quantify developer friction in docs navigation, getting-started flows, and CLI usage.

Updated Apr 16, 2026

Search Tags:#onboarding #evidence #developer-experience #scorecard #cli-help #docs-navigation #dx-audit

Ready to run

npx skills add https://github.com/vib795/copilot-anatomy --skill devex-review-vib795

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/vib795/copilot-anatomy/tree/main/.github/skills/gstack-devex-review
Command: npx skills add https://github.com/vib795/copilot-anatomy --skill devex-review-vib795

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Live developer experience audits identify friction in getting started, navigating docs, and using the CLI, enabling teams to ship faster by pinpointing onboarding gaps.

Core Features & Use Cases

Live DX testing with documentation navigation, getting-started flow checks, and CLI help text evaluation.
Evidence-backed DX scoring that generates a report with actionable recommendations and artifacts.
Use Case: A team onboarding new contributors can run this skill to surface blockers and improve onboarding docs and setup scripts.

Quick Start

Run the devex-review skill to perform a live developer experience audit using the browse tool and report results.

Frequently Asked Questions about devex-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I perform a live developer experience audit on my repository?▼

A live developer experience audit evaluates docs navigation, getting-started flows, and CLI help text to identify and quantify developer friction. It produces a DX scorecard with evidence and actionable recommendations to improve onboarding.

What is a DX scorecard and how does it quantify developer friction?▼

A DX scorecard quantifies developer friction by testing documentation navigation, getting-started flows, and CLI usage. It generates evidence-backed reports with actionable recommendations to surface onboarding gaps and improve the developer experience.

Can I use a DX audit to improve onboarding for new contributors?▼

A DX audit improves onboarding by testing getting-started flows and documentation navigation to surface blockers for new contributors. It generates an evidence-backed scorecard with actionable recommendations to fix onboarding gaps and setup scripts.

How do I evaluate CLI help text and error messages for developer friction?▼

Evaluating CLI help text and error messages involves testing CLI usage during a live DX audit to identify and quantify developer friction. The audit produces evidence-backed reports with actionable recommendations to improve the developer experience.

What's the best way to identify documentation navigation blockers during onboarding?▼

Identifying documentation navigation blockers requires running a live DX audit that tests getting-started flows and docs navigation. It produces a scorecard with evidence and actionable recommendations to pinpoint onboarding gaps and improve the developer experience.