init

Init

Bootstrap cc-suite in the current project.

When to Use

• Setting up a project for the first time
• Re-initializing after cloning a repo that already has AGENTS.md
• Walks through the same setup flow as /cc-suite:init — useful when the agent should drive the steps in conversation rather than via a slash command

Workflow

Step 0: Resolve the plugin root

CLAUDE_PLUGIN_ROOT is set by Claude Code only — in a Codex or Antigravity session it is unset. Resolve the root from the bridged skills symlink (it points at <plugin-root>/skills/cc-suite):

PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-$(dirname "$(dirname "$(readlink -f .claude/skills/cc-suite 2>/dev/null)")")}"
[ -d "${PLUGIN_ROOT}/scripts" ] || echo "! cannot resolve the cc-suite plugin root — run /cc-suite:bridge-skills from Claude Code first, or export CLAUDE_PLUGIN_ROOT"

Every command below uses ${PLUGIN_ROOT}. Stop if it could not be resolved.

Step 1: Check for existing config

[ -f .cc-suite.md ] && echo "exists" || echo "missing"

If it exists, read it and ask the user:

• Show — display the file and stop
• Regenerate — replace with a fresh config (proceed through questions)
• Cancel — keep as-is and stop

Step 2: Detect project stack

Run these checks to build the stack description:

[ -f package.json ]                                   && echo "node"
[ -f requirements.txt ] || [ -f pyproject.toml ]      && echo "python"
[ -f go.mod ]                                         && echo "go"
[ -f Cargo.toml ]                                     && echo "rust"
[ -f Gemfile ]                                        && echo "ruby"
[ -f pom.xml ] || [ -f build.gradle ]                 && echo "java"
ls *.csproj *.sln 2>/dev/null                         && echo "dotnet"
[ -f jest.config.js ] || [ -f vitest.config.ts ]      && echo "jest/vitest"
[ -f pytest.ini ] || [ -f conftest.py ]               && echo "pytest"
[ -d src ]  && echo "src/"
[ -d lib ]  && echo "lib/"
[ -d app ]  && echo "app/"