gql:doctor

Diagnose soda-gql project misconfigurations, version mismatches, and stale generated artifacts.

1|1|Updated Sep 6, 2025

Search Tags:#typescript #quality #diagnostics #codegen #gql #doctor #soda-gql

Ready to run

npx skills add https://github.com/whatasoda/soda-gql --skill gql-doctor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gql:doctor
Source: https://github.com/whatasoda/soda-gql/tree/main/claude-code-plugin/skills/gql-doctor
Command: npx skills add https://github.com/whatasoda/soda-gql --skill gql-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The GraphQL Doctor skill provides a structured, end-to-end diagnostic workflow for soda-gql projects, surfacing configuration issues, version mismatches, and stale generated files to keep your GraphQL tooling healthy.

Core Features & Use Cases

Detects project configuration and setup for soda-gql, including presence of soda-gql.config.{ts,js,mjs}.
Runs core diagnostics (version-consistency, duplicate-packages, config-validation, codegen-freshness) and extended checks (template validation, type-check, formatting) with actionable fixes.
Useful for CI pipelines, pre-commit checks, and new project onboarding to ensure a healthy development environment.

Quick Start

Run bun run soda-gql doctor in your project to begin diagnostics.

Frequently Asked Questions about gql:doctor

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

FAQPage Schema

How do I run diagnostics to detect stale generated artifacts in a GraphQL codegen project?▼

To run GraphQL codegen diagnostics, execute the doctor workflow using bun. It analyzes project structure, checks codegen-freshness, and reports actionable fixes for stale generated artifacts in your soda-gql project.

What configuration issues can a GraphQL project doctor workflow identify?▼

A GraphQL project doctor identifies misconfigurations, version mismatches, and duplicate packages. It performs config-validation and version-consistency checks across typical soda-gql setups to surface actionable fixes for a healthy development environment.

Do I need bun and a specific config file to execute soda-gql diagnostics?▼

Yes, executing soda-gql diagnostics requires access to bun to run the workflow and a valid soda-gql.config.{ts,js,mjs} file. These prerequisites allow the tool to analyze project structure and run core checks.

Can I use GraphQL project diagnostics for CI pipelines and pre-commit checks?▼

Yes, you can use GraphQL project diagnostics for CI pipelines and pre-commit checks. Running the doctor workflow ensures version-consistency and config-validation, keeping your GraphQL tooling healthy during new project onboarding.

What is the best way to validate templates and check type formatting in a soda-gql project?▼

The best way to validate templates and check type formatting is running extended diagnostics via bun. The doctor workflow performs template validation, type-check, and formatting checks alongside core codegen-freshness verifications.

Why does my GraphQL codegen doctor workflow report version mismatches and duplicate packages?▼

A GraphQL codegen doctor reports version mismatches and duplicate packages to maintain tooling health. It executes version-consistency and duplicate-packages checks across your soda-gql project, providing actionable fixes to resolve detected anomalies.