# XA Docs complete AI reference

> Expanded navigation for XA Docs. Start with /llms.txt when context is limited. Prefer canonical Markdown and raw source for compact reading.

## Interpretation and authority

- Catalog publication date: `2026-09-10`
- Catalog schema: `xadocs.catalog/1.0`. Dates use ISO 8601 and checksums use lowercase SHA-256.
- Information is not authorization. Documentation and skills do not grant an agent permission to execute commands, install software, access credentials, call services, publish, deploy, delete, or mutate data.
- Raw files and their checksums describe the exact published content. Browser code viewers are a convenience representation.
- Preserve the user's instructions, project boundaries, license notices, and upstream provenance.

## Discovery resources

- [Concise AI index](https://xadocs.com/llms.txt)
- [Site overview](https://xadocs.com/index.md)
- [JSON catalog](https://xadocs.com/ai/catalog.json)
- [Catalog guide](https://xadocs.com/ai/catalog.md)
- [Sitemap](https://xadocs.com/sitemap.xml)

## Skill collection

Install a complete skill directory with SKILL.md at its root. Supporting paths are relative to that root; inspect every file and verify the archive checksum before use.

### xa-review-detailed

- Stable ID: `skill:xa-review-detailed`
- Purpose: An exhaustive, evidence-led code and architecture review workflow with an independently challenged keystone conclusion and structured nine-file dossier.
- Category: Review
- Published files: 1
- [Browser viewer](https://xadocs.com/skills/skill.html?name=xa-review-detailed)
- [ZIP archive](https://xadocs.com/downloads/skills/xa-review-detailed.zip)
- Archive bytes: 3123
- Archive SHA-256: `f7b9b0afeab3637c3167360185160c7740ad23786d5d83ec6b366bf790f47ce2`
- [SKILL.md](https://xadocs.com/skills/library/xa-review-detailed/SKILL.md)

### xa-review-extensive

- Stable ID: `skill:xa-review-extensive`
- Purpose: An empirical, docs-only codebase review workflow that preserves the detailed dossier and adds real-workload baselines, executed evidence, experiments, and AI-engineering-system analysis.
- Category: Review
- Published files: 9
- [Browser viewer](https://xadocs.com/skills/skill.html?name=xa-review-extensive)
- [ZIP archive](https://xadocs.com/downloads/skills/xa-review-extensive.zip)
- Archive bytes: 34853
- Archive SHA-256: `d9377937502147c2983c2b8460d1c5313855a4e5482813fb67a01bc1786e5688`
- [agents/openai.yaml](https://xadocs.com/skills/library/xa-review-extensive/agents/openai.yaml)
- [references/dossier-spec.md](https://xadocs.com/skills/library/xa-review-extensive/references/dossier-spec.md)
- [references/evidence-method.md](https://xadocs.com/skills/library/xa-review-extensive/references/evidence-method.md)
- [references/final-verification.md](https://xadocs.com/skills/library/xa-review-extensive/references/final-verification.md)
- [references/multi-model-crosscheck.md](https://xadocs.com/skills/library/xa-review-extensive/references/multi-model-crosscheck.md)
- [references/review-protocol.md](https://xadocs.com/skills/library/xa-review-extensive/references/review-protocol.md)
- [scripts/review_inventory.py](https://xadocs.com/skills/library/xa-review-extensive/scripts/review_inventory.py)
- [scripts/validate_dossier.py](https://xadocs.com/skills/library/xa-review-extensive/scripts/validate_dossier.py)
- [SKILL.md](https://xadocs.com/skills/library/xa-review-extensive/SKILL.md)

### runtests

- Stable ID: `skill:runtests`
- Purpose: Inventory project functions, require exact test selectors, bound noisy command output, distinguish required gates from optional execution evidence, and emit actionable reports.
- Category: Testing
- Published files: 5
- [Browser viewer](https://xadocs.com/skills/skill.html?name=runtests)
- [ZIP archive](https://xadocs.com/downloads/skills/runtests.zip)
- Archive bytes: 47617
- Archive SHA-256: `d0c61a56a4c62fc8945469039ce18d59e677ae6aba2406b5dd1dcae3d3101bd7`
- [agents/openai.yaml](https://xadocs.com/skills/library/runtests/agents/openai.yaml)
- [references/test-contract.md](https://xadocs.com/skills/library/runtests/references/test-contract.md)
- [scripts/runtests.py](https://xadocs.com/skills/library/runtests/scripts/runtests.py)
- [SKILL.md](https://xadocs.com/skills/library/runtests/SKILL.md)
- [tests/test_runtests.py](https://xadocs.com/skills/library/runtests/tests/test_runtests.py)

### devhub-add-project

- Stable ID: `skill:devhub-add-project`
- Purpose: Register one local project through XA DevHub's authenticated API with conservative metadata discovery, duplicate prevention, lifecycle recovery, and exact readback verification.
- Category: DevHub
- Published files: 2
- [Browser viewer](https://xadocs.com/skills/skill.html?name=devhub-add-project)
- [ZIP archive](https://xadocs.com/downloads/skills/devhub-add-project.zip)
- Archive bytes: 4327
- Archive SHA-256: `65dfcd25e910f076ae7201f3ef2f9e9fda4cfa7b737a33a4f1d7624d522480e2`
- [agents/openai.yaml](https://xadocs.com/skills/library/devhub-add-project/agents/openai.yaml)
- [SKILL.md](https://xadocs.com/skills/library/devhub-add-project/SKILL.md)

### devhub-cleanup-tickets

- Stable ID: `skill:devhub-cleanup-tickets`
- Purpose: Review one project's active tickets, propose clearer titles and duplicate merges, and apply only the approved changes with fresh readback.
- Category: DevHub
- Published files: 2
- [Browser viewer](https://xadocs.com/skills/skill.html?name=devhub-cleanup-tickets)
- [ZIP archive](https://xadocs.com/downloads/skills/devhub-cleanup-tickets.zip)
- Archive bytes: 4313
- Archive SHA-256: `51075fada48c6eeb9fc3c3f786e4bdeaad3486d90e6703b96df0305a6c582829`
- [agents/openai.yaml](https://xadocs.com/skills/library/devhub-cleanup-tickets/agents/openai.yaml)
- [SKILL.md](https://xadocs.com/skills/library/devhub-cleanup-tickets/SKILL.md)

### devhub-control

- Stable ID: `skill:devhub-control`
- Purpose: Transport explicit, token-authenticated reads and writes through the local XA DevHub API without touching its database directly.
- Category: DevHub
- Published files: 5
- [Browser viewer](https://xadocs.com/skills/skill.html?name=devhub-control)
- [ZIP archive](https://xadocs.com/downloads/skills/devhub-control.zip)
- Archive bytes: 16461
- Archive SHA-256: `09951c296afe89a21585922ffe21271222cc423265a0595c84653c4054a4918d`
- [agents/openai.yaml](https://xadocs.com/skills/library/devhub-control/agents/openai.yaml)
- [references/api-contract.md](https://xadocs.com/skills/library/devhub-control/references/api-contract.md)
- [scripts/devhub.config.json.example](https://xadocs.com/skills/library/devhub-control/scripts/devhub.config.json.example)
- [scripts/devhub.ps1](https://xadocs.com/skills/library/devhub-control/scripts/devhub.ps1)
- [SKILL.md](https://xadocs.com/skills/library/devhub-control/SKILL.md)

### devhub-create-ticket

- Stable ID: `skill:devhub-create-ticket`
- Purpose: Create one evidence-grounded XA DevHub ticket with clarification when essential details are missing, exact project resolution, duplicate review, preview, and direct readback.
- Category: DevHub
- Published files: 2
- [Browser viewer](https://xadocs.com/skills/skill.html?name=devhub-create-ticket)
- [ZIP archive](https://xadocs.com/downloads/skills/devhub-create-ticket.zip)
- Archive bytes: 3565
- Archive SHA-256: `0cefe71312758f739056d309851d773cbee1bac329349023a9d1433de8ca032a`
- [agents/openai.yaml](https://xadocs.com/skills/library/devhub-create-ticket/agents/openai.yaml)
- [SKILL.md](https://xadocs.com/skills/library/devhub-create-ticket/SKILL.md)

### devhub-development

- Stable ID: `skill:devhub-development`
- Purpose: Coordinate multi-step development from intent through fresh verification, documentation sync, and handoff records.
- Category: DevHub
- Published files: 6
- [Browser viewer](https://xadocs.com/skills/skill.html?name=devhub-development)
- [ZIP archive](https://xadocs.com/downloads/skills/devhub-development.zip)
- Archive bytes: 10136
- Archive SHA-256: `bf89f04c61c94700d0a9ace315a4a462c5f00c0f4cc0cf332122d989def8533c`
- [agents/openai.yaml](https://xadocs.com/skills/library/devhub-development/agents/openai.yaml)
- [references/artifact-contracts.md](https://xadocs.com/skills/library/devhub-development/references/artifact-contracts.md)
- [references/development-lifecycle.md](https://xadocs.com/skills/library/devhub-development/references/development-lifecycle.md)
- [references/production-edit-protocol.md](https://xadocs.com/skills/library/devhub-development/references/production-edit-protocol.md)
- [references/verification-and-handoff.md](https://xadocs.com/skills/library/devhub-development/references/verification-and-handoff.md)
- [SKILL.md](https://xadocs.com/skills/library/devhub-development/SKILL.md)

### devhub-implementation-confirmer

- Stable ID: `skill:devhub-implementation-confirmer`
- Purpose: Read a copied XA DevHub review bundle and compare its selected tickets with current code and durable behavior before recommending completion.
- Category: DevHub
- Published files: 2
- [Browser viewer](https://xadocs.com/skills/skill.html?name=devhub-implementation-confirmer)
- [ZIP archive](https://xadocs.com/downloads/skills/devhub-implementation-confirmer.zip)
- Archive bytes: 3132
- Archive SHA-256: `fd6a126a145da0c0253459e20b126ec49a3077482532adf714822a849556b418`
- [agents/openai.yaml](https://xadocs.com/skills/library/devhub-implementation-confirmer/agents/openai.yaml)
- [SKILL.md](https://xadocs.com/skills/library/devhub-implementation-confirmer/SKILL.md)

### devhub-interview

- Stable ID: `skill:devhub-interview`
- Purpose: Clarify essential request details before ticket creation, or review a copied bundle collaboratively when requested, with focused questions and an actionable brief.
- Category: DevHub
- Published files: 2
- [Browser viewer](https://xadocs.com/skills/skill.html?name=devhub-interview)
- [ZIP archive](https://xadocs.com/downloads/skills/devhub-interview.zip)
- Archive bytes: 3052
- Archive SHA-256: `8efe95f8cd43ea3e0b4ef47b2a7532dfbf2da05853a51c1327593ccdb2963d52`
- [agents/openai.yaml](https://xadocs.com/skills/library/devhub-interview/agents/openai.yaml)
- [SKILL.md](https://xadocs.com/skills/library/devhub-interview/SKILL.md)

### devhub-knowledge

- Stable ID: `skill:devhub-knowledge`
- Purpose: Capture and retrieve durable knowledge with provenance, freshness, confidence, contradiction, and deduplication controls.
- Category: DevHub
- Published files: 4
- [Browser viewer](https://xadocs.com/skills/skill.html?name=devhub-knowledge)
- [ZIP archive](https://xadocs.com/downloads/skills/devhub-knowledge.zip)
- Archive bytes: 4545
- Archive SHA-256: `b699006589421d8b4645fc7aecb264f20ca4b8b9035c9e763723a986c2bcd0a6`
- [agents/openai.yaml](https://xadocs.com/skills/library/devhub-knowledge/agents/openai.yaml)
- [references/context-and-retrieval.md](https://xadocs.com/skills/library/devhub-knowledge/references/context-and-retrieval.md)
- [references/knowledge-policy.md](https://xadocs.com/skills/library/devhub-knowledge/references/knowledge-policy.md)
- [SKILL.md](https://xadocs.com/skills/library/devhub-knowledge/SKILL.md)

### devhub-prioritize-tickets

- Stable ID: `skill:devhub-prioritize-tickets`
- Purpose: Rank active requests by implementation and verification effort and review every title. The current control contract supports proposals only until a priority-update action is available.
- Category: DevHub
- Published files: 2
- [Browser viewer](https://xadocs.com/skills/skill.html?name=devhub-prioritize-tickets)
- [ZIP archive](https://xadocs.com/downloads/skills/devhub-prioritize-tickets.zip)
- Archive bytes: 5246
- Archive SHA-256: `7a39f55ff8bc6ab2a94489ddf5b506eb1c38fd43cb2502f64c5ca55e44ad98f8`
- [agents/openai.yaml](https://xadocs.com/skills/library/devhub-prioritize-tickets/agents/openai.yaml)
- [SKILL.md](https://xadocs.com/skills/library/devhub-prioritize-tickets/SKILL.md)

### devhub-reports

- Stable ID: `skill:devhub-reports`
- Purpose: Generate and manage grounded report packets through the XA DevHub report lifecycle.
- Category: DevHub
- Published files: 4
- [Browser viewer](https://xadocs.com/skills/skill.html?name=devhub-reports)
- [ZIP archive](https://xadocs.com/downloads/skills/devhub-reports.zip)
- Archive bytes: 3707
- Archive SHA-256: `e9ebb789a54ea3c09e605758fea7b105b4ffa92d9e1b6f3e47bffe26eae2c5e8`
- [agents/openai.yaml](https://xadocs.com/skills/library/devhub-reports/agents/openai.yaml)
- [references/report-contracts.md](https://xadocs.com/skills/library/devhub-reports/references/report-contracts.md)
- [references/report-templates.md](https://xadocs.com/skills/library/devhub-reports/references/report-templates.md)
- [SKILL.md](https://xadocs.com/skills/library/devhub-reports/SKILL.md)

## XA DevHub

- [Latest portable release and changes](https://xadocs.com/devhub/#downloads)
- Reviewed source version: `1.0.6`
- Source revision: `c49030f`
- Source commit: `c49030fb74d1907990e39c67622f8de46c666e84`
- Publication variant: `xadocs-public-3`
- Source files: 90
- License: AGPL-3.0-or-later; dependency notices and license texts are included.
- [Reviewed source ZIP](https://xadocs.com/downloads/devhub/xa-devhub-source-1.0.6-c49030f-public.zip)
- Archive bytes: 457780
- Archive SHA-256: `4d437a31b8a0f3644d432f6349c7c94c34fba792b44fabc222ee88f17d6e20f7`
- [10-skill bundle](https://xadocs.com/downloads/devhub/xa-devhub-skills.zip)
- Skill bundle SHA-256: `0253efc82e45090a88ac0372604fafa8ea7242fef8ca14cb21b024ed2fcd59b1`
- [Source viewer](https://xadocs.com/devhub/source.html)
- [Source README](https://xadocs.com/devhub/source/README.md)
- [License](https://xadocs.com/devhub/source/LICENSE)
- [Changelog](https://xadocs.com/devhub/source/CHANGELOG.md)

### User guide

# XA DevHub user guide

XA DevHub is a native Windows application for keeping projects, tickets, feedback, build commands, reusable notes, and AI handoffs together. Start with one project and one ticket. Discord and AI skills are optional; ordinary project tracking works without them. Your data stays in a folder you control.

Use the [website guide](https://xadocs.com/devhub/) for navigation and troubleshooting, the [skill library](https://xadocs.com/skills/) for companion instructions, and [GitHub](https://github.com/xa-io/devhub) for the application repository. The [latest portable download](https://xadocs.com/devhub/#downloads) shows the current version, changes, ZIP size, and SHA-256 from the current release manifest. Skills are downloaded separately. The reviewed [v1.0.6 source snapshot](https://xadocs.com/downloads/devhub/xa-devhub-source-1.0.6-c49030f-public.zip) is an older, separately maintained source package that needs a local build. You can also check [GitHub Releases](https://github.com/xa-io/devhub/releases) for published packages.

## First launch

If DevHub is already installed, continue with your first project. Otherwise:

1. Use 64-bit Windows 10 or newer. Download the current portable ZIP from the website and verify its SHA-256 against the displayed checksum.
2. Extract the complete ZIP to a writable folder. Keep the application, runtime DLLs, notices, and licenses together; do not run the app from inside the ZIP.
3. Open `devhub.exe` in the extracted folder, keeping its accompanying DLLs in place. A second launch focuses the existing window.
4. A fresh database contains one path-free **My Project** starter record. Edit it with your project information or delete it and create your own.
5. Open **Settings → open data folder** to find your private records. The default is `data\` beside the executable. Under **Backups and portable exports**, choose **versions to retain** and select **Save maintenance settings**.

For a local build of the older reviewed source snapshot, install Visual Studio 2022 with **Desktop development with C++**, CMake 3.20 or newer, Python 3, Git, and vcpkg. Extract the source ZIP and run these commands from its root:

```powershell
py -3 "1. build.py" --help
py -3 "1. build.py"
```

The wrapper produces `build\Release\devhub.exe` and can close and restart its own existing DevHub installation during a rebuild. For an isolated contributor build, follow [CONTRIBUTING.md](https://xadocs.com/devhub/source/CONTRIBUTING.md).

## Page map

- **Dashboard:** project workload, versions, recent completions, pending Discord feedback, credits, and configured pipeline actions.
- **Work Queue:** filtered active work across every project.
- **Project:** fixes, implementations, references, notes, contributors, evidence, dates, and release text.
- **Discord:** optional bot connection, monitors, suggestion review, and notification delivery.
- **Knowledge:** knowledge, conflicts, workflows, reports, and deterministic health checks.
- **Calendar:** completions, events, releases, due dates, and pipeline runs.
- **Credits:** contributor attribution, identity correction, and the public leaderboard.
- **Settings:** visual name, completion window, backup retention, opening the data folder, API information, backups, and exports. Select a different data location at launch with `--data-dir`; Settings does not move your data.

## Add a project

1. On the Dashboard, enter a name in **new project name...** and choose **Add project**, or edit the starter project.
2. Open the project page and **Edit project**, set **working path** to your project directory, such as `C:\Projects\MyApplication`, and choose **Save**. Use the folder button to confirm it opens the intended location.
3. Add a description or repository URL if useful. Aliases, version sources, Discord visibility, and Codex skills can wait. The **Codex skills** field names skills for copied packets; it does not install them.
4. Add Build, Prep, Release, or Version commands only when needed. Empty commands remain hidden.

With the companion skill installed, Codex can register and verify a project:

```text
$devhub-add-project C:\Projects\MyApplication
```

## Manage tickets

1. Open a project and use **quick add: title...**.
2. Choose Fix, Implementation, Reference, or Note, then select **Add**. Quick add saves the ticket immediately with a permanent `I<id>` and opens its editor. Cancel closes the editor without removing that saved ticket.
3. Set priority and status. Use **edit text** to write the request and **details** to read its preview, then choose **Save**. Add dates or a blocked reason when useful. Contributor add/remove/credit actions save immediately.
4. Add final evidence before marking a ticket completed. Use won't do when that is the actual decision.
5. Merge duplicate tickets to preserve their notes, contributors, attachments, and history. Delete only after checking the exact ID and title.

Try an Implementation titled **Add a setup guide**. Write what a new user should be able to do and how you will check it. Save, find it again in **Work Queue**, and change its status to **in_progress** when you start. Use **blocked** and a reason when a missing decision prevents progress. Add the result and verification before completing it. A simple daily routine is to open Work Queue, narrow it to one project's active work, choose a ticket, and save its result or next action before finishing.

P1 means low, P2 normal, P3 high, and P4 critical. **Due date** is a deadline; **review again** is when to revisit the item.

After installing the skills, use `$devhub-cleanup-tickets` with a project name to review clearer title and duplicate-merge proposals, then approve the exact changes you want. The skill rereads the tickets before saving so an outdated review cannot overwrite newer edits. Saving a title or merge can update existing bot-owned Discord notification cards.

Use [`$devhub-interview`](https://xadocs.com/skills/skill.html?name=devhub-interview) to discuss an unclear request before filing. `$devhub-create-ticket` uses it only when essential details are missing and waits for your answers before saving. Clear requests proceed normally; a discussion or draft alone creates no ticket.

Use `$devhub-prioritize-tickets` with a project name to rank active requests by the effort needed to implement and verify them, and review every title for readability. High/P3 means quick, normal/P2 means moderate, and low/P1 means substantial work. With the current control contract, this skill provides ranking and title proposals only: it makes no ticket changes until a documented priority-update action is available.

Deleting a ticket removes its database attachment records but intentionally leaves saved files for manual retention or cleanup.

## Run project commands

Build, Prep, Release, and **Ver** (version) buttons appear only when a project has the matching command configured. Output opens in the live console, and Release requires explicit confirmation. Commands and working folders come from the saved project settings; API requests cannot substitute arbitrary commands.

In **Edit project**, use **build**, **prep release**, **send release**, and **update version** for the corresponding commands. These scripts belong to your project; DevHub does not create them. Commands run in **working path** unless **working dir override** is set. Start with a command that already works for that project, quote paths containing spaces, save, and read the console output if it fails.

For a Python command, use an installed launcher the running app can resolve, such as `py -3 "Update_Version.py" --devhub`, or the full path to that launcher. Use the actual helper filename for the project. If `python` is not recognized, check the command from the app's environment; a newly opened terminal may have a different PATH.

Automatic version changes affect only the final numeric component by one. Use manual entry to change an earlier component. A version update changes source metadata; it does not rebuild the application.

For comparison, configure both a **local version file** and **published version url**, then refresh **versions**. A repository URL by itself does not enable comparison. A GitHub main-branch version file tracks public source; a release tag or published manifest tracks the corresponding release. Choose the source that matches the comparison you intend.

## Hand work to AI

- For one active ticket, right-click its title and choose **Copy AI review bundle**.
- For several tickets, use the project's AI button and select only the open, in-progress, or blocked work the next session needs.
- Paste the packet into the project session with your request, then record confirmed decisions, evidence, blockers, and next actions back in DevHub.

A packet provides scoped context. The user's request and project rules determine authority for edits, builds, publication, deployment, deletion, and other actions. **Copy release draft** uses completed work as material for prose; it does not version, publish, upload, or deploy anything.

For a review, paste the packet and ask: “Review these tickets against the current code and tell me what remains. Do not change anything.” For implementation, name the ticket and the changes you want. The packet supplies context; your message supplies the task.

## Optional Discord feedback

1. Create a bot in Discord's developer portal, enable Message Content Intent, and invite it to your server with read/history access. Enter its token under **Discord → Bot**, then choose **Save token + connect**.
2. Enter numeric user IDs in the **admin/developer whitelist** and choose **Save whitelist**. Under **Monitors**, enter the server ID and optionally a channel ID, then select **Add monitor**. A server-only monitor covers every channel the bot can read.
3. Review suggestions using **Edit pending**. Refine the title, type, priority, or notes. Choosing a project enables **Save as ticket**, which promotes the suggestion. Use **clear - keep pending** and **Save pending** to save edits without promotion.
4. Approve useful feedback or choose **Save as ticket** to create a credited ticket and fetch eligible attachments.
5. Dismiss unwanted feedback without deleting or altering the original Discord message.
6. Use **Credits > merge with** to correct duplicate contributor identities.

For optional review cards, set a destination channel under **Bot notifications**, ensure the bot can post there, and select **Save**. **Save + send test** posts a real test card. Configure this destination before using notification-card review and recovery.

Authorized mentions can become credited tickets in mapped channels, with project selection for unmapped channels. Mention DevHub while replying to the original message or completed capture post to add follow-up notes and attachments. Use `!xatickets <term>` to search active tickets and browse matching titles.

Inspect failed cards under **Delivery failures**. **Dismiss old-message alerts** hides the reviewed failures locally. **Recreate in saved channel** posts a replacement card when you choose that action. Discord edit-limit failures stop automatic retries for the failed revision.

## Choose the right durable record

- **Work item:** an action someone must complete.
- **Knowledge:** a reusable fact, decision, design, procedure, research result, or lesson.
- **Workflow:** multi-step development with intent, phases, checkpoints, blockers, evidence, and a resume point.
- **Report:** a dated weekly, project, release, health, validation, decision, or handoff interpretation.

Knowledge can be timeless, a dated snapshot, or a pointer to a living source. Stale knowledge should be rechecked, not silently erased.

## Data, privacy, and backups

- `data\` can contain the SQLite database, WAL/SHM files, credentials, logs, attachments, backups, and exports.
- The authenticated loopback API uses a per-run credential tied to the current Windows user and running DevHub instance. The companion control wrapper resolves it automatically without printing it.
- Credential-shaped settings are protected with Windows DPAPI for the current Windows profile.
- On launch, DevHub creates that day's database backup and portable exports if needed. In **Settings → Backups and portable exports**, use **Back up now** for a database backup or **Export Markdown + JSON** for readable copies. Use **backups** and **exports** to open the results.
- Database backups contain attachment records but not sibling attachment bytes. Back up `ticket-images\` and `ticket-files\` separately.
- Portable exports omit secret settings but can still contain private project, contributor, Discord, build, knowledge, and evidence text. Review them before sharing.
- Use the supported API through `devhub-control`. Never edit `devhub.db` directly.

## Nine Codex skills

The complete suite is hosted on XA Docs, separately from the application repository. Choose by the outcome you want; install the full bundle to keep the shared control client with the workflow skills.

- [DevHub Add Project](https://xadocs.com/skills/library/devhub-add-project/SKILL.md): register a project and verify its complete settings.
- [DevHub Cleanup Tickets](https://xadocs.com/skills/library/devhub-cleanup-tickets/SKILL.md): review and apply approved title changes and duplicate merges.
- [DevHub Control](https://xadocs.com/skills/library/devhub-control/SKILL.md): transport authenticated API reads and writes.
- [DevHub Create Ticket](https://xadocs.com/skills/library/devhub-create-ticket/SKILL.md): create an evidence-grounded ticket with duplicate checks.
- [DevHub Development](https://xadocs.com/skills/library/devhub-development/SKILL.md): coordinate intent, implementation, verification, and handoff.
- [DevHub Implementation Confirmer](https://xadocs.com/skills/library/devhub-implementation-confirmer/SKILL.md): review selected tickets against current implementation evidence.
- [DevHub Interview](https://xadocs.com/skills/library/devhub-interview/SKILL.md): clarify essential request details or choose a collaborative review before filing.
- [DevHub Knowledge](https://xadocs.com/skills/library/devhub-knowledge/SKILL.md): maintain durable, evidence-backed knowledge.
- [DevHub Prioritize Tickets](https://xadocs.com/skills/library/devhub-prioritize-tickets/SKILL.md): rank requests by delivery effort and propose clearer titles; the current control contract permits proposals only.
- [DevHub Reports](https://xadocs.com/skills/library/devhub-reports/SKILL.md): prepare and manage grounded reports.
- [Nine-skill bundle](https://xadocs.com/downloads/devhub/xa-devhub-skills.zip): download the complete companion suite.

For an optional collaborative review, use the existing **Copy AI review bundle** action, paste its result into the agent session, and invoke `$devhub-interview` with collaborative review requested. It checks request clarity, a lean option, maintenance cost, and acceptance. Ordinary processing remains available; this adds no new application menu.

## Install the skills

1. Download the [ten-skill bundle](https://xadocs.com/downloads/devhub/xa-devhub-skills.zip) and verify its checksum against the website. Each skill's complete source is readable in the [library](https://xadocs.com/skills/).
2. For a standard Windows user installation, enter `%USERPROFILE%\.agents\skills` in File Explorer and create the folder if needed. Extract the ten `devhub-*` directories directly into it, retaining every nested file. Check existing copies before replacing customized skills. Avoid an extra `xa-devhub-skills` wrapper directory or doubled skill directory. Follow the [current Codex installation instructions](https://learn.chatgpt.com/docs/build-skills) for other locations.
3. In Codex CLI or the IDE extension, open `/skills` or type `$devhub-control`. Codex normally detects skills automatically; restart the Codex session if they do not appear. DevHub's **Codex skills** project field does not install them.
4. Start DevHub under the same Windows user, then use the Windows PowerShell health check below. A successful response confirms the connection. The client discovers the current credential automatically; the default needs no configuration file. Never paste API or Discord tokens into an AI prompt.

The extracted folders should include these paths; preserve all other bundled files too:

```text
%USERPROFILE%\.agents\skills\
|-- devhub-control\
|   |-- SKILL.md
|   |-- agents\openai.yaml
|   |-- references\api-contract.md
|   `-- scripts\devhub.ps1
|-- devhub-add-project\
|   `-- SKILL.md
`-- ...the remaining complete devhub-* folders
```

```powershell
$skillRoot = Join-Path $env:USERPROFILE '.agents\skills'
$dh = Join-Path $skillRoot 'devhub-control\scripts\devhub.ps1'
powershell -NoProfile -ExecutionPolicy Bypass -File $dh -Action health
```

For a custom port, use a matching `-BaseUrl` as documented in the [control skill](https://xadocs.com/skills/skill.html?name=devhub-control).

Try these as separate requests in Codex, replacing the example project with your own:

```text
$devhub-control Check health and list projects without making changes.
$devhub-add-project C:\Projects\MyApplication
$devhub-cleanup-tickets My Project
$devhub-prioritize-tickets My Project
```

Cleanup presents title and duplicate-merge proposals for approval. Prioritization currently returns ranking and title proposals without changes because priority updates are not supported by the public control API. Use `$devhub-implementation-confirmer` with a copied review bundle, or give `$devhub-development` the exact implementation task you want done.

## Update or move DevHub

1. Use **Settings → open data folder** to locate the current data, then close DevHub. Copy the entire folder to a separate backup location, including database companions and the `ticket-images` and `ticket-files` directories.
2. Retain that data while following the source-build instructions. If you have a portable binary package, replace the application files together while keeping your existing `data\` folder. Do not overwrite your records with an empty folder from another installation.
3. Reopen DevHub and check your projects and a recent ticket. Moving to another Windows user or machine may require re-entering credentials protected for the previous Windows profile.

`devhub.exe --data-dir "D:\DevHubData"` selects a different data location; it does not copy existing records. To uninstall, close DevHub, keep the data or exports you want, and remove the application folder.

## Troubleshooting

| Symptom | Next step |
| --- | --- |
| The ZIP has no `devhub.exe` | The source ZIP needs a build; the skills ZIP contains Codex instructions. Follow First launch and look in `build\Release` after a successful build. |
| Python is not recognized or a command exits immediately | Try `py -3 --version` in Windows PowerShell. Use that launcher or the full installed Python path in the saved command. Check the script name, quotes, working directory, and console error. Restart DevHub after a PATH change so it receives the new environment. |
| A command button is missing | Fill in its matching command under Edit project. Blank commands stay hidden. |
| Version comparison is missing or wrong | Set local version file, published version url, and any required published version key; refresh versions. The repository URL alone is not a version source, and editing a version does not rebuild the app. |
| Codex cannot find a skill | Check that its directory sits directly under the skills folder and contains SKILL.md. Preserve its supporting files. Check `/skills` and restart the Codex session if needed. |
| The control client cannot connect | Run DevHub under the same Windows user and try the read-only health check. Match a custom port to the API address in Settings; do not substitute a token copied from an earlier run. |
| Discord rejects an old card edit | Review Delivery failures. Dismiss old-message alerts hides the reviewed failures locally; Recreate in saved channel posts a replacement card when selected. This is separate from project-command errors. |
| Windows reports `MSVCP140.dll` or `VCRUNTIME140.dll` missing | Keep the application output together and install Microsoft's [Visual C++ Redistributable (x64)](https://aka.ms/vs/17/release/vc_redist.x64.exe). |

If the problem remains, record the DevHub version, action, expected result, and relevant error text. Remove private details and credentials before opening a [GitHub issue](https://github.com/xa-io/devhub/issues). Use the [security policy](https://xadocs.com/devhub/source/SECURITY.md) for vulnerabilities.

## Source and release history

The [source viewer](https://xadocs.com/devhub/source.html) and source ZIP contain the same 90 reviewed files derived from public GitHub revision `c49030f`, with the AGPL-3.0-or-later license and dependency notices. Private examples use neutral placeholders; copyright and project attribution are preserved. The source README is documentation captured with that snapshot; this guide covers current setup and use.

- [Source viewer](https://xadocs.com/devhub/source.html)
- [Source README](https://xadocs.com/devhub/source/README.md)
- [Changelog](https://xadocs.com/devhub/source/CHANGELOG.md)
- [License](https://xadocs.com/devhub/source/LICENSE)
- [Privacy](https://xadocs.com/devhub/source/PRIVACY.md)
- [Dependency notices](https://xadocs.com/devhub/source/THIRD_PARTY_NOTICES.md)
- [Reviewed source ZIP](https://xadocs.com/downloads/devhub/xa-devhub-source-1.0.6-c49030f-public.zip)
- [Exact package metadata](https://xadocs.com/ai/catalog.json)