devex-review

Audit developer experience by testing docs, onboarding, CLI help, and error messaging.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/tyhuffman7/gstack-hermes --skill devex-review-tyhuffman7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/tyhuffman7/gstack-hermes/tree/main/gstack-devex-review
Command: npx skills add https://github.com/tyhuffman7/gstack-hermes --skill devex-review-tyhuffman7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Live developer experience audit. Uses the browse tool to actually TEST the developer experience: navigates docs, tries the getting started flow, times TTHW, screenshots error messages, evaluates CLI help text. Produces a DX scorecard with evidence. Compares against /plan-devex-review scores if they exist (the boomerang: plan said 3 minutes, reality says 8). Use when asked to "test the DX", "DX audit", "developer experience test", or "try the onboarding". Proactively suggest after shipping a developer-facing feature. (gstack) Voice triggers (speech-to-text aliases): "dx audit", "test the developer experience", "try the onboarding", "developer experience test".

Core Features & Use Cases

  • Live DX audits across docs, onboarding flows, and CLI usage with evidence collection.
  • DX scorecard generation, benchmarking against plan-devex-review when available.
  • Proactive UX guidance after shipping developer-facing features and roles.

Quick Start

Initiate a live DX audit by navigating docs, starting the getting-started flow, and recording timings, errors, and evidence to produce a DX scorecard.

Frequently Asked Questions about devex-review

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

FAQPage Schema
What is a developer experience audit and what does it evaluate?

Live DX audits measure time to first hello world (TTHW) and collect evidence like screenshots and error messages. They compare actual developer journey timings against planned benchmarks to identify onboarding friction.

How do I test the developer experience of my onboarding flow?

You can test the DX by simulating real journeys across docs and CLI usage, recording timings and screenshots, and comparing the actual results against planned benchmarks to identify onboarding friction.

Can I benchmark live developer experience results against planned targets?

Benchmarking compares actual developer journey timings against planned benchmarks. For example, if a plan estimated three minutes but reality takes eight, the scorecard highlights the variance.

When should I run a developer experience test?

Run a DX audit proactively after shipping developer-facing features and roles to identify friction. It is also used when testing CLI help text, error messaging, and documentation navigation.

Does the developer experience audit work with CLI help text and error messaging?

The audit evaluates CLI help text and error messaging by simulating real developer journeys. It records timings and screenshots to produce a DX scorecard with evidence of these interactions.