gibson-setuplisted

Wire a repository for autonomous fleet development: install the Gibson guardrail bundle (AGENTS section, CI gates, labels, branch protection, kill switch) and connect the Devin cloud supervisor as merge captain. Consumes gibson-audit's gap list; idempotent. Third stage of the /gibson pipeline; also standalone ('set up this repo for the fleet', 'gibson-ify this repo', 'install the guardrails').
The-AIE/the-gibson · ★ 1 · AI & Automation · score 67

Install: claude install-skill The-AIE/the-gibson

# gibson-setup — teeth, not just prose An `AGENTS.md` alone is policy in prose; agents drift from it and nothing notices. This skill installs the ENFORCEMENT bundle so the rules are checked by machines. Source of truth: `templates/target-repo/` in the Gibson clone (currently thin — one file — plus the `ci/` workflows; be honest about that). When a target repo needs something the templates lack, write it for the target, then contribute the generalized version back to the Gibson **via a normal worktree branch + PR (Law 3: never edit the canonical clone directly)** so the next repo gets it for free. ## Install checklist (drive from the audit's gap list; skip what exists) 1. **AGENTS section** — append `templates/target-repo/AGENTS-section.md` to the target's `AGENTS.md` (create if absent). Never overwrite existing content. 2. **CI gates** — test/lint/typecheck/build on every PR, as required checks. Reuse the repo's existing CI if present; add the missing jobs only. **Verify every referenced script actually exists in the TARGET repo before installing any workflow from `ci/`.** `ci/gibson-gate.yml` runs `node scripts/check-active-work.mjs` (claim isolation, issue #55) and the protected **test-integrity** four-job path (issue #70) that grades with the merge-base copy of `scripts/test-integrity.mjs` only. Vendor **both** scripts into the target alongside the workflow. Calibrate `<generate>`/`<typecheck>`/ `<lint>`/`<test>`/`<build>` **and** set `TEST_CO