devex-review

Audit developer onboarding by navigating documentation and testing CLI workflows.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/yocxy2/gstack3 --skill devex-review-yocxy2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/yocxy2/gstack3/tree/main/devex-review
Command: npx skills add https://github.com/yocxy2/gstack3 --skill devex-review-yocxy2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the gap between documented developer onboarding and the actual, lived experience of a new engineer by performing a real-time, automated audit of your project's developer journey.

Core Features & Use Cases

  • Live DX Audit: Navigates documentation, executes getting-started flows, and measures time-to-hello-world (TTHW) to provide an objective performance score.
  • Evidence Collection: Automatically captures screenshots of error messages and evaluates CLI help text for clarity and accuracy.
  • Use Case: Use this skill after shipping a new developer-facing feature to ensure the onboarding flow remains frictionless and that your documentation matches the current state of the codebase.

Quick Start

Invoke the devex-review skill to perform a full audit of the current developer onboarding flow and generate a scorecard.

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 workflows and measure time-to-hello-world?

To audit developer onboarding workflows, you can execute a live review that navigates documentation and runs getting-started flows to measure time-to-hello-world (TTHW) and generate an evidence-based scorecard.

What is a live developer experience audit and how does it evaluate documentation accuracy?

A live developer experience audit evaluates documentation accuracy by executing shell commands and browser navigation to validate that your getting-started flows match the current codebase state.

Can I use this skill to capture evidence of CLI usability issues during onboarding?

Yes, you can use this skill to capture evidence of CLI usability issues by automatically taking screenshots of error messages and evaluating CLI help text for clarity during the onboarding workflow.

Do I need browser and shell execution capabilities to run a developer experience review?

Yes, you need browser access and shell execution capabilities to run a developer experience review, as the skill requires executing commands and navigating project environments to validate developer-facing features.

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

You should run a developer experience audit after shipping a new developer-facing feature to ensure the onboarding flow remains frictionless and that your documentation matches the current state of the codebase.

What is the best way to generate a scorecard for developer experience friction?

The best way to generate a scorecard for developer experience friction is to perform an automated audit that navigates documentation, evaluates CLI usability, and captures evidence of errors to objectively score the onboarding journey.