Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

conductor-worktree-setup

Estrelas4

Forks5

Atualizado27 de junho de 2026 às 02:10

Use when setting up, reviewing, or changing Cogni Conductor worktree bootstrap, including conductor.json, scripts/conductor-worktree-setup.sh, secret/auth symlinks, and AI launch-pack references for human or AI developers.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

cogni-dao

cogni-dao/cogni

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	conductor-worktree-setup
description	Use when setting up, reviewing, or changing Cogni Conductor worktree bootstrap, including conductor.json, scripts/conductor-worktree-setup.sh, secret/auth symlinks, and AI launch-pack references for human or AI developers.

Cogni Conductor Worktree Setup

Use this with the bundled Conductor app skill when a human asks how to run Cogni in Conductor or when changing the repo's worktree bootstrap.

Ground Truth

conductor.json wires Conductor setup to bash scripts/conductor-worktree-setup.sh.
scripts/conductor-worktree-setup.sh is the canonical setup script.
docs/guides/new-worktree-setup.md is the human-facing worktree guide.
.claude/skills/node-wizard-expert/SKILL.md and nodes/operator/app/src/features/nodes/launch-pack.ts are the launch-handoff references.

Human Flow

Set COGNI_TEMPLATE_ROOT to the primary checkout if it is not $HOME/dev/cogni-template.

In the primary checkout, update main before creating the Conductor workspace:

git -C "$COGNI_TEMPLATE_ROOT" checkout main
git -C "$COGNI_TEMPLATE_ROOT" pull --ff-only origin main

Create the Conductor workspace from that fresh base.
Let Conductor run the committed setup script.

The setup script also fetches origin/main and fast-forwards the primary checkout only when it is already on clean main. It must not rewrite the Conductor feature branch after workspace creation.

Invariants

Ensure the primary checkout has COGNI_NODE_API_KEY, then symlink .env.cogni and .local-auth from the primary checkout; never copy them into worktrees. Operator keys such as COGNI_API_KEY_PROD are for CI/CD authority and do not satisfy session cognition, so Conductor workspaces must not require manual key exports after the one-time node-agent registration bootstrap.
Keep pnpm install --offline --frozen-lockfile, pnpm packages:build, and pnpm worktree:check in the setup path.
If the setup contract changes, update the script, this skill, docs/guides/new-worktree-setup.md, and launch-pack wording together.

Mais deste repositório

mesmo repositório

manage-node-envs

cogni-dao/cogni

Manage which deploy-environments a Cogni node lives in (candidate-a / preview / production) via the operator app — the full request→owner-approve→verb→merge→verify loop for env (deploy-topology) membership. Use whenever an agent needs to add a node to an env or remove it from one, is asked to 'give this node a preview deploy', 'promote this node into production topology', 'take a node out of preview', 'stop deploying X to candidate-a', 'change a node's deploy reach / env set', 'onboard my node to an environment', or hits a 403 authz_denied / 503 authz_unavailable on POST /api/v1/nodes/{id}/envs. Also triggers on 'env_manager', 'can_manage_envs', 'env-membership PR', 'node deploy topology', 'catalog envs: line'. This is distinct from FLIGHTING a build (candidate-flight / can_flight) and from PROMOTING a sha (promote / can_promote_production) — env-membership changes WHERE a node is deployed, not WHICH build runs there. Do NOT use for provisioning a whole environment (that is provision-env), for secret-writes (

2026-07-174

node-to-candidate-a

cogni-dao/cogni

Take a Cogni node from NOT-deployed to live-and-validated on candidate-a, end to end, as a node-contributor agent — RBAC request → owner approve → env-membership verb (add candidate-a) → merge → Argo auto-reconcile → agent-api-validation. This is the cold-start runbook: a fresh agent with only its COGNI API key + a node id can follow it start to finish. Use when asked to 'get my node onto candidate-a', 'deploy node X to candidate-a', 'prove a node deploys e2e', 'add a node to the candidate environment', or to validate the env-membership verb against a real deployment. Distinct from node-setup (which BIRTHS a node into the registry — a prerequisite here) and from flighting/promoting a BUILD (candidate-flight / promote — which pick which image runs in an env you're already in). This picks the ENV itself, then proves the node actually deployed and answers.

2026-07-094

test-expert

cogni-dao/cogni

Authoritative reference for the cogni-template test pyramid and production-like e2e test topology — enforcement vs test layers, vitest configs, infra prereqs, GitHub/DoltHub test org boundaries, the cogni-operator-test app, what agents can/can't run locally, coverage tracking, and the non-obvious gotchas that bite every time. Use this skill whenever the user is writing a new test, asking "which layer does this belong in", debugging a flaky test, hitting CWD/env-loading issues, deciding between unit/component/stack/external, running any `pnpm test:*` or `pnpm arch:check` / `pnpm lint` command, working with testcontainers, touching fake adapters or `APP_ENV=test`, troubleshooting skip-gates, seeing errors from `.env.test` not loading, wondering about coverage or whether a test will run in CI, or trying to decide whether to run stack/e2e locally vs defer to CI. Also trigger when the user mentions mocking the database, Privy/GitHub App construction errors in tests, the smee proxy, `pnpm test:smee`, validating the

2026-07-094

devops-expert

cogni-dao/cogni

CI/CD architecture reviewer and DevOps advisor for monorepo pipelines, branch workflows, and deployment strategy. Use this skill when reviewing GitHub Actions workflows, designing promotion pipelines, evaluating branch protection rules, reviewing deploy scripts, auditing CI/CD for anti-patterns, or making decisions about build/test/deploy strategy. Also triggers for: 'review this workflow', 'is this CI pattern correct', 'branch strategy', 'deploy pipeline design', 'release promotion', 'should we use PRs for this', 'CI is slow', 'pipeline gap analysis', 'provision', 'deploy script'.

2026-06-304

payments-expert

cogni-dao/cogni

Use whenever working on Cogni USDC credit top-ups, payment intent creation, payment activation, operator wallet funding, 0xSplits allocations, x402 outbound provider payments, Hyperbolic, EIP-3009 signatures, retired OpenRouter/Coinbase top-ups, system-tenant revenue share, repo-spec payment config, live payment rail guards, payment CI failures, or debugging money-loop behavior. Trigger on phrases like payments, payment rail, credits top-up, USDC, Split, 0xSplits, splitHash, x402, Hyperbolic, facilitator, signX402Payment, EIP-3009, OpenRouter funding, Coinbase Commerce, operator wallet, Privy wallet, markup_factor, revenue_share, system bonus, provider top-up, settlement_skipped, SPLIT_CONFIG_MISMATCH, activate payments, node payments, or "is this payment behavior validated". This skill is the launching point for future payments work and debugging.

2026-06-284

node-setup

cogni-dao/cogni

Agentic node setup for Cogni forks. Orchestrates the full lifecycle: DAO formation, payment activation, repo identity, infrastructure provisioning, and deploy verification. Delegates to guide docs for step-by-step details.

2026-06-264

name	conductor-worktree-setup
description	Use when setting up, reviewing, or changing Cogni Conductor worktree bootstrap, including conductor.json, scripts/conductor-worktree-setup.sh, secret/auth symlinks, and AI launch-pack references for human or AI developers.

Cogni Conductor Worktree Setup

Use this with the bundled Conductor app skill when a human asks how to run Cogni in Conductor or when changing the repo's worktree bootstrap.

Ground Truth

conductor.json wires Conductor setup to bash scripts/conductor-worktree-setup.sh.
scripts/conductor-worktree-setup.sh is the canonical setup script.
docs/guides/new-worktree-setup.md is the human-facing worktree guide.
.claude/skills/node-wizard-expert/SKILL.md and nodes/operator/app/src/features/nodes/launch-pack.ts are the launch-handoff references.

Human Flow

Set COGNI_TEMPLATE_ROOT to the primary checkout if it is not $HOME/dev/cogni-template.

In the primary checkout, update main before creating the Conductor workspace:

git -C "$COGNI_TEMPLATE_ROOT" checkout main
git -C "$COGNI_TEMPLATE_ROOT" pull --ff-only origin main

Create the Conductor workspace from that fresh base.
Let Conductor run the committed setup script.

The setup script also fetches origin/main and fast-forwards the primary checkout only when it is already on clean main. It must not rewrite the Conductor feature branch after workspace creation.

Invariants

Ensure the primary checkout has COGNI_NODE_API_KEY, then symlink .env.cogni and .local-auth from the primary checkout; never copy them into worktrees. Operator keys such as COGNI_API_KEY_PROD are for CI/CD authority and do not satisfy session cognition, so Conductor workspaces must not require manual key exports after the one-time node-agent registration bootstrap.
Keep pnpm install --offline --frozen-lockfile, pnpm packages:build, and pnpm worktree:check in the setup path.
If the setup contract changes, update the script, this skill, docs/guides/new-worktree-setup.md, and launch-pack wording together.