Mission control import codebase
Skill MN755/Codex-Mission_Control/plugins/mission-control/skills/mission-control-import-codebase
Import or attach an existing codebase into Mission Control. Use when the workspace already contains a repo and Codex should let Mission Control scan, understand, and classify it before edits.From its SKILL.md
npx -y skills add MN755/Codex-Mission_Control --skill mission-control-import-codebaseAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.5 KB, 470 tokens by cl100k_base, as published. Nobody here has run it
Mission Control Import Codebase
Purpose
Import an existing repo safely and let Mission Control build understanding before execution.
The Codex chat agent is not the Mission Control Manager. It is the bridge between the user and the Mission Control Manager.
Use when
- The folder is non-empty and looks like a real codebase.
- The user wants Mission Control to take over an existing repo.
- You need codebase understanding before planning or writing.
Workflow
- Attach the current workspace with
mission_control_attach_workspace. - Use
mission_control_import_existing_codebaseor the import prompt path for non-empty folders. - Request a read-only scan first.
- Retrieve the codebase map and understanding summary.
- Ask whether to skip interview, quick clarify, full interview, or let the Manager decide.
- Start the requested task only after the understanding path is chosen.
Mission Control calls
Tools:
mission_control_attach_workspacemission_control_import_existing_codebasemission_control_get_statusmission_control_start_task
Resources:
mission-control://projects/{project_id}/codebase-mapmission-control://projects/{project_id}/statusmission-control://projects/{project_id}/pending-decisions
User-facing output
- Summarize what Mission Control learned about the stack and entry points.
- Show the available intake choices: skip, quick clarify, full interview, or Manager decides.
- Report the project identifier and safest next step.
Approval behavior
Ask before any write-capable step, import permission change, or interview-skipping choice that materially changes assumptions.
Never do
- Do not run builds, installs, or tests during initial scan unless the user explicitly wants that.
- Do not expose
.envcontents or secrets. - Do not skip understanding and jump into edits.
Failure and fallback
If import tooling is missing, attach the workspace, explain that import-specific tooling is expected or future, and rely on read-only codebase resources where available. If Mission Control registered but only partial MCP capabilities exposed, say that exact bridge limitation before falling back.
Example invocation
Attach this existing repo to Mission Control, scan it read-only, and then let the Manager decide how to proceed.
What ships with it: 1 file
161 B alongside SKILL.md
agents/
- openai.yaml161 B