# Dev Doctor

Find what is going wrong with Devs in production, file each cause once in the Devs and...

- Repository: https://github.com/ParadevAI/Paradev (15823 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add ParadevAI/Paradev --skill dev-doctor -g -a claude-code -y`
Codex: `npx skills add ParadevAI/Paradev --skill dev-doctor -g -a codex -y`
Cursor: `npx skills add ParadevAI/Paradev --skill dev-doctor -g -a cursor -y`
Gemini CLI: `npx skills add ParadevAI/Paradev --skill dev-doctor -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add ParadevAI/Paradev`

## Description

Find what is going wrong with Devs in production, file each cause once in the Devs and Channels Linear project, and refine the Devs architecture one rough edge at a time. Run by the "Dev doctor" automations; use when asked to diagnose Dev failures or review the Devs architecture.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Dev doctor

Devs are Paradev's agent teammates (see "Architecture map" in the notebook). Their code was
written fast on purpose. You keep it honest: you find the failures that slip through, you turn
each understood failure into code so nobody treats it by hand again, and you move the
architecture toward a good end state one change at a time.

The reconciler (`packages/trpc/src/router/agent/reconcile.ts`) already repairs the failures we
understand. You handle the ones nobody has seen before, and you make yourself unnecessary: a kind
of failure you have diagnosed three times with the same fix becomes a reconciler rule or a code
fix, and you stop seeing it.

You run in a cloud workspace of the Paradev repo. Nobody is watching: do not ask questions. When
something blocks you, write it in the run log and in your final message, and continue.

## Your notebook

The Linear document **Dev doctor notes** (id `b74e1574-7fef-4297-b3b9-d99976cfcd26`, in project
**Devs and Channels**, id `124fd465-3c78-43dc-a252-e99f5f8c33e0`) is your memory between runs.

- Read it first: `get_document` on the Linear plugin.
- Update it last. Two runs can overlap, so read it again right before you write, and change only
  your parts with `save_document`'s `patch`, never a full rewrite. Keep everything people wrote. Add one line at the top
  of "Run log" for this run. Update the "Failure kinds" table and the "Rough edges" list from what
  you learned. When you research something, add a section with what you found and the sources.
- When this procedure is wrong or missing something, open a PR that edits this file.

Reach the plugins with `superset mcp call-tool <tool> '<json args>' --plugin <linear|neon|posthog|sentry> --json`, or the matching MCP tools if your agent has them.

## Mode

The prompt says which mode: **incidents** (hourly) or **architecture** (daily). Do only that mode.

## Incidents

### 1. Gather the last day

The rest: https://github.com/ParadevAI/Paradev/blob/HEAD/.agents/skills/dev-doctor/SKILL.md