gs:devex-review

Audit developer experience by navigating documentation and executing onboarding flows.

34|6|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/thanh-abaii/gstack-windows-port --skill gs-devex-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gs:devex-review
Source: https://github.com/thanh-abaii/gstack-windows-port/tree/main/skills/gstack-devex-review
Command: npx skills add https://github.com/thanh-abaii/gstack-windows-port --skill gs-devex-review

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill performs a live developer experience audit, comparing expected vs. actual development workflows, and providing a detailed scorecard.

Core Features & Use Cases

  • Live DX Audit: Tests the developer experience by navigating documentation, executing getting started flows, and capturing error messages.
  • Evidence-Based Scoring: Generates a DX scorecard that includes evidence of the audit.
  • Use Case: After shipping a new feature, use this Skill to ensure the developer experience aligns with expectations and identify areas for improvement.

Quick Start

Run a developer experience audit on the latest feature release.

Frequently Asked Questions about gs:devex-review

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

FAQPage Schema
How do I perform a developer experience audit after shipping a new feature?

A developer experience audit tests your feature release by navigating documentation, executing getting started flows, and capturing error messages to compare actual developer experience against expected outcomes and produce a detailed scorecard.

What is evidence-based scoring for developer experience?

Evidence-based DX scoring generates a scorecard that captures live audit results from navigating onboarding flows and error messages, providing concrete proof of where the developer experience aligns with or fails expected outcomes.

How do I test onboarding flows and capture error messages for code review?

You test onboarding flows by executing getting started steps and capturing error messages during the process, comparing the actual developer experience against expected outcomes to identify areas for improvement in a detailed audit scorecard.

Do I need web browsing and CLI execution to run a developer experience audit?

Yes, a developer experience audit requires web browsing to navigate documentation and CLI execution to run onboarding flows, enabling the tool to capture error messages and generate an evidence-based DX scorecard.

What's the best way to automate developer experience quality assurance for new releases?

Automate developer experience quality assurance by running a live audit that navigates documentation, executes getting started flows, and compares actual results against expected outcomes to generate an evidence-based scorecard for your feature release.

Why does my developer experience scorecard show gaps after a feature release?

Your developer experience scorecard shows gaps because the live audit captured actual error messages and onboarding flow failures, comparing them against expected outcomes to highlight areas where the developer experience needs improvement.