Skip to content

repoctl documentation

What does your repository need next?

Initialize, diagnose, create, check, and release pnpm or Turborepo workspaces from one task-first CLI.

A real repoctl doctor report showing repository checks and findings

Choose a task

Pick the result you need. Each path begins with the smallest safe command.

Three commands to a useful baseline

Install repoctl, initialize its managed defaults, then diagnose the workspace.

  1. Install

    pnpm add -D repoctl

    Keep repoctl with the repository so teammates and CI use the same version.

  2. Initialize

    pnpm exec repo init

    Review the file plan before adding managed scripts and configuration.

  3. Diagnose

    pnpm exec repo doctor

    Use the first blocker as your next task. Run the diagnosis again after each fix.

See the plan before the repository changes

Preview work, redact local paths, and keep the exact command sequence with the report.

See how diagnosis works
pnpm exec repo new docs --template vitepress --dry-run
pnpm exec repo check --dry-run
pnpm exec repo doctor --markdown --redact

Continue with the decision in front of you

Move from the current task to the level of detail you need.

Frequently asked questions

What is repoctl?

repoctl is a task-first CLI for initializing, diagnosing, creating, checking, and releasing pnpm and Turborepo monorepos.

How do I install repoctl?

Run pnpm add -D repoctl, then use pnpm exec repo init and pnpm exec repo doctor.

How does repoctl relate to pnpm and Turborepo?

pnpm and Turborepo provide package management and task orchestration; repoctl turns repository conventions and checks into reusable tasks.

What is the difference between repo doctor and repo check?

repo doctor diagnoses repository health, while repo check plans and runs lint, type, build, and test checks.