How to Create a Custom Fork of the i-have-adhd Skill

To create a custom fork of the i-have-adhd skill, fork the ayghri/i-have-adhd repository, edit the skills/i-have-adhd/SKILL.md rule file to modify behavior, push your changes, and reinstall the skill in your AI agent to override the upstream version.

The i-have-adhd skill is a lightweight, manifest-driven enhancement for AI coding agents that relies entirely on a single markdown rule file rather than compiled code. Because the repository exposes all behavior through declarative configuration in SKILL.md, you can create a custom fork of the i-have-adhd skill by altering these rules and pointing your runtime to your personal repository.

Forking and Modifying the Core Repository

Customizing the skill requires forking the source repository and editing the authoritative rule definition. The architecture is intentionally minimal: all behavior is defined in skills/i-have-adhd/SKILL.md, making modifications straightforward and instantaneous.

Step 1: Fork the Repository on GitHub

Navigate to the ayghri/i-have-adhd repository on GitHub and click the Fork button. This creates a copy under your username (e.g., <your-username>/i-have-adhd) that you can modify without affecting the upstream project.

Alternatively, clone the repository locally and push to a new remote:

git clone https://github.com/ayghri/i-have-adhd.git
cd i-have-adhd
git remote set-url origin https://github.com/<your-username>/i-have-adhd.git

Step 2: Edit the Core Rule File (SKILL.md)

The skill's behavior is governed by skills/i-have-adhd/SKILL.md. This file contains the complete rule set, metadata, and configuration flags (such as disable-model-invocation) that agents consume.

Open the file in your preferred editor:

code skills/i-have-adhd/SKILL.md

Modify any rules, adjust wording, or add new constraints specific to your workflow. Because this is the only file controlling logic, changes here instantly redefine how the skill behaves when loaded by an agent.

Step 3: Commit and Publish Your Changes

After editing, commit the modifications and push to your fork:

git add skills/i-have-adhd/SKILL.md
git commit -m "Customize ADHD rules for personal workflow"
git push origin main

Your fork is now the authoritative source for your customized version of the skill.

Installing Your Custom Fork in AI Agents

Once published, you must redirect your AI agent to load the skill from your fork rather than the official marketplace version. The installation path varies by runtime.

For Claude Code Users

Claude Code manages skills through its plugin marketplace. To swap to your fork:

# Remove the upstream version

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

# Register your fork

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

# Install from your fork

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

These commands deregister the official ayghri/i-have-adhd reference and bind your version using the @ syntax to specify the fork source.

For OpenCode Users

OpenCode uses a vendor folder architecture. Clone your fork directly into the runtime's plugin directory:

git clone https://github.com/<your-username>/i-have-adhd \
  ~/.config/opencode/vendor/i-have-adhd

The opencode.json manifest already references this path, so no additional registration is required. Restart OpenCode and invoke the skill to load your custom rules.

Manual Installation for Other Runtimes

For agents not using marketplace commands, reference AGENTS.md and INSTALL.md in the repository root. These files map runtime entry points and provide platform-specific instructions for loading skills from arbitrary Git URLs. Generally, you will update the skill manifest URL in your agent's configuration to point to https://github.com/<your-username>/i-have-adhd.

Verifying Your Custom Rules

Start a new session with your AI agent and invoke the skill:

/i-have-adhd

The output should reflect your modifications from SKILL.md. If the agent responds with your custom rules or adjusted phrasing, the fork is active. If the upstream behavior persists, verify that the previous installation was fully removed and that your fork URL is correctly registered in the agent's skill manifest.

Summary

• Fork the repository on GitHub to create your own copy of ayghri/i-have-adhd.
• Edit skills/i-have-adhd/SKILL.md to customize rules, metadata, or invocation flags without touching any code.
• Push changes to your fork to publish the customized behavior.
• Reinstall the skill in your AI agent using runtime-specific commands to override the upstream reference.
• Verify by invoking the skill and confirming your custom rules are active.

Frequently Asked Questions

What file controls the behavior in the i-have-adhd skill?

The file skills/i-have-adhd/SKILL.md is the sole authority for skill behavior. It contains the complete rule set, metadata, and configuration flags that AI agents parse to determine how to apply the skill. According to the ayghri/i-have-adhd source code, no compiled code or additional scripts are required to modify functionality.

Do I need to modify any code to customize the skill?

No. The i-have-adhd skill uses a manifest-driven architecture where behavior is defined entirely in markdown documentation. You only need to edit SKILL.md to change how the skill operates. The repository contains no build steps or compiled artifacts, so any text editor is sufficient for customization.

Can I use my fork with multiple AI agents simultaneously?

Yes. As long as each agent is configured to load the skill from your fork's URL (or local path), they will all consume the same SKILL.md rules. Be aware that agents like Claude Code and OpenCode cache skill definitions locally, so you may need to reinstall or restart each runtime after pushing updates to your fork.

How do I revert to the official version if something breaks?

Uninstall your forked version using your agent's plugin manager (e.g., claude plugin uninstall i-have-adhd), then reinstall from the official marketplace source (ayghri/i-have-adhd). The original SKILL.md rules will be restored, overriding any local changes from your fork.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}