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 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/"

Detect the test command:

• package.json with "test" script → npm test
• pytest.ini / conftest.py → pytest
• go.mod → go test ./...
• Cargo.toml → cargo test
• Gemfile + spec/ → bundle exec rspec

Step 3: Ask customization questions (conversational)

Ask the user three questions in sequence:

1. Audit focus — balanced / security-first / performance-first / quality-first (default: balanced)
2. Audit depth — mini (5 dimensions, faster) / full (9 dimensions) (default: mini)
3. Reasoning effort — high / medium / low (default: high)

Step 4: Generate .cc-suite.md

Write .cc-suite.md to the project root:

# CC-Suite Configuration

Project-specific settings for cc-suite commands.
Generated by `/cc-suite:init`. Edit freely — all fields are optional.

## Project

- **Stack**: {detected stack}
- **Test command**: {detected test command or "unknown"}
- **Source directories**: {detected dirs}

## Defaults

These override the built-in defaults for all commands in this project.
Remove a line to fall back to the built-in default.

- **Default model**: {current Codex model from $CODEX_MODEL env or leave blank}
- **Default effort**: {chosen effort}
- **Default audit type**: {chosen audit type}
- **Default sandbox**: workspace-write

## Audit Focus

{chosen focus}

Additional instructions appended to every audit's developer-instructions:

```text
{focus-specific instructions}

Skip Patterns

Files and directories to always skip during audits (glob patterns):

node_modules/
dist/
build/
coverage/
*.min.js
*.bundle.js
*.lock
vendor/
.git/

Project-Specific Instructions

Custom instructions appended to Codex's developer-instructions for every command.

{stack-specific default, e.g. "This is a Node.js project. Follow existing patterns in src/."}

Focus-specific instructions:
- **balanced**: "Give equal attention to all audit dimensions."
- **security-first**: "Prioritize security findings. Flag any auth bypass, injection, data exposure, or cryptographic weakness as Critical regardless of other severity heuristics."
- **performance-first**: "Prioritize performance findings. Flag N+1 queries, O(n²) algorithms, memory leaks, and blocking I/O as High regardless of other severity heuristics."
- **quality-first**: "Prioritize code quality findings. Flag untested critical paths, high cyclomatic complexity, and DRY violations as High regardless of other severity heuristics."

### Step 5: Bridge init

```bash
bash "${CLAUDE_PLUGIN_ROOT}/scripts/init.sh"

Creates AGENTS.md, CLAUDE.md (@AGENTS.md), GEMINI.md, .codex/config.toml, scaffold directories, and the .gitignore block. Skips each artifact if already correct.

Step 6: Expose skills

bash "${CLAUDE_PLUGIN_ROOT}/scripts/bridge_skills.sh"

Step 7: Register codex-cli MCP server

bash "${CLAUDE_PLUGIN_ROOT}/scripts/mcp_codex.sh"
bash "${CLAUDE_PLUGIN_ROOT}/scripts/bridge_mcp.sh"

Step 8: Register claude-code MCP server

bash "${CLAUDE_PLUGIN_ROOT}/scripts/mcp_claude.sh"

Step 9: Final status

bash "${CLAUDE_PLUGIN_ROOT}/scripts/status.sh"

Report:

cc-suite initialized

Bridge artifacts: {status summary}
Claude → Codex:  .mcp.json has codex-cli registered ✓
Codex → Claude:  .codex/config.toml has claude-code registered ✓
Project config:  .cc-suite.md written ({focus}, {depth}, effort={effort})

Next steps:
  Edit AGENTS.md to add project-specific conventions
  Run /cc-suite:audit-fix to test the full cycle
  Run /cc-suite:diagnose to verify health at any time
  Commit AGENTS.md, .cc-suite.md, .mcp.json to share with your team

Source: xiaolai/cc-suite — distributed by TomeVault.