# How to Update the i-have-adhd Skill After Forking for Custom Rules > Learn to update the i-have-adhd skill after forking. Uninstall the upstream plugin, add your fork, and reinstall to use your custom rules instead of the originals. - Repository: [Ayoub Ghriss/i-have-adhd](https://github.com/ayghri/i-have-adhd) - Tags: how-to-guide - Published: 2026-07-22 --- **Uninstall the upstream plugin, add your forked repository to the marketplace, and reinstall the skill so the agent harness loads your customized [`SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/SKILL.md) instead of the original rules.** Forking the `ayghri/i-have-adhd` repository allows you to modify the ADHD-focused output rules, but the agent platform continues to reference the upstream plugin until you explicitly redirect it. To apply your customizations, you must remove the original reference and point the harness to your forked version containing the edited rule set. ## Why Forking Requires a Manual Plugin Swap The i-have-adhd skill stores its behavior in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md), a markdown file containing the rule set that drives the agent’s output style. When you fork the repository and edit this file, the changes exist in your GitHub namespace, but the agent’s plugin index still points to `ayghri/i-have-adhd`. According to the source code in [`README.md`](https://github.com/ayghri/i-have-adhd/blob/main/README.md) (lines 100-107), you must uninstall the upstream copy and reinstall from your fork to redirect the harness to your customized `.skill` directory. ## Updating the Skill in Claude Code Follow this three-step sequence to switch from the upstream plugin to your customized fork. ### 1. Remove the Upstream Plugin First, uninstall the original skill and remove it from the marketplace index: ```bash claude plugin uninstall i-have-adhd claude plugin marketplace remove i-have-adhd ``` This drops the reference that the harness maintains in its plugin registry. ### 2. Add Your Fork to the Marketplace Register your forked repository under your GitHub username. Replace `` with your actual handle: ```bash claude plugin marketplace add /i-have-adhd ``` This makes the harness aware of your custom rule source. ### 3. Install the Custom Version Finally, install the skill from your fork: ```bash claude plugin install i-have-adhd@i-have-adhd ``` After installation, restart Claude Code or start a new session. Invoke the skill with `/i-have-adhd` to verify the harness reads your edited [`SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/SKILL.md) and applies your custom rules immediately. ## Updating for Other Agent Platforms The same uninstall-add-install pattern applies to Codex, Zed, Gemini CLI, and other agents, though command syntax varies by platform. For **Codex**, use the following commands as documented in [`INSTALL.md`](https://github.com/ayghri/i-have-adhd/blob/main/INSTALL.md): ```bash codex plugin remove i-have-adhd codex plugin marketplace add /i-have-adhd --ref main codex plugin add i-have-adhd@i-have-adhd ``` For **Zed**, you can alternatively copy the rule contents from [`SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/SKILL.md) into `~/.config/zed/AGENTS.md` or a project-local `.cursor/rules/` file to make the style always-on without managing a plugin. ## Customizing the Rule Set The behavior-driving file is located at [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) in your fork. Edit this file to change how the agent structures responses—such as leading with the answer or breaking complex tasks into numbered sub-tasks. The [`plugin.json`](https://github.com/ayghri/i-have-adhd/blob/main/plugin.json) file contains metadata for the marketplace, while [`hooks/hooks.json`](https://github.com/ayghri/i-have-adhd/blob/main/hooks/hooks.json) enables optional always-on flags for Claude Code. ## Summary - The i-have-adhd skill uses [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) to define output rules. - After forking, you must uninstall the upstream plugin and reinstall from your fork to apply changes. - Use `claude plugin uninstall` and `claude plugin marketplace add` to redirect the harness to your repository. - Restart the agent session after updating to load the new rules from your customized `.skill` directory. - Alternative agents like Codex follow the same pattern with platform-specific CLI commands documented in [`INSTALL.md`](https://github.com/ayghri/i-have-adhd/blob/main/INSTALL.md). ## Frequently Asked Questions ### Where is the skill configuration stored? The rule logic lives in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md). The agent’s plugin registry tracks which repository hosts the skill, with metadata defined in [`plugin.json`](https://github.com/ayghri/i-have-adhd/blob/main/plugin.json) at the repository root and optional hooks configured in [`hooks/hooks.json`](https://github.com/ayghri/i-have-adhd/blob/main/hooks/hooks.json). ### Do I need to restart the agent after updating the skill? Yes. After running the uninstall and install commands, start a new session or restart the agent to force the harness to reload [`SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/SKILL.md) from your fork. ### Can I keep the same skill name after forking? Yes. The skill identifier remains `i-have-adhd` even when installed from your fork because the marketplace entry points to your repository while maintaining the same plugin namespace. ### What if I want different rules for only one project? For project-specific customization without maintaining a fork, copy the relevant rules from [`SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/SKILL.md) into your project’s local configuration—such as `.cursor/rules/` for Cursor or [`.zed/AGENTS.md`](https://github.com/ayghri/i-have-adhd/blob/main/.zed/AGENTS.md) for Zed—instead of installing the skill globally.