feat: all 3 commands — gacp, lock, unlock

This commit is contained in:
2026-06-09 17:34:07 +02:00
parent 9fc2a6205a
commit a08d7a0223
3 changed files with 30 additions and 0 deletions
+12
View File
@@ -0,0 +1,12 @@
Git add, commit, and push. Run this workflow:
1. Run `git status` to see what's dirty/untracked.
2. Run `git diff --stat` for a summary of changes.
3. If there are untracked files that look unintentional (build artifacts, temp files, secrets), ask the user before staging them.
4. If there are mixed concerns (changes to unrelated files), ask whether to commit everything together or split into separate commits.
5. Stage all intended files with `git add`.
6. Write a concise commit message matching the repo's existing style (check `git log --oneline -5` for convention). Use conventional commits if the repo uses them.
7. Commit.
8. Push to the current tracking branch. If no upstream is set, ask which remote/branch to push to.
Be interactive — ask questions when something looks off, but don't over-ask on straightforward cases. If everything is clean and obvious, just do it.
+11
View File
@@ -0,0 +1,11 @@
Claim PRIME session lock. This makes the current session the exclusive recipient of:
- Incoming Signal messages (via signal-bridge)
- TTS playback rights
- Any other inbound comms routing
Steps:
1. Call `whoami_info` to get your session ID.
2. Write that session ID to `~/.local/state/opencode/prime.lock` (create parent dirs if needed).
3. Confirm: "PRIME locked to session {id}"
This always overwrites — no contention check, no confirmation needed. The current session becomes PRIME immediately.
+7
View File
@@ -0,0 +1,7 @@
Release PRIME session lock. Removes the lock file so no session is PRIME.
Steps:
1. Delete `~/.local/state/opencode/prime.lock` if it exists.
2. Confirm: "PRIME released — no active PRIME session"
Incoming Signal messages will route to a new HERALD session until someone runs /lock again.