taurean.bryant.land
a template starter repo for sveltekit projects
docs(kickoff): wire the pi-review secret during Step 8
Every fork needs MINIMAX_API_KEY before pi-review.yml can run; repo
secrets don't inherit. Step 8 now sets it right after the remote is
created (op read from 1Password piped to gh secret set) and the hand-back
checklist verifies it — or it's carried as an unchecked follow-up item
when op is unavailable or the remote was deferred.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
author
Taurean Bryant
co-author
Claude Fable 5
date
(Jul 3, 2026, 11:28 AM -0700)
commit
8e869ab4
8e869ab4ccac367f835da65b9a3af1d74771619c
parent
ff79c4a3
ff79c4a3d89d75821bec5474255833e28abc9589
+12
-1
+12
-1
.pi/skills/suede-kickoff/SKILL.md
+12
-1
.pi/skills/suede-kickoff/SKILL.md
···
126
126
git checkout -b chore/suede-kickoff
127
127
```
128
128
129
-
The follow-up PR's description is the audit trail. Step 4 created no remote, so ask the human: if they want one now, create it (`gh repo create`, confirming visibility with them) and open the draft PR (with a placeholder diff — a `chore: open PR for follow-up` commit on the new branch is fine). If not, write the same content to `tmp/KICKOFF-FOLLOWUP.md` (gitignored) and open the PR from it when a remote lands. Either way, capture:
129
+
The follow-up PR's description is the audit trail. Step 4 created no remote, so ask the human: if they want one now, create it (`gh repo create`, confirming visibility with them) and open the draft PR (with a placeholder diff — a `chore: open PR for follow-up` commit on the new branch is fine). If not, write the same content to `tmp/KICKOFF-FOLLOWUP.md` (gitignored) and open the PR from it when a remote lands.
130
+
131
+
Immediately after the remote exists, wire the review workflow's secret — `.github/workflows/pi-review.yml` is inert without it:
132
+
133
+
```bash
134
+
op read "op://Private/Minimax Subscription Key/key" --account family-passvault.1password.com | gh secret set MINIMAX_API_KEY
135
+
```
136
+
137
+
If `op` isn't available or the human deferred the remote, list the secret as an unchecked item in the follow-up PR description (or `tmp/KICKOFF-FOLLOWUP.md`) instead — don't let it silently drop.
138
+
139
+
Either way, capture:
130
140
131
141
- The human's answers verbatim from Step 3 (both Thread A and Thread B).
132
142
- The commit hash from Step 1 (audit trail).
···
156
166
- `cat package.json` shows `suede.from` set to the tag from Step 1.
157
167
- `.deciduous/` does not exist.
158
168
- The follow-up PR is open on `chore/suede-kickoff` with the process-layer edits list in the description (or `tmp/KICKOFF-FOLLOWUP.md` holds it, if the human deferred the remote).
169
+
- `gh secret list` shows `MINIMAX_API_KEY` (or the secret is an unchecked item in the follow-up description, if the remote was deferred).
159
170
- `pnpm install` succeeds (the bootstrap is mechanical; if it broke something, the follow-up task will surface it).