devex-review

Audit developer onboarding and CLI help text to produce a DX scorecard.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gfires/motion-analysis --skill devex-review-gfires
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/gfires/motion-analysis/tree/main/devex-review
Command: npx skills add https://github.com/gfires/motion-analysis --skill devex-review-gfires

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Removes guesswork from developer experience assessments by performing a hands-on DX audit across docs, onboarding flows, and CLI help to surface friction points.

Core Features & Use Cases

  • Hands-on DX testing: Uses the browse tool to navigate docs, validate getting started flows, and collect evidence of bottlenecks.
  • DX scoring: Produces a DX scorecard with concrete evidence and recommended improvements.
  • Comparative analysis: Compares results against existing /plan-devex-review scores when they exist to quantify gaps.

Quick Start

Describe your DX test scenario to Claude, then trigger the audit with the /qa command.

Frequently Asked Questions about devex-review

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

FAQPage Schema
How do I conduct a developer experience audit for my CLI tool?

A DX audit measures onboarding friction by performing a live browser-based exploration of docs and CLI help text, timestamping setup steps, and capturing errors to generate a scorecard with concrete improvement recommendations.

What is developer experience onboarding friction and how is it measured?

Onboarding friction is measured by performing hands-on browser exploration of docs and CLI checks, capturing error messages and setup timestamps, and comparing results against existing plan scores to quantify gaps.

Can I evaluate CLI help text and getting started flows automatically?

Yes, the DX audit performs live browser-based exploration and CLI checks to evaluate help text and getting started flows, producing a scorecard with concrete evidence and recommended improvements.

How do I compare live DX audit results against existing plan scores?

The audit automatically compares live browser-based exploration and CLI check results against existing plan-devex-review scores when they exist, quantifying gaps and surfacing concrete recommendations.

What do I need to provide to start a developer experience audit?

You need to describe your DX test scenario and trigger the audit with the qa command, which then performs live browser-based exploration and CLI checks to generate a scorecard with concrete evidence.