capture-configlisted

Use when a hand-edit to a machine-level agent config should become permanent and available everywhere — the user edited ~/.claude/settings.json, ~/.claude/CLAUDE.md, ~/.codex/AGENTS.md, ~/.cursor/, ~/.gemini/ or ~/.config/opencode/ by hand and says 'make this permanent', 'save this to the repo', 'keep this setting', 'add this rule everywhere', 'sync my machine back to the repo', 'capture my config', 'I tweaked a permission, don't lose it', 'put this on all my platforms' — or when setup/doctor reports the machine has drifted from the repo and the machine is the side that is right. Offer it proactively right after helping the user hand-edit one of those files. It classifies each difference (portable / machine-local / secret / third-party / unknown), refuses credentials, blocks employer references, and produces a reviewed PR. It never merges.
Tamircohen28/tamirs-superpowers · ★ 2 · Code & Development · score 74

Install: claude install-skill Tamircohen28/tamirs-superpowers

# capture-config Propose a machine's hand-edits back into this repo, as a reviewed pull request. `scripts/setup.sh` renders repo → machine. This is the inverse: machine → repo. Your job is to run it, read the classified change set with the user, and hand the result to `pr-dev`. **You do not decide what is portable — the script classifies, and the user answers.** ## Why this is not automatic Rendering only ever writes files this repo authored. Capture reads files a *person* edited, so a run can pick up a credential, a path that exists only on one laptop, or another tool's wiring. That is why nothing is adopted without an explicit answer, why secrets are refused rather than skipped, and why the result is a PR and never a commit. Do not try to shortcut any of that. ## When to offer it Offer it — do not wait to be asked — when: - you have just helped the user hand-edit `~/.claude/settings.json`, `~/.claude/CLAUDE.md`, `~/.codex/AGENTS.md`, `~/.cursor/`, `~/.gemini/` or `~/.config/opencode/`, and the change reads like policy rather than a one-off - `scripts/doctor.sh` or `setup.sh plan` reports repo/machine drift **and the machine is the side that is right** - the user says a setting "keeps getting lost" between machines Do **not** offer it for a repo-scoped `.claude/settings.json`, and do not offer it when the repo is right and the machine is stale — that is `make setup`. ## The three steps ### 1. Look first, always ```bash bash scripts/capture-config.sh detect `