# How to Uninstall and Reinstall a Forked Version of the i-have-adhd Skill

> Learn how to uninstall and reinstall a forked i-have-adhd skill. Remove the local plugin and marketplace registration, then install from your GitHub fork.

- Repository: [Ayoub Ghriss/i-have-adhd](https://github.com/ayghri/i-have-adhd)
- Tags: how-to-guide
- Published: 2026-09-13

---

**To switch from the upstream i-have-adhd skill to your own fork, you must completely remove both the local plugin and the marketplace registration, then register and install from your fork's GitHub repository.**

The *i-have-adhd* skill is distributed as a plugin for AI-agent runtimes including Claude Code, Codex, and Pi. When you fork the `ayghri/i-have-adhd` repository to customize the behavior in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md), the process for uninstalling and then reinstalling a forked version of the skill requires a specific four-step sequence to prevent the upstream version from shadowing your changes.

## Why Forking Requires a Clean Reinstall

Forking creates an independent copy of the repository under your GitHub account. However, AI-agent runtimes maintain two separate references to a skill: the **local plugin copy** and the **marketplace registry entry**. If you only uninstall the local plugin without clearing the marketplace registration, the runtime may automatically reinstall the upstream version from `ayghri/i-have-adhd` instead of your fork.

According to the repository's [`INSTALL.md`](https://github.com/ayghri/i-have-adhd/blob/main/INSTALL.md) (lines 21-45) and [`README.md`](https://github.com/ayghri/i-have-adhd/blob/main/README.md) (lines 84-91), you must completely sever both references before adding your fork.

## The Four-Step Process

The workflow is consistent across all supported runtimes, though the specific CLI commands differ:

1. **Remove the upstream plugin** from your local environment
2. **Delete the marketplace registration** to clear the upstream reference
3. **Add your fork to the marketplace** pointing to `your-username/i-have-adhd`
4. **Install the plugin** from your newly registered fork

### Step 1: Remove the Upstream Plugin

First, uninstall the existing skill to remove the local copy. This does not affect the marketplace entry.

### Step 2: Clear the Marketplace Registration

Remove the upstream entry from the runtime's marketplace database. This step is critical—without it, the runtime retains a pointer to the original `ayghri/i-have-adhd` repository.

### Step 3: Register Your Fork

Add your forked repository URL to the marketplace. This registers `https://github.com/<your-username>/i-have-adhd` as a valid source for the skill.

### Step 4: Install from Your Fork

Finally, install the skill using the marketplace entry you just created. The runtime will fetch the manifest from your fork (defined in files like [`.claude-plugin/plugin.json`](https://github.com/ayghri/i-have-adhd/blob/main/.claude-plugin/plugin.json)) and load the skill rules from [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md).

## Runtime-Specific Commands

While the logic remains identical, each AI-agent runtime uses distinct CLI syntax.

### Claude Code

The Claude Code workflow is documented in [`INSTALL.md`](https://github.com/ayghri/i-have-adhd/blob/main/INSTALL.md) and [`README.md`](https://github.com/ayghri/i-have-adhd/blob/main/README.md) (lines 84-91).

```bash

# Step 1 & 2: Remove plugin and marketplace entry

claude plugin uninstall i-have-adhd
claude plugin marketplace remove i-have-adhd

# Step 3: Register your fork

claude plugin marketplace add <your-username>/i-have-adhd

# Step 4: Install from fork

claude plugin install i-have-adhd@i-have-adhd

```

### Codex

Codex follows a similar pattern but uses `remove` instead of `uninstall` and requires a `--ref` flag:

```bash

# Step 1 & 2: Remove plugin and marketplace entry

codex plugin remove i-have-adhd
codex plugin marketplace remove i-have-adhd

# Step 3: Register your fork with branch reference

codex plugin marketplace add <your-username>/i-have-adhd --ref main

# Step 4: Install from fork

codex plugin add i-have-adhd@i-have-adhd

```

### AgY (Antigravity)

AgY does not use a marketplace abstraction. You reference the repository URL directly:

```bash

# Step 1: Uninstall upstream

agy plugin uninstall i-have-adhd

# Steps 3 & 4: Install directly from fork URL

agy plugin install https://github.com/<your-username>/i-have-adhd

```

### Pi

Pi also uses direct URL management without a separate marketplace step:

```bash

# Step 1: Remove upstream

pi remove https://github.com/ayghri/i-have-adhd

# Steps 3 & 4: Install from fork

pi install https://github.com/<your-username>/i-have-adhd

```

### OpenCode

OpenCode manages plugins via configuration files rather than CLI commands. According to [`AGENTS.md`](https://github.com/ayghri/i-have-adhd/blob/main/AGENTS.md), you must:

- Remove the plugin entry from [`opencode.json`](https://github.com/ayghri/i-have-adhd/blob/main/opencode.json) or delete the plugin directory
- Add a new entry pointing to your fork's `.opencode/plugins/i-have-adhd.mjs`
- Restart OpenCode or reload the plugin configuration

## Key Repository Files

Understanding these source files helps clarify why the uninstall-and-reinstall process works:

- **[`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md)**: Contains the actual skill rules and behavior you modify in your fork. This is the primary file you customize when forking.
- **[`.claude-plugin/plugin.json`](https://github.com/ayghri/i-have-adhd/blob/main/.claude-plugin/plugin.json)**: Declares the plugin metadata, version, and repository URL for Claude Code. The runtime reads this manifest during installation to determine where to load the skill from.
- **[`AGENTS.md`](https://github.com/ayghri/i-have-adhd/blob/main/AGENTS.md)**: Maps each supported runtime to its specific entry points and manifest locations (e.g., `.claude-plugin/`, `.codex-plugin/`).
- **[`INSTALL.md`](https://github.com/ayghri/i-have-adhd/blob/main/INSTALL.md)**: Lines 21-45 contain the detailed uninstall and reinstall commands for Claude Code and other runtimes.
- **[`README.md`](https://github.com/ayghri/i-have-adhd/blob/main/README.md)**: Lines 84-91 highlight the Claude Code installation workflow and prerequisites.

## Summary

- Uninstalling and then reinstalling a forked version of the skill requires removing both the local plugin and the marketplace registration to prevent upstream shadowing.
- The process involves four distinct steps: uninstall plugin, remove marketplace entry, add fork to marketplace, and install from the new source.
- Claude Code and Codex require explicit marketplace management commands, while Pi and AgY use direct URL installation.
- Always verify your changes by checking the runtime loads [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) from your fork rather than the original repository.

## Frequently Asked Questions

### Why do I need to remove both the plugin and the marketplace entry?

The runtime maintains two separate references: the local plugin copy and the marketplace registry. If you only run `plugin uninstall`, the marketplace entry for `ayghri/i-have-adhd` persists and can trigger an automatic reinstallation of the upstream version. Removing both ensures a clean slate for your fork.

### Can I install multiple forks simultaneously?

Most runtimes treat the skill name `i-have-adhd` as a unique identifier. Installing a second fork typically overwrites the first. To test multiple versions, you would need to rename the skill identifier in your fork's manifest files (such as [`.claude-plugin/plugin.json`](https://github.com/ayghri/i-have-adhd/blob/main/.claude-plugin/plugin.json)) before registration.

### How do I verify my fork is installed correctly?

After installation, check which repository URL the runtime is using. For CLI-based runtimes like Claude Code or Codex, run the plugin list command and verify it points to `https://github.com/<your-username>/i-have-adhd`. The behavior should match your customizations in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md).

### Where do I edit the skill behavior in my fork?

All skill logic resides in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) at the root of your forked repository. Edit this file to customize how the AI-agent manages ADHD-related workflows, then commit and push to your GitHub fork. The changes take effect the next time you install or update the plugin from your fork.