diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-07 09:36:14 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-07 09:36:14 -0500 |
| commit | 9858611afcdf848b6e483ba78f89c576aa5c8743 (patch) | |
| tree | e46cc1049ef12d54faebddb4cb3f035bef2259b5 /.ai/workflows | |
| parent | 5bee32b3e11dfc8fa3eefa589a8fc18932abaa79 (diff) | |
| download | rulesets-9858611afcdf848b6e483ba78f89c576aa5c8743.tar.gz rulesets-9858611afcdf848b6e483ba78f89c576aa5c8743.zip | |
chore(skills): remove humanizer (superseded by voice)
I deleted humanizer/SKILL.md now that all three callers (commits.md, respond-to-cj-comments.md, start-work.md) invoke /voice instead. The 25 humanizer patterns live on as patterns 1-25 in voice/SKILL.md. Same source (Wikipedia's Signs of AI writing), same prose, same examples — just renumbered alongside the universal good-writing additions and the personal-only patterns.
I also updated .ai/notes.org and .ai/workflows/wrap-it-up.org to reference /voice personal instead of the old humanizer + manual-passes flow. The wrap-it-up change landed upstream in claude-templates first so it survives the next startup rsync.
todo.org gets the matching update: the voice TODO is marked DONE with a "Built and shipped" timestamp, the publish-mode terminology is renamed to personal-mode throughout, the V1 scope checklist is ticked, the open questions are resolved with the answers we landed on during implementation, and the migration section records the delete-not-alias decision.
Diffstat (limited to '.ai/workflows')
| -rw-r--r-- | .ai/workflows/wrap-it-up.org | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/.ai/workflows/wrap-it-up.org b/.ai/workflows/wrap-it-up.org index 37d2522..5c5dc89 100644 --- a/.ai/workflows/wrap-it-up.org +++ b/.ai/workflows/wrap-it-up.org @@ -119,7 +119,7 @@ Commit message rules (also see protocols.org "Git Commit Requirements"): *Wrap-up commits skip the inline-approval gate.* The =commits.md= rule that requires writing the message to =/tmp/commit-<slug>.md=, printing inline, and waiting for an approve / request-changes / open-in-editor response does *not* apply to wrap-up commits. The wrap-up flow is meant to be quick — Craig has already authorized the wrap by triggering the workflow ("wrap it up"), and stopping again to approve a commit message disrupts the cadence. -Still apply the prose-quality passes silently before committing — humanizer + jargon-rewrite + semicolon-swap + contractions + sentence-split — so the message reads cleanly. Just don't print and ask. Commit directly with the cleaned message. +Still apply =/voice personal= silently before committing so the message reads cleanly. Just don't print and ask. Commit directly with the cleaned message. If a wrap-up commit needs Craig's eyes for a content reason (sensitive change, unusual scope, something he flagged earlier), surface it explicitly. Otherwise commit and move on. |