coily adopt: one-shot bootstrap so new repos pick up coily conventions #66
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally filed by @coilysiren on 2026-04-26T23:17:15Z - https://github.com/coilysiren/coily/issues/18
Problem
Coily already ships the pieces that make a repo "coily-aware":
coily lockdownwrites per-repo.claude/settings.jsondenies that force ops through coily.coily lockdown skillregenerates thecoily-passthroughsSKILL so Claude has the offline manifest.coily gh .../coily aws .../coily kubectl ...are the audited entry points.But applying them is manual and per-repo, and Kai keeps forgetting to run them when standing up (or returning to) a repo. The result is that sessions land in a repo and reach for bare
gh/aws/kubectl, bypass the audit log, and (on Desktop, where the deny list is read but not enforced) silently succeed. Exactly the failure mode lockdown was meant to prevent.Proposal
A single
coily init(name TBD:coily bootstrap,coily setup,coily adoptare all candidates) that, run once from a repo root, applies the full coilysiren-convention bundle:coily lockdown(settings.json denies + PreToolUse hook).coily lockdown skill(regen passthroughs SKILL)..pre-commit-config.yamltrufflehog entry if missing.coily ghnotgh").Open questions
initcollides withgit initsemantics (creates something new).adoptorenrollreads more accurately, it's pulling an existing repo into the coily regime, not creating one. Lean towardadopt.Makefiletargets (make checkinper the daily-checkin discussion), or is that out of scope and a separate per-repo thing?coily adopt --checkmode that just reports what would change, for use in a daily sweep across allcoilysiren/*repos? Pairs naturally with repo-recall surfacing "this repo isn't coily-adopted" as a signal.Why this matters
The lockdown story only works if lockdown is actually applied. A one-command bootstrap removes the "I forgot" failure mode and makes it cheap to keep every repo in the workspace consistent. Also unblocks treating coily-adoption as a checkable invariant (CI lint, repo-recall signal) rather than a per-repo memory task.