qdoctor

Audits a repository's Claude Code configuration against the user's other repos.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/QSchlegel/session-viz --skill qdoctor-qschlegel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qdoctor
Source: https://github.com/QSchlegel/session-viz/tree/main/plugins/session-viz/skills/qdoctor
Command: npx skills add https://github.com/QSchlegel/session-viz --skill qdoctor-qschlegel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Scheduled and headless Claude Code runs often fail silently because a repo's configuration is missing pieces the user's other repos already have — most critically a Write permission entry, without which a headless run dies at its first write after doing all the work. This Skill compares the current repo's CLAUDE.md, slash commands, hooks, and permissions against the user's own other repositories to surface concrete configuration gaps. ## Core Features & Use Cases - Cross-repo configuration audit: Compares this repo's .claude/settings.json and settings.local.json against every other repo discovered from transcript cwd records, never against a generic best-practice list. - Write-permission check: Flags when permissions.allow lacks a Write or Edit entry, the most common cause of cron jobs that run for weeks and ship nothing. - Evidence-graded findings: Reports a gap only when at least half of four or more other repos have the item; otherwise it reports a note, keeping evidence separate from hunches. - Use Case: A user's nightly scheduled task produces no output. Running the audit reveals eleven of their sixteen repos allow Write in settings while this one does not, and the Skill offers to draft the fix on a branch. ## Quick Start Ask the assistant to audit this repository's Claude Code setup against my other projects and tell me why my scheduled runs might be failing.

Frequently Asked Questions about qdoctor

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

FAQPage Schema
How do I check if my repo is set up correctly for Claude Code?▼

Run the qdoctor audit, which compares your repo's CLAUDE.md, slash commands, hooks, and permissions against your other repositories. Use the --all flag to audit every repo that has transcripts on the machine.

Why does my scheduled Claude Code run fail without errors?▼

Headless and scheduled runs cannot answer permission prompts, so without a Write or Edit entry in permissions.allow the run dies at its first write after completing all prior work. The audit's permissionCoversWrite check detects exactly this condition.

Does the audit check user-level Claude settings?▼

No, it reads only the repo's .claude/settings.json and .claude/settings.local.json. A machine-wide allow entry in user-level settings will show as not covering Write, so verify user settings separately before changing a repo.

What counts as a configuration gap versus a note?▼

A finding is a gap only when at least half of the other repos have the item and at least four repos exist for comparison. With fewer repos or weaker prevalence it is reported as a note, an observation with too little evidence behind it.

Can the audit fix the configuration problems it finds?▼

Yes, it can offer to draft a CLAUDE.md from your own recurring constraints or write the missing settings line. Fixes are written on a branch, never directly to main, and never committed without being asked.