devex-review

Audit developer experience by testing onboarding, docs, and CLI flows.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/yckkkk/reo --skill devex-review-yckkkk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/yckkkk/reo/tree/main/.agents/skills/devex-review
Command: npx skills add https://github.com/yckkkk/reo --skill devex-review-yckkkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The DevEx Review DX audit provides a structured way to test and quantify the developer experience of a project or workflow by simulating onboarding, navigating docs, testing CLI flows, and capturing evidence to produce a DX scorecard.

Core Features & Use Cases

  • Onboarding validation: verify getting started flow is clear, fast, and deterministic.
  • DX scoring & evidence: generate a scorecard with timestamps, screenshots, and CLI output for pain points.
  • Documentation and CLI testing: review docs and help text to surface ambiguous or missing guidance.
  • Use case: imagine a new contributor trying to start a local dev environment and running into confusing setup steps; the skill flags friction and suggests improvements.

Quick Start

Run a live DX audit on the current repository and produce a scorecard with evidence.

Frequently Asked Questions about devex-review

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

FAQPage Schema
How do I audit developer experience for new contributors onboarding to a project?

A developer experience audit tests onboarding flows, documentation, and CLI commands to surface friction. It captures timing data, screenshots, and CLI outputs to generate a DX scorecard quantifying the overall experience for new contributors.

What is a DX scorecard and how does it measure onboarding friction?

A DX scorecard measures developer friction by collecting evidence like timestamps, screenshots, and CLI outputs during onboarding. It flags confusing setup steps and ambiguous documentation to quantify the experience and suggest improvements.

How do I test CLI flows and documentation for ambiguous guidance?

You test CLI flows and documentation by running a DX audit that navigates help text and setup instructions. The audit reviews docs to surface ambiguous or missing guidance, capturing CLI outputs as evidence for the scorecard.

Can I measure onboarding time against plan estimates for a local dev environment?

Yes, you can measure onboarding time against plan-devex-review estimates by capturing timing data during a simulated local dev environment setup. The audit compares actual setup times against plan estimates to identify delays and friction.

Does the DX audit require browser access to capture screenshots and timing data?

Yes, the DX audit requires browser and tool access to navigate documentation, capture timing data, and collect screenshots. This access is necessary to simulate user interactions and generate evidence for the scorecard.