devex-review

Automate live testing of developer workflows to produce a DX scorecard.

2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/esopian/blue-oak-audit --skill devex-review-esopian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/esopian/blue-oak-audit/tree/main/.claude/skills/gstack/devex-review
Command: npx skills add https://github.com/esopian/blue-oak-audit --skill devex-review-esopian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the process of testing and auditing the developer experience for software projects, saving time and identifying pain points early.

Core Features & Use Cases

  • Active Developer Experience Testing: Navigates documentation, runs onboarding flows, and evaluates the speed of key developer tasks.
  • Evidence Collection: Takes screenshots, records error messages, and analyzes CLI help to generate a comprehensive DX scorecard.
  • Use Case: When a team ships a new feature, use this Skill to assess if onboarding and documentation still meet developer needs and identify areas for improvement.

Quick Start

Test the developer experience of your project by invoking the gstack tool and asking it to audit onboarding and docs.

Frequently Asked Questions about devex-review

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

FAQPage Schema
How do I automate developer experience testing for onboarding and documentation?

Automating developer experience testing involves running live onboarding flows, navigating documentation, and evaluating CLI usability to identify pain points. This Skill captures screenshots and logs errors to generate a DX scorecard.

What does a developer experience audit measure?

A developer experience audit measures the speed and usability of key onboarding tasks, documentation clarity, and CLI help effectiveness. It collects evidence like error messages and screenshots to quantify friction in developer workflows.

How do I find onboarding friction in my project's documentation?

Finding onboarding friction requires actively navigating your documentation and running setup flows to detect errors. This process records CLI issues and missing steps, producing a scorecard that highlights areas for improvement.

Can I evaluate CLI usability as part of a developer experience review?

Evaluating CLI usability is a core part of a developer experience review. This involves analyzing CLI help outputs, logging command errors during onboarding, and assessing task completion speed to calculate overall usability.

When should I run a developer experience audit in my release cycle?

Run a developer experience audit during your project release cycle when shipping new features. This verifies that updated onboarding flows and documentation still meet developer needs and identifies friction points early.

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

Generating a developer experience scorecard requires automating live testing of developer workflows, capturing screenshots, and analyzing CLI help. This consolidates error logs and task speed metrics into a comprehensive report.