Files
cc-ci-orchestrator/.opencode/skills/cctest-opencode-sync/SKILL.md
T
autonomic-bot be7f8bc850 cctest: unify merge policy wording — recipe PRs are never agent-merged, both sides
Operator decision: no policy difference between cc-ci and recipe-maintainer. On
inspection ARM already agrees (recipe-upgrade-cron-all: 'PRs are reviewed and merged
manually by a human afterwards... never merges anything'; 'no human review in the
middle' = skip the mid-run plan confirmation only). Wrappers previously framed this
as a cc-ci override over ARM auto-merge flows — wrong reading; now stated as ONE
unified rule. /help conventions updated to match.
2026-08-04 01:40:36 +00:00

1.7 KiB

name, description
name description
cctest-opencode-sync [recipe-maintainer/cctest] Ensure every Claude skill has a corresponding OpenCode skill alias (Wraps the autonomic-recipe-maintainer skill /opencode-sync; runs against the cctest test server + ARM sandbox, not cc-ci. Invoke as /cctest-opencode-sync.)

cctest-opencode-sync (cctest wrapper)

Canonical procedure: references/recipe-maintainer/.opencode/skills/opencode-sync/SKILL.md — read it and follow it. This wrapper only sets context + policy.

Context: this is an autonomic-recipe-maintainer (ARM) skill. It operates on the recipe-maintainer cctest test server / local abra sandbox — NOT on the cc-ci CI server or its shared swarm. Execute with the submodule as your working directory: cd /srv/cc-ci-orch/references/recipe-maintainer. If the ARM environment is not yet configured on this host (settings.toml from settings.toml.example, sandbox/test instances), run /cctest-intro / /cctest-setup-sandbox first.

Unified policy (same as cc-ci — no differences):

  • Recipe PRs are NEVER merged by an agent. Every flow ends at an open PR; the operator reviews and merges. This is ARM's own rule too ("PRs are reviewed and merged manually by a human afterwards — never pushes to upstream or merges anything"); ARM's "no human review in the middle" wording refers only to skipping the mid-run plan confirmation, not to merging.
  • Never touch cc-ci infrastructure (the CI server, its swarm, /root/* clones, the weekly timers) from an ARM skill — cc-ci work goes through the cc-ci skills.
  • The submodule is pinned: don't commit into it from here; upstream ARM changes arrive via a deliberate submodule bump + scripts/gen-cctest-skills.py regeneration.