mission-dev

Sets up mission development branches, workspaces, and branch indexing in ContextHub.

Updated May 12, 2026
One-click install
npx skills add https://github.com/contexthub-md/marketplace --skill mission-dev-contexthub-md
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mission-dev
Source: https://github.com/contexthub-md/marketplace/tree/main/contexthub/skills/mission-dev
Command: npx skills add https://github.com/contexthub-md/marketplace --skill mission-dev-contexthub-md

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting work on a ContextHub mission requires coordinating branch creation across multiple repos, checking out the right branches, and indexing changes for code intelligence. This Skill automates that setup so you can begin development immediately. ## Core Features & Use Cases - Mission Branch Setup: Creates or checks out mission/{mission_id} branches across all repos linked to a project, with manual fallback if automatic creation fails. - Branch Indexing: Triggers delta indexing on the mission branch so code changes are searchable via OCXP tools before merging. - Mission Lifecycle Tracking: Guides commit conventions with mission IDs, PR creation, and mission status updates through completion. - Use Case: You are assigned a mission titled "Project Observability". Run the skill to create the mission, check out its branch on every linked repo, index the branch, and start committing with traceable mission-tagged messages. ## Quick Start Ask the assistant to start development on a mission by saying "start mission-dev for the Project Observability mission on the ContextHub project".

Frequently Asked Questions about mission-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start development on a ContextHub mission?

Provide a mission ID or title to the mission-dev skill. It creates the mission if needed, checks out the mission/{mission_id} branch on all linked repos, and optionally indexes the branch for code search.

How are mission branches created in ContextHub?

Calling ch_create_mission triggers a background task that creates mission/{mission_id} branches on all repos linked to the project within about 30 seconds. If branches are missing, the skill creates and pushes them manually with git.

Can I search code changes on a mission branch before merging?

Yes. Run ch_trigger_index with the mission branch name to build a delta index on top of main, then use ch_ocxp_grep or ch_ocxp_search with the branch parameter to search your changes.

What happens if mission branches are not created automatically?

Missing branches usually indicate expired GitHub credentials. The skill falls back to manual creation: checkout main, pull, create the mission/{mission_id} branch, and push it to origin.

How do I complete a mission after finishing development?

Push all changes, create a PR from the mission branch to main, then call ch_update_mission with status completed and progress 100 after merge. Optionally delete the branch index with ch_delete_branch_index.