Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
everyinc avatar

Ce Setup

  • 2.4k installs
  • 23.9k repo stars
  • Updated August 5, 2026
  • everyinc/compound-engineering-plugin

ce-setup checks Compound Engineering health and fixes repo-local config and gitignore issues.

About

The ce-setup skill is a lightweight Compound Engineering health check and repo-local configuration helper. Phase one detects the installed plugin version when available, runs the bundled check-health script or inline equivalents for optional tools like agent-browser, gh, jq, ast-grep, and ffmpeg, and reports missing capabilities without treating them as failures. It inspects git repos for obsolete compound-engineering.local.md, outdated config.local.example.yaml, and config.local.yaml files not covered by gitignore. Phase two fixes repo-local issues only with user approval: delete obsolete local markdown, refresh the example config from references/config-template.yaml, optionally create config.local.yaml, and append .compound-engineering/*.local.yaml to gitignore. The skill never bulk-installs optional dependencies and uses blocking question tools per platform instead of silent auto-configuration. disable-model-invocation is true, so users invoke it explicitly for onboarding or troubleshooting. Users invoke ce-setup explicitly because disable-model-invocation is true.

  • Runs bundled check-health or inline optional-tool diagnostics.
  • Reports missing tools as optional capabilities, not setup failures.
  • Removes obsolete compound-engineering.local.md with user approval.
  • Refreshes committed config.local.example.yaml from template.
  • Ensures config.local.yaml is gitignored before local prefs are saved.

Ce Setup by the numbers

  • 2,408 all-time installs (skills.sh)
  • +68 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #78 of 1,435 DevOps & CI/CD skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

ce-setup capabilities & compatibility

Capabilities
bundled or inline optional tool health diagnosti · obsolete local markdown detection and removal · example and local yaml config refresh from templ · gitignore verification for machine local setting · platform specific blocking question prompts
Use cases
devops · ci cd
From the docs

What ce-setup says it does

Missing optional tools are not setup failures.
SKILL.md
Never silently skip or auto-configure.
SKILL.md
npx skills add https://github.com/everyinc/compound-engineering-plugin --skill ce-setup

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs2.4k
repo stars23.9k
Security audit1 / 3 scanners passed
Last updatedAugust 5, 2026
Repositoryeveryinc/compound-engineering-plugin

Is Compound Engineering configured correctly and are local settings safely gitignored?

Check Compound Engineering health, refresh repo-local config examples, and safely gitignore machine-local settings.

Who is it for?

Onboarding a repo or troubleshooting missing optional Compound Engineering tools.

Skip if: Skip for bulk installing every optional dependency; the skill only reports gaps.

When should I use this skill?

User runs /ce-setup, verifies setup, or troubleshoots missing optional tools.

What you get

Diagnostic report plus optional repo-local fixes for example config and gitignore.

  • .compound-engineering/config.local.yaml
  • Configured delegation and pulse settings

By the numbers

  • Configures .compound-engineering/config.local.yaml with optional delegation and pulse settings
  • Supports sandbox modes yolo and full-auto for Codex work delegation

Files

SKILL.mdMarkdownGitHub ↗

Compound Engineering Setup

Interaction Method

Ask each question below using the platform's blocking question tool: AskUserQuestion in Claude Code (call ToolSearch with select:AskUserQuestion first if its schema isn't loaded), request_user_input in Codex, ask_question in Antigravity CLI (agy), ask_user in Pi (requires the pi-ask-user extension). Fall back to a numbered list in chat only when no blocking tool exists in the harness or the call errors. Never silently skip or auto-configure.

ce-setup is a lightweight health check and repo-local config helper. It does not bulk-install every optional dependency. Missing tools are reported as optional capabilities so the user can install only the workflows they use.

Phase 1: Diagnose

Step 1: Determine Plugin Version

Detect the installed compound-engineering plugin version by reading the plugin metadata or manifest when the platform exposes it. If the version cannot be determined, skip this step.

If a version is found, pass it to the check script via --version. Otherwise omit the flag.

Step 2: Run the Health Check

Before running the script, display:

Compound Engineering -- checking your environment...

Run the bundled check script when the skill directory can be resolved:

if [ -n "${CLAUDE_SKILL_DIR}" ] && [ -f "${CLAUDE_SKILL_DIR}/scripts/check-health" ]; then
  bash "${CLAUDE_SKILL_DIR}/scripts/check-health" --version VERSION
else
  echo "Bundled health script is unavailable on this platform; run the inline checks from ce-setup instead."
fi

Use the same command without --version VERSION if Step 1 could not determine a version.

If the script is unavailable, perform the inline equivalent:

1. Check optional tools with command -v: agent-browser, gh, jq, ast-grep, ffmpeg. 2. If inside a git repo, resolve the repo root with git rev-parse --show-toplevel. 3. Check for obsolete compound-engineering.local.md at the repo root. 4. Check whether .compound-engineering/config.local.yaml exists and, if it does, whether git check-ignore -q .compound-engineering/config.local.yaml succeeds. 5. Compare .compound-engineering/config.local.example.yaml with references/config-template.yaml when the template is readable; otherwise report that the example refresh must be done manually.

Display the diagnostic output to the user. Missing optional tools are not setup failures.

Step 3: Decide Whether Fixes Are Needed

Proceed to Phase 2 only if one or more repo-local project issues exist:

  • obsolete compound-engineering.local.md
  • .compound-engineering/config.local.yaml exists but is not safely gitignored
  • .compound-engineering/config.local.example.yaml is missing or outdated

If no project issues exist, report:

✅ Compound Engineering setup complete

Project config: ✅
Optional capabilities: see diagnostic report above

Run /ce-setup anytime to re-check.

If optional tools are missing, do not offer a bulk install. The diagnostic already printed the relevant install command or project URL. Say: "Install optional tools only for the workflows you use."

Phase 2: Fix Repo-Local Issues

Resolve the repository root (git rev-parse --show-toplevel). All paths below are relative to the repo root, not the current working directory.

Step 4: Remove Obsolete Local Config

If compound-engineering.local.md exists at the repo root, explain that it is obsolete because review-agent selection is automatic and surviving machine-local settings now live in .compound-engineering/config.local.yaml.

Ask whether to delete it now. Delete only if the user approves.

Step 5: Refresh Example Config

Copy references/config-template.yaml to <repo-root>/.compound-engineering/config.local.example.yaml, creating the directory if needed. This file is committed to the repo and should always reflect the latest available settings.

If the bundled template cannot be located by the current platform, print the source template path that failed and tell the user the example config could not be refreshed automatically.

Step 6: Create Local Config If Wanted

If .compound-engineering/config.local.yaml does not exist, ask:

Set up a local config file for this project?
This saves optional Compound Engineering preferences such as output formats, product pulse settings, and Codex delegation defaults.
Everything starts commented out -- you only enable what you need.

1. Yes, create it
2. No thanks

If the user approves, copy references/config-template.yaml to <repo-root>/.compound-engineering/config.local.yaml.

Step 7: Ensure Local Config Is Gitignored

If .compound-engineering/config.local.yaml exists and is not covered by .gitignore, offer to add:

.compound-engineering/*.local.yaml

Append the entry to the repo-root .gitignore only if the user approves. Do not overwrite unrelated .gitignore content.

Phase 3: Summary

Display a brief summary:

✅ Compound Engineering setup complete

Fixed:     <repo-local fixes applied, or none>
Skipped:   <repo-local fixes declined, or none>
Optional:  <missing optional tools, or all available>

Run /ce-setup anytime to re-check.

Related skills

How it compares

Pick ce-setup over editing ~/.codex/config.toml alone when you need per-project Compound Engineering delegation and product pulse configuration.

FAQ

Does ce-setup install all optional tools?

No. It reports missing optional capabilities and prints install hints for workflows you use.

What repo issues trigger fixes?

Obsolete compound-engineering.local.md, outdated example config, or local yaml not gitignored.

Can it auto-configure silently?

No. It uses blocking questions and applies fixes only after user approval.

Is Ce Setup safe to install?

skills.sh reports 1 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.