devex-review

Audit live developer onboarding workflows and generate evidence-based DX scorecards.

Updated Jul 21, 2025
One-click install
npx skills add https://github.com/robertzengcn/aiFetchly --skill devex-review-robertzengcn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/robertzengcn/aiFetchly/tree/main/.agents/skills/gstack/devex-review
Command: npx skills add https://github.com/robertzengcn/aiFetchly --skill devex-review-robertzengcn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the blind spot between what teams assume their developer onboarding experience is and what new contributors actually encounter, catching friction points that static documentation reviews miss.

Core Features & Use Cases

  • Live Workflow Testing: Uses the browse tool to navigate your docs and run the actual getting started flow, rather than just reviewing written content.
  • Quantified DX Metrics: Times time-to-hello-world (TTHW), screenshots error messages, and evaluates CLI help text to produce an evidence-based DX scorecard.
  • Plan vs. Reality Comparison: Compares actual onboarding performance against planned /plan-devex-review scores to catch gaps between expected and real user experience.
  • Use Case: Run this after shipping a new developer-facing feature to verify onboarding works as expected, or when new contributors report getting stuck during setup.

Quick Start

Use the devex-review skill to audit the current project's developer onboarding flow and generate a DX scorecard with TTHW metrics and evidence of any friction points.

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 onboarding friction in my project?

To audit developer onboarding friction, you can run live workflow testing that navigates your actual getting started flow rather than just reviewing static documentation. This identifies real friction points new contributors encounter during setup.

Can I measure time-to-hello-world to quantify my developer experience?

You can measure time-to-hello-world to quantify developer experience by running live onboarding tests that time the flow, screenshot error messages, and evaluate CLI help text to produce an evidence-based DX scorecard.

What is the difference between static documentation review and live DX audit?

Live DX audits test actual onboarding workflows by navigating your docs and running the getting started flow, catching friction points that static documentation reviews miss when evaluating planned versus actual developer experience performance.

How do I generate a DX scorecard with evidence of contributor friction?

Generate a DX scorecard with evidence of contributor friction by testing actual onboarding workflows, capturing time-to-hello-world metrics, screenshotting error messages, and evaluating CLI help text to guide documentation improvements.

Does this developer experience audit work for CLI interfaces and APIs?

This developer experience audit applies to projects with developer-facing tools, APIs, or CLI interfaces where onboarding time, error message clarity, and documentation accuracy directly impact contributor retention and productivity.

When should I run a developer experience audit on my project?

Run a developer experience audit after shipping a new developer-facing feature to verify onboarding works as expected, or when new contributors report getting stuck during setup and you need to compare planned versus actual performance.