# Repair Dev Workspace

Starts, reseeds and verifies isolated dev services, including their ports and health.

- Repository: https://github.com/paperclipai/paperclip (109885 stars)
- Category: DevOps
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add paperclipai/paperclip --skill paperclip-dev-workspace-run-verify-fix -g -a claude-code -y`
Codex: `npx skills add paperclipai/paperclip --skill paperclip-dev-workspace-run-verify-fix -g -a codex -y`
Cursor: `npx skills add paperclipai/paperclip --skill paperclip-dev-workspace-run-verify-fix -g -a cursor -y`
Gemini CLI: `npx skills add paperclipai/paperclip --skill paperclip-dev-workspace-run-verify-fix -g -a gemini-cli -y`

## Description

Run, verify, reseed, and repair Paperclip isolated dev workspace services. Use when asked to start or fix a managed project/worktree service and prove health, login readiness, cloned data, runtime visibility, and correct port ownership.

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

# Paperclip Dev Workspace Run / Verify / Fix

This skill is for Paperclip-specific development workspaces whose service is
started through project execution workspace runtime services, typically a
worktree service such as `paperclip-dev`.

Success means all of these are true:

- the service was started through the normal managed runtime path, not a
  detached workaround
- the worktree database is a full bootstrapped isolated clone of the primary
  instance database
- `/api/health` returns `status: ok` and `bootstrapStatus: ready`
- the root page returns `200` and does not show the first-admin setup gate
- the board user can log in with their normal dev credentials
- the app shows populated cloned data, not only a manually copied auth user
- the main control plane shows the service as `running` / `healthy` with the
  expected URL
- the served workspace app also knows about that service and shows it as
  `running` / `healthy`
- the process that owns the service port really belongs to the target
  workspace: `readlink /proc/<pid>/cwd` resolves inside the target worktree,
  not a sibling workspace

If any item fails, keep fixing. Do not mark the issue done because one probe
passed.

## Hard rules

The rest: https://github.com/paperclipai/paperclip/blob/HEAD/.agents/skills/paperclip-dev-workspace-run-verify-fix/SKILL.md