doctor

Audit pipeline configuration, GitHub auth, labels, and plugin registration for install health.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/rjskene/pipeline --skill doctor-rjskene
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doctor
Source: https://github.com/rjskene/pipeline/tree/main/skills/doctor
Command: npx skills add https://github.com/rjskene/pipeline --skill doctor-rjskene

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

Prevents broken or partially migrated pipeline installations by auditing your repo’s configuration, GitHub access, plugin registration, and residual legacy files before you run any automation.

Core Features & Use Cases

  • Read-only install validation: checks pipeline.config, gh availability/auth, GitHub repo reachability, plugin root resolution, label presence, and base-branch enforcement wiring.
  • Residual migration detection: flags retired subtree artifacts and legacy .claude / CLAUDE.md / hook-skill/script collisions that could cause incorrect behavior.
  • Safety-focused diagnostics: surfaces drift severity (including an escalation path for active configuration bugs) and provides remediation guidance, with optional idempotent fixes for labels.

Quick Start

Run /pipeline:doctor to audit your current consumer install state and see a summary of any failures or warnings.

Frequently Asked Questions about doctor

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

FAQPage Schema
How do I validate my GitHub pipeline configuration after a migration?

Validate your GitHub pipeline configuration by running read-only install health checks that audit pipeline.config, GitHub auth, plugin registration, and legacy residuals to ensure deterministic discovery before running automation.

Why does my CI automation fail when processing GitHub issues?

CI automation processing GitHub issues can fail due to broken pipeline installations, missing labels, or residual legacy files like retired subtree artifacts. Run diagnostic checks to surface drift severity and identify configuration bugs.

How do I check if my GitHub repository has residual legacy files affecting my pipeline?

Check for residual legacy files by auditing your repository for retired subtree artifacts and legacy .claude or CLAUDE.md collisions that could cause incorrect behavior during pipeline execution.

Can I automatically fix missing GitHub labels during a pipeline configuration audit?

You can automatically fix missing GitHub labels during a pipeline configuration audit by running the doctor checks with the --fix labels flag, which applies idempotent fixes to ensure label enforcement.

Do I need the gh CLI installed to verify my pipeline install health?

You need the gh CLI installed and authenticated because the install validation checks GitHub availability, authentication status, and repository reachability to ensure your CI automation can interact with GitHub issues.

What is the best way to troubleshoot a partially migrated CI automation pipeline?

Troubleshoot a partially migrated CI automation pipeline by running read-only diagnostics that audit configuration, GitHub access, plugin root resolution, and base-branch enforcement wiring, surfacing drift severity with remediation guidance.