brain-uninstall

Files (1)

• SKILL.md

SKILL.md (first lines)

# Brain Plugin -- Uninstall

This skill guides the user through removing or disconnecting the brain plugin's persistent memory layer. Per ADR-0055, the brain ships as a standalone `mybrain` plugin (separate from atelier-pipeline). This skill targets the brain config and database — it does NOT uninstall the mybrain plugin itself (use `claude plugin uninstall mybrain` for that). Run this conversationally -- ask questions one at a time, not as a list. Present what will be removed BEFORE doing anything destructive.

<contract>
  <requires>
    - At least one brain config file exists: `.claude/brain-config.json` (shared) or `${CLAUDE_PLUGIN_DATA}/brain-config.json` (personal).
    - Explicit user "yes" confirmation before any destructive action (config removal, container/volume removal, database drop, table drop).
    - For full-uninstall paths: matching tooling reachable for the chosen strategy (`docker` for Docker, `pg_isready` + `dropdb` for local, `psql` with credentials for remote).
  </requires>
  <produces>
    - Removal of `.claude/brain-config.json` and/or `${CLAUDE_PLUGIN_DATA}/brain-config.json`.
    - Optionally (Path B, per user choice): stopped/removed Docker container `brain-db`, deleted `brain-data` volume, dropped local database, or dropped public schema on remote.
  </produces>
  <invalidates>
    - `brain-hydrate` `<requires>`: brain is no longer reachable / `brain_enabled` no longer true after disconnect.
    - Pre-approved brain MCP tools in `permissions.allow` remain in `settings.json` but are inert until a new brain is configured (not removed by this skill).
  </invalidates>
</contract>

<protocol id="config-detection">

## Detection: Locate Config

Before asking anything, find the brain config file:

1. Check if `.claude/brain-config.json` exists in the project root (shared config).
2. Check if `${CLAUDE_PLUGIN_DATA}/brain-config.json` exists (personal config).
3. If **both** exist, note both. The shared config is the project-level config; the personal config is the user's local override.
4. If **neither** exists, stop:

> No brain configuration found. There is nothing to uninstall.
> If a brain was set up but the config was already removed, the database
> may still exist. Use your database tools directly to clean it up.

5. If a config file is found, read it to determine:
   - **Database strategy:** Infer from the `database_url` field:
     - Contains `localhost` with port `5432` and user `atelier` -- likely **Docker**
     - Contains `localhost` -- likely **Local PostgreSQL**
     - Contains a remote host -- **Remote PostgreSQL**
   - **Config type:** personal (`${CLAUDE_PLUGIN_DATA}`) or shared (`.claude/`)
   - **Scope:** from the `scope` field
   - **Brain name:** from the `brain_name` field (if present)

</protocol>

---

<procedure id="uninstall">

## Uninstall Procedure

### Step 1: Present Current Setup

Display what the brain setup looks like based on the config file:

```
Brain Uninstall -- Current Setup
================================

Config type:     [personal | shared]
Config location: [file path]
Database:        [Docker | Local PostgreSQL | Remote PostgreSQL]
Database URL:    [URL with password masked as ****]
Scope:           [scope path]
Brain name:      [name, or "Brain" if not set]
```

### Step 2: Offer Uninstall Options

Ask the user which level of removal they want:

> How would you like to proceed?
>
> 1. **Disconnect only** -- Remove the config file but leave the database untouched. The brain data stays intact and can be reconnected later.
> 2. **Full uninstall** -- Remove the config file AND clean up the database. Brain data will be permanently deleted.

Wait for the user's answer before proceeding.

---

### Path A -- Disconnect Only

This path removes the config file without touching the database.

#### A1: Present Removal Plan

```
Disconnect Plan
===============

WILL REMOVE:
  [config file path]    -- brain configuration file

WILL NOT TOUCH:
  Database at [masked URL]    -- data remains intact
  mybrain plugin              -- the plugin itself stays installed (use `claude plugin uninstall mybrain` to remove it)
```

If the config is shared (`.claude/brain-config.json`), add:

```
NOTE: This file is committed to git. You will need to commit the deletion.
```

#### A2: Get Confirmation

> Remove the config file? The database will remain untouched and can be
> reconnected by running brain-setup again. (yes/no)

**Do not proceed without explicit "yes" from the user.**

#### A3: Remove Config File

Delete the config file.

#### A4: Print Summary

```

From UberUmbra/atelier-pipeline, Apache-2.0.

More from UberUmbra/atelier-pipeline