diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-07 09:32:39 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-07 09:32:39 -0500 |
| commit | 5bee32b3e11dfc8fa3eefa589a8fc18932abaa79 (patch) | |
| tree | 2829a7ad66b2c30ed38014b03de2117eb7bc8137 /.claude/commands/start-work.md | |
| parent | fd3eda377aee1e797fa4bcf975d656ec25d66bd0 (diff) | |
| download | rulesets-5bee32b3e11dfc8fa3eefa589a8fc18932abaa79.tar.gz rulesets-5bee32b3e11dfc8fa3eefa589a8fc18932abaa79.zip | |
chore: migrate humanizer callers to /voice personal
I switched the three publish subflows in commits.md (commit messages, PR descriptions, PR review comments) from "run humanizer; apply five personal-style passes in order" to a single "run /voice personal" invocation. The new skill walks 39 patterns in one editorial review and absorbs the five passes wholesale, plus four more personal-style additions (felt-experience cut, fragment-in-prose rewrite, terse cut, public-artifact scope flag) and six universal good-writing patterns. The numbered steps in each subflow collapse from 5 to 4 (commits) and 9 to 8 (PRs) since the dedicated personal-style step folds into the voice invocation.
The Multi-pass gate paragraph becomes a Single-skill gate. The mid-flow "all the passes" prompt now means re-run the full 39-pattern walk in personal mode rather than reapplying six discrete steps.
I also updated respond-to-cj-comments.md to invoke /voice personal for public writing and /voice general for the lighter pass on internal notes when wanted, and updated start-work.md's Phase 7 summary to match.
The humanizer skill itself stays in place for now. The next commit removes it.
Diffstat (limited to '.claude/commands/start-work.md')
| -rw-r--r-- | .claude/commands/start-work.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/.claude/commands/start-work.md b/.claude/commands/start-work.md index bf32801..2224490 100644 --- a/.claude/commands/start-work.md +++ b/.claude/commands/start-work.md @@ -236,9 +236,9 @@ If deviations are significant, the user may want to loop back and revise the app Follow `commits.md` exactly. Summary of the flow: 1. Run `/review-code --staged` before each commit, or `/review-code` on the whole branch before the PR. Block on Critical or Important findings. -2. Draft the commit message to `/tmp/commit-<slug>.md`. Run `humanizer`. Apply the plain-English pass. Replace semicolons. Stop for approval. +2. Draft the commit message to `/tmp/commit-<slug>.md`. Run `/voice personal`. Stop for approval. 3. After approval, commit. -4. Draft the PR body to `/tmp/pr-<ticket-or-slug>.md`. Body must include a `Linear:` or equivalent cross-link line. Run `humanizer`. Apply the plain-English pass. Replace semicolons. Stop for approval. +4. Draft the PR body to `/tmp/pr-<ticket-or-slug>.md`. Body must include a `Linear:` or equivalent cross-link line. Run `/voice personal`. Stop for approval. 5. After approval, push and run `gh pr create`. 6. Post the PR URL back to the Linear ticket, GitHub issue, or todo.org entry. 7. Move the Linear or GitHub status to **Dev Review**. Todo.org has no equivalent. Leave the todo.org entry as `DOING` until the PR merges. |