devex-review

Audit developer experience by browsing documentation and executing onboarding flows.

12|6|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/shogo-labs/shogo-ai --skill devex-review-shogo-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/shogo-labs/shogo-ai/tree/main/packages/agent-runtime/templates/virtual-engineering-team/.shogo/skills/gstack-devex-review
Command: npx skills add https://github.com/shogo-labs/shogo-ai --skill devex-review-shogo-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines live developer-experience audits to identify onboarding friction, documentation gaps, and CLI usability issues across workflows.

Core Features & Use Cases

  • Live onboarding testing: navigates docs, executes getting-started steps, times flows, and records evidence like screenshots.
  • DX scoring & evidence: produces a DX scorecard with concrete findings and recommended improvements.
  • Cross-scenario applicability: useful for onboarding new features, evaluating docs, and auditing CLI help text.

Quick Start

Ask the AI to run a DX audit by browsing docs, testing onboarding flows, and compiling a DX scorecard.

Frequently Asked Questions about devex-review

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

FAQPage Schema
How do I run a developer experience audit for onboarding flows?

A developer experience audit executes getting-started steps, times onboarding flows, captures screenshots, and compiles findings into a DX scorecard with actionable improvement recommendations.

What is a DX scorecard and how does it evaluate documentation friction?

A DX scorecard aggregates timing data and evidence from live documentation reviews to quantify developer-experience friction, highlighting gaps and usability issues across technical workflows.

Can I test CLI usability and help text during a live DX audit?

Yes, live DX audits apply to CLI usability checks by executing commands, evaluating help text, and recording timing data and evidence to identify command-line interface friction.

What's the best way to identify onboarding friction in developer documentation?

Browsing documentation and executing onboarding flows while collecting timing data and screenshots identifies onboarding friction, producing structured evidence to guide developer-experience improvements.

Does a live DX audit require any specific dependencies or environment setup?

No dependencies are required to run a live DX audit, which independently browses documentation and executes onboarding flows to generate scorecards without external environment setup.