@manhnv319/codexkit
v0.1.8
Published
Project-local Codex workspace kit for clean umbrella-repo workflows, recommended skills, agents, hooks, plans, docs, scripts, and Python runtime selection.
Maintainers
Readme
Codex Kit
Project-local Codex setup for serious multi-repository workspaces.
Codex Kit installs a curated Codex workspace layer with skills, agents, hooks, workflow rules, helper scripts, plan templates, output styles, and project documentation. It is designed for umbrella repositories that contain many child repos: keep the operational knowledge in the parent workspace, while Codex can still reason about and work across the child projects cleanly.
Why Use Codex Kit?
Most AI coding setups become messy in monorepos or workspace folders because each child repository starts accumulating its own plans, docs, scripts, and agent configuration. Codex Kit solves that by letting the umbrella folder act as the coordination layer.
- Keep
plans,.codex/docs,.codex/scripts, rules, hooks, and templates in the selected top-level target instead of scattering files across child repos. - Wrap child repositories from the parent workspace so Codex can work across the whole system without polluting every project.
- Choose the exact target at setup time: install into the umbrella folder, or intentionally install into a specific child project when that is what you want.
- Select skills, agents, hooks, and Python runtime from an interactive terminal UI.
- Auto-detect project signals and recommend relevant skills and agents.
- Pin a shared Python environment, such as
~/.venv/shared/bin/python, so Codex scripts do not accidentally use system Python. - Install guardrails for privacy checks, scout blocking, development-rule reminders, plan/cook workflow reminders, and post-edit simplification.
- Preserve existing project conventions by writing managed sections instead of replacing user-owned content.
Install
npm install -g @manhnv319/codexkitCheck that the CLI is available:
ckit --helpQuick Start
From the umbrella folder that contains your repositories:
cd ~/Documents/projects/my-workspace
ckitRunning ckit with no arguments is equivalent to:
ckit --target .By default, this opens the interactive selector. Use the arrow keys to move,
Space to select/toggle, and Enter to apply.
Interactive Setup
The selector includes these tabs:
Target: choose the umbrella folder or a detected child project.Python: chooseautoor a detected Python interpreter.Skills: choose installed Codex skills.Agents: choose Codex agent roles.Hooks: choose runtime hooks and guardrails.Review: confirm the final setup before applying.
The Python tab scans common locations on macOS, Linux/Ubuntu, and Windows,
including project .venv, ~/.venv, ~/.venv/shared, ~/.virtualenvs,
~/.pyenv/versions, Conda environments, Windows Python installs, and system
fallbacks. The selected value is stored in .codex/.ck.json as
python.runner.
Recommended Umbrella Setup
Use this when one folder contains multiple repositories and you want Codex workspace files to live only in the parent folder:
cd ~/Documents/projects/my-workspace
ckitIn the Target tab, keep . selected. This installs Codex Kit into the current
workspace folder. Plans, docs, scripts, rules, hooks, and templates stay in that
selected target.
Use this mode when you want a clean child-repo structure with no extra kit files inside each application/service repository.
Preview Changes
ckit --target . --dry-run --detailsThis prints detected project signals, recommendations, selected skills/agents, selected hooks, the Python runner, and planned file actions without writing anything.
Apply Without the Selector
ckit --target . --yesPin a shared Python interpreter:
ckit --target . --python ~/.venv/shared/bin/python --yesUse auto-detection explicitly:
ckit --target . --python auto --yesChild-Project Installs
If you intentionally want to install Codex Kit into a child repository, choose
that child project in the Target tab or pass it directly:
ckit --target ./backend-serviceThis is useful when a child repository is worked on independently and should own
its own .codex, .agents, plans, and AGENTS.md setup.
Batch Mode
Preview detected child repositories:
ckit --all-projects --dry-run --detailsApply to detected child repositories:
ckit --all-projects --yesBatch mode is intentionally different from the recommended umbrella setup. It
installs .codex and .agents configuration into each detected child project.
Use it only when you actually want child repositories to receive their own kit
files.
Profiles
ckit --target . --profile default
ckit --target . --profile minimal --yes
ckit --target . --profile all --yesdefault: core kit plus project-specific recommendations.minimal: smaller setup with essential workflow skills and guardrails.all: install every available migrated skill, agent, and hook.custom: start from explicit selections passed through CLI flags.
Example custom setup:
ckit --target . \
--profile custom \
--with-recommended \
--skills react-best-practices,tanstack,backend-development \
--agents planner,tester,code_reviewer \
--hooks privacy,scout,dev-rules \
--python ~/.venv/shared/bin/python \
--yesUseful Commands
ckit --list
ckit --target . --suggest-only
ckit --target . --dry-run --details
ckit --target . --repair-hook-wrappersWhat It Installs
.agents/skills.agents/skillssupport files such ascommon/,install.sh, andINSTALLATION.md.codex/agents.codex/hooks.codex/rules.codex/scripts.codex/output-styles.codex/docs.codex/.ck.json.codex/config.toml.codex/hooks.jsonplans/templates- a managed Codex Kit block in
AGENTS.md
Configuration Highlights
Codex Kit stores project preferences in .codex/.ck.json, including:
paths.plans: where plan directories and reports should be created.paths.docs: where docs should be maintained.python.runner: selected Python interpreter orauto.hooks: enabled/disabled hook preferences.plan: naming, report, and validation behavior.
Notes
Use ckit --target . for the clean umbrella-repo workflow. Use
ckit --all-projects only when you intentionally want to apply the kit to
detected child repos.
After applying Codex Kit, restart Codex in the target workspace so the new skills, agents, hooks, and rules are loaded.
License
MIT License. See LICENSE for details.
