Post review gate
Adam gets a timed chance to look at every post that goes out under his name, and his silence never blocks the work. Draft to a file, alert him, wait up to five minutes, post whatever the file says, write it down.
Pairs with adams-voice (how the text reads) and claude-attribution (how Claude's words are marked). This skill only governs the handoff: file, alert, wait, post, record.
Scripts live in this skill's scripts/ directory (~/.claude/skills/post-review-gate/scripts/ once installed).
The workflow
Draft to a file. Write the exact text to ~/Downloads/<context>-<kind>.md: gutenberg-81397-comment.md, trac-62345-ticket.md, wpd-9012-review-reply.md, my-skills-post-review-gate-pr.md. The file holds only what will be posted, attribution header and block quote included. No preamble, no notes to Adam, no "let me know" - those go in chat.
Alert and wait, in the background.
bash ~/.claude/skills/post-review-gate/scripts/wait-for-review.sh ~/Downloads/gutenberg-81397-comment.md
Run it with run_in_background: true. It watches the file for five minutes. The alert is the terminal bell and nothing more: Claude Code rings it when the turn ends (preferredNotifChannel is terminal_bell in ~/.claude/settings.json), and iTerm shows it. No macOS notifications, no sounds, no PushNotification, no phone push; Adam finds those obtrusive.
Then tell Adam in chat: the path, that he can edit it in place, delete it to veto, or ignore it and it posts in five minutes. Never block on the script. Finish any other step that is ready, then end the turn so the bell rings. The script's result arrives as a notification and the workflow resumes from step 3.
Act on the first signal.
| Signal |
Do this |
review |
Script prints TIMEOUT |
Post as drafted. |
unreviewed |
Script prints EDITED |
Post the file exactly as it is now on disk. (Also printed when an edit is still in progress two minutes past the deadline.) |
edited |
Script prints DELETED |
Do not post. Say so in chat and move on. |
- |
| Adam tells you to post it in chat ("post it", "go ahead", "looks good, ship it") |
Post now. Stop the waiter with TaskStop. |
approved |
| Adam asks for changes in chat |
Revise the file, run the waiter again. Fresh five minutes. |
- |
Post from the file. Re-read it from disk immediately before posting. The file is the source of truth, not the version drafted in the conversation - Adam edits in place and may not mention it.
Record it, then report it.
bash ~/.claude/skills/post-review-gate/scripts/log-post.sh comment "WordPress/gutenberg#81397" <url> unreviewed ~/Downloads/gutenberg-81397-comment.md
Kinds: comment, review-reply, issue, pr, trac-ticket, trac-comment. The log is ~/.claude/posts-log.md. Give Adam the URL in chat, and say whether it went out reviewed or not.
Short replies skip the file and the wait, not the record. A short reply is one sentence that states something Adam already knows or has already decided: a commit hash, a thanks, a merge, a "done" ("Updated in a1b2c3d.", "Thanks, merging."). It posts directly with no draft file and is logged with review: short and no draft path. A reply that carries an opinion, a claim about the code, or a question goes through the gate however short it is.
Guardrails
- Five minutes, then post. No manual sleeps, no re-running the waiter to "give Adam more time", no ending the turn with the draft unposted and no waiter running. The whole point is that Adam being busy does not stall the task.
- The waiter fired but the post already went out (Adam approved in chat first): if you already have the URL for this post, do nothing. Do not use the draft path in the log as the test; draft filenames are reused, so an older entry can match.
- No file, no gated post. When Adam says "just post it" about something longer than a short reply before a draft exists, still write the file, post from it, and log it as
approved. Cheap next to a comment that cannot be unsent.
- Log before reporting. If the log line fails, fix it before handing over the URL. A post that is not in the log did not happen as far as "what have you posted for me" is concerned.
- Approval is a reply about the post, not about the work. "Looks good, go ahead" after you named the draft is approval. "Looks good" about the code, the diff, or the task, with no reference to posting, is not. When in doubt, the timer decides.
"What have you posted for me today?"
bash ~/.claude/skills/post-review-gate/scripts/show-posts.sh # today
bash ~/.claude/skills/post-review-gate/scripts/show-posts.sh 2026-09-01 # one day
bash ~/.claude/skills/post-review-gate/scripts/show-posts.sh all # everything
Present the entries as a list with links. Call out anything marked unreviewed so Adam knows which posts went out without his eyes on them.
Log line shape:
- 16:52 PDT | comment | WordPress/gutenberg#81397 | https://github.com/WordPress/gutenberg/pull/81397#issuecomment-123 | review: unreviewed | draft: ~/Downloads/gutenberg-81397-comment.md
Rationalizations that mean stop and follow the workflow
| Thought |
Reality |
| "Adam is probably busy, better to wait until he answers." |
Waiting indefinitely is the failure this skill replaces. Five minutes, then post. |
| "This one is too important to post unreviewed." |
Adam set the timeout knowing he might not respond. Post it. The unreviewed flag in the log tells him to look. |
| "It's quick, I'll just paste it in chat and ask." |
A draft in chat cannot be edited in place and leaves no record. Write the file. |
| "I already posted, no need to log it." |
The log is how Adam finds out what went out under his name. Log it. |
| "I'll post first and write the file after." |
The file is what Adam edits and what the waiter watches. File first, always. |
1---2name: post-review-gate3description: Use before posting anything under Adam's name that runs longer than a sentence or two - a GitHub issue, PR description, issue or PR comment, code review reply, Trac ticket or Trac comment - and whenever Adam asks what Claude has posted on his behalf (today, this week, ever).4---56# Post review gate78Adam gets a timed chance to look at every post that goes out under his name, and his silence never blocks the work. Draft to a file, alert him, wait up to five minutes, post whatever the file says, write it down.910Pairs with adams-voice (how the text reads) and claude-attribution (how Claude's words are marked). This skill only governs the handoff: file, alert, wait, post, record.1112Scripts live in this skill's `scripts/` directory (`~/.claude/skills/post-review-gate/scripts/` once installed).1314## The workflow15161. **Draft to a file.** Write the exact text to `~/Downloads/<context>-<kind>.md`: `gutenberg-81397-comment.md`, `trac-62345-ticket.md`, `wpd-9012-review-reply.md`, `my-skills-post-review-gate-pr.md`. The file holds only what will be posted, attribution header and block quote included. No preamble, no notes to Adam, no "let me know" - those go in chat.17182. **Alert and wait, in the background.**19 ```20 bash ~/.claude/skills/post-review-gate/scripts/wait-for-review.sh ~/Downloads/gutenberg-81397-comment.md21 ```22 Run it with `run_in_background: true`. It watches the file for five minutes. The alert is the terminal bell and nothing more: Claude Code rings it when the turn ends (`preferredNotifChannel` is `terminal_bell` in `~/.claude/settings.json`), and iTerm shows it. No macOS notifications, no sounds, no PushNotification, no phone push; Adam finds those obtrusive.2324 Then tell Adam in chat: the path, that he can edit it in place, delete it to veto, or ignore it and it posts in five minutes. Never block on the script. Finish any other step that is ready, then end the turn so the bell rings. The script's result arrives as a notification and the workflow resumes from step 3.25263. **Act on the first signal.**2728 | Signal | Do this | `review` |29 |---|---|---|30 | Script prints `TIMEOUT` | Post as drafted. | `unreviewed` |31 | Script prints `EDITED` | Post the file exactly as it is now on disk. (Also printed when an edit is still in progress two minutes past the deadline.) | `edited` |32 | Script prints `DELETED` | Do not post. Say so in chat and move on. | - |33 | Adam tells you to post it in chat ("post it", "go ahead", "looks good, ship it") | Post now. Stop the waiter with TaskStop. | `approved` |34 | Adam asks for changes in chat | Revise the file, run the waiter again. Fresh five minutes. | - |35364. **Post from the file.** Re-read it from disk immediately before posting. The file is the source of truth, not the version drafted in the conversation - Adam edits in place and may not mention it.37385. **Record it, then report it.**39 ```40 bash ~/.claude/skills/post-review-gate/scripts/log-post.sh comment "WordPress/gutenberg#81397" <url> unreviewed ~/Downloads/gutenberg-81397-comment.md41 ```42 Kinds: `comment`, `review-reply`, `issue`, `pr`, `trac-ticket`, `trac-comment`. The log is `~/.claude/posts-log.md`. Give Adam the URL in chat, and say whether it went out reviewed or not.4344**Short replies skip the file and the wait, not the record.** A short reply is one sentence that states something Adam already knows or has already decided: a commit hash, a thanks, a merge, a "done" ("Updated in a1b2c3d.", "Thanks, merging."). It posts directly with no draft file and is logged with `review: short` and no draft path. A reply that carries an opinion, a claim about the code, or a question goes through the gate however short it is.4546## Guardrails4748- **Five minutes, then post.** No manual sleeps, no re-running the waiter to "give Adam more time", no ending the turn with the draft unposted and no waiter running. The whole point is that Adam being busy does not stall the task.49- **The waiter fired but the post already went out** (Adam approved in chat first): if you already have the URL for this post, do nothing. Do not use the draft path in the log as the test; draft filenames are reused, so an older entry can match.50- **No file, no gated post.** When Adam says "just post it" about something longer than a short reply before a draft exists, still write the file, post from it, and log it as `approved`. Cheap next to a comment that cannot be unsent.51- **Log before reporting.** If the log line fails, fix it before handing over the URL. A post that is not in the log did not happen as far as "what have you posted for me" is concerned.52- **Approval is a reply about the post, not about the work.** "Looks good, go ahead" after you named the draft is approval. "Looks good" about the code, the diff, or the task, with no reference to posting, is not. When in doubt, the timer decides.5354## "What have you posted for me today?"5556```57bash ~/.claude/skills/post-review-gate/scripts/show-posts.sh # today58bash ~/.claude/skills/post-review-gate/scripts/show-posts.sh 2026-09-01 # one day59bash ~/.claude/skills/post-review-gate/scripts/show-posts.sh all # everything60```6162Present the entries as a list with links. Call out anything marked `unreviewed` so Adam knows which posts went out without his eyes on them.6364Log line shape:6566```67- 16:52 PDT | comment | WordPress/gutenberg#81397 | https://github.com/WordPress/gutenberg/pull/81397#issuecomment-123 | review: unreviewed | draft: ~/Downloads/gutenberg-81397-comment.md68```6970## Rationalizations that mean stop and follow the workflow7172| Thought | Reality |73|---|---|74| "Adam is probably busy, better to wait until he answers." | Waiting indefinitely is the failure this skill replaces. Five minutes, then post. |75| "This one is too important to post unreviewed." | Adam set the timeout knowing he might not respond. Post it. The `unreviewed` flag in the log tells him to look. |76| "It's quick, I'll just paste it in chat and ask." | A draft in chat cannot be edited in place and leaves no record. Write the file. |77| "I already posted, no need to log it." | The log is how Adam finds out what went out under his name. Log it. |78| "I'll post first and write the file after." | The file is what Adam edits and what the waiter watches. File first, always. |
adamsilverstein