Contribution Workflow and Label Requirements for the i-have-adhd Repository

The i-have-adhd repository enforces a strict contribution workflow requiring every pull request to declare its authorship type (Human, AI, or Hybrid), apply three mandatory label groups (Target, Author, Workflow), and include a standardized four-section description covering changes, behavior, safety, and verification.

The i-have-adhd project maintains high code quality and clear provenance through a comprehensive contribution workflow and label requirements system. This open-source repository, which provides ADHD-focusedCursor skills and development tools, requires contributors to follow specific protocols documented in CONTRIBUTING.md to ensure every change is categorized, safe, and properly reviewed.

Authorship Declaration Categories

Every pull request must declare one of three authorship categories in the PR description. This requirement is reflected in the [Author] label group and enforced through the repository’s pull request template.

• Human-authored – The substantive implementation was performed entirely by a human contributor.
• Autonomous-agent-authored – An AI agent performed the main changes, with a human providing the task description and reviewing the final result.
• Hybrid – Both a human and one or more AI agents contributed substantively to the implementation.

This classification appears in the PR description and must match the corresponding Author label selected in the GitHub interface.

Mandatory Label Groups

The label requirements specify that three independent label groups must be applied to every PR via the GitHub UI. These are defined in .github/pull_request_template.md and cross-referenced in CONTRIBUTING.md.

Target Labels

Indicates which project component the change affects:

• Target:Integrations
• Target:Evals
• Target:Rules
• Target:Docs

Author Labels

Mirrors the authorship declaration:

• Author:Human
• Author:Hybrid
• Author:AI

Workflow Labels

Describes the nature of the change (select exactly one):

• bug
• enhancement
• issue
• question
• duplicate

PR Content Requirements

The contribution workflow mandates that every PR description contain four specific sections to facilitate review and verification.

1. What changed and why – Brief summary of the modification and its rationale.
2. Before and after behavior – Description of observable behavior prior to and after the change.
3. Safety, compatibility, and side‑effects – Analysis of safety considerations, compatibility impacts, or potential side effects.
4. Verification – Exact commands run and their output summary.

Example PR description structure:

## What changed and why

- Brief summary of the change.

## Before and after behavior

- Describe the observable behavior prior to the change.
- Describe the new behavior after the change.

## Safety, compatibility, and side‑effects

- List any safety considerations, compatibility impacts, or potential side‑effects.

## Verification

- Commands run:
  python3 -m unittest discover -s tests -v
  python3 scripts/run_evals.py validate
- Summary of results:
  All tests passed. No regressions detected.

Canonical Skill Synchronization

When contributing changes to skill rules, the contribution workflow requires keeping the canonical skill file synchronized with its Cursor runtime copy. The canonical definition lives at skills/i-have-adhd/SKILL.md and must be mirrored to .cursor/skills/i-have-adhd/SKILL.md.

Synchronization commands:

cp skills/i-have-adhd/SKILL.md .cursor/skills/i-have-adhd/SKILL.md
cmp skills/i-have-adhd/SKILL.md .cursor/skills/i-have-adhd/SKILL.md

Verification Process

After submission, maintainers execute the appropriate verification commands based on the change type. These typically include unit tests and evaluation scripts. The command output must be included in the PR discussion as proof of validation.

Standard verification commands include:

python3 -m unittest discover -s tests -v
python3 scripts/run_evals.py validate

Summary

• The contribution workflow and label requirements for i-have-adhd mandate three authorship categories: Human-authored, Autonomous-agent-authored, and Hybrid.
• Every PR must display three label groups: Target (component), Author (provenance), and Workflow (change type).
• PR descriptions must follow a four-section template covering changes, behavior, safety, and verification.
• Skill rule modifications require syncing skills/i-have-adhd/SKILL.md with .cursor/skills/i-have-adhd/SKILL.md.
• Verification commands must be run and their output posted to the PR discussion before merge.

Frequently Asked Questions

What happens if I forget to add the required labels to my pull request?

The repository’s contribution workflow is designed to enforce labeling through the PR template in .github/pull_request_template.md. If labels are missing, maintainers will request changes before review proceeds, as the label requirements are mandatory for triage and automation.

Can I submit a PR that was partially written by AI?

Yes. The authorship declaration system explicitly supports Hybrid contributions where both humans and AI agents contribute substantively. You must select the Author:Hybrid label and document the division of labor in the PR description according to CONTRIBUTING.md.

How do I verify that my skill file changes are synchronized correctly?

Run the copy and compare commands documented in the canonical skill section: copy skills/i-have-adhd/SKILL.md to .cursor/skills/i-have-adhd/SKILL.md and use cmp to verify they are identical. This ensures the Cursor runtime uses the same definitions as the canonical source.

Are there specific verification commands for documentation-only changes?

While the standard verification commands include python3 -m unittest discover and python3 scripts/run_evals.py validate, the exact verification required depends on the Target label applied. Documentation changes under Target:Docs may require different validation, but the PR must still document the exact verification performed in the dedicated section.

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