gsp-doctor

Analyze GSP project .design directory for structural and configuration drift.

49|4|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jubscodes/get-shit-pretty --skill gsp-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsp-doctor
Source: https://github.com/jubscodes/get-shit-pretty/tree/main/gsp/skills/gsp-doctor
Command: npx skills add https://github.com/jubscodes/get-shit-pretty --skill gsp-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GSP design projects can accumulate configuration drift, missing files, and phase mismatches, making it hard to determine if the project is ready for production. This skill provides an instant, read‑only diagnostic of the entire .design workspace.

Core Features & Use Cases

  • Structural validation: Ensures required files and directories exist for each brand and project.
  • Phase ordering checks: Detects out‑of‑order or incomplete phases across the dual‑diamond workflow.
  • Drift detection: Identifies brand, config, and stack drift, as well as stale outputs.
  • Upgrade & legacy warnings: Flags legacy structures, missing palettes, and version mismatches.
  • Installation health: Verifies skill invocability, bundle directories, VERSION file, and duplicate installations.
  • Use case: Quickly assess a newly cloned GSP repository before starting development, or run in CI to ensure health before deployment.

Quick Start

Run the gsp-doctor skill to receive a full health report of the current GSP project.

Frequently Asked Questions about gsp-doctor

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

FAQPage Schema
What is design system drift detection and how does it validate project structure?

Design system drift detection works by performing deterministic pattern matching across the .design directory using Read, Glob, Grep, and Bash tools to identify configuration, brand, and stack drift without modifying files.

Does the GSP project validation check work for newly cloned repositories in a CI pipeline?

Yes, you can validate a GSP repository before deployment by running a comprehensive health check that identifies missing assets, stale outputs, phase ordering issues, and structural mismatches across the dual-diamond workflow.

What is the best way to verify installation health and skill invocability for a design system CLI?

To find legacy structures and version mismatches in a design system workspace, run a diagnostic health check that flags missing palettes, legacy directory structures, and version discrepancies within the .design directory.

How do I find legacy structures and version mismatches in my design system workspace?

Verifying installation health for a design system CLI involves checking bundle directories, the VERSION file, skill invocability, and duplicate installations to ensure the project environment is correctly configured.