Conversation
The Voice section let a sample override every pattern. A sample that carries tells therefore taught the rewrite to keep them, and human writing keeps absorbing AI habits, so the writer's own text is not proof that it is clean. Mark the sample's tells first and act on one of three results: follow a clean sample in full, take only surface traits from a sample with scattered tells, and refuse one with a tell in every paragraph. Report the result before returning anything else. Also points the dash override at §8, its number since 3.0.0 (blader#273).
There was a problem hiding this comment.
🟡 Changes recommended
The sample fallback rule contradicts the scattered-tells behavior, and the README omits two preserved voice traits.
Get a fresh assessment by requesting another Copilot review.
Pull request overview
This PR adds voice-sample screening before style matching and synchronizes the package version to 3.1.0.
Changes:
- Classifies samples as clean, scattered-tell, or heavily tainted.
- Documents the new behavior and release.
- Updates package metadata versions.
File summaries
| File | Description |
|---|---|
| SKILL.md | Adds sample screening and voice-handling rules. |
| README.md | Documents behavior and version 3.1.0. |
| .claude-plugin/plugin.json | Updates the plugin version. |
Review details
- Files reviewed: 3/3 changed files
- Comments generated: 2
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| - **A few scattered tells.** Follow the sample's sentence length, formality, punctuation rate, openings, transitions, and subject vocabulary. It licenses no pattern below. | ||
| - **A tell in every paragraph.** Do not use it. Tell the writer the sample reads as AI-written, name two or three tells you found, and ask for another. | ||
|
|
||
| A sample written before November 30, 2022 is not AI-written. Work without a sample rather than follow one that carries tells. |
| ``` | ||
|
|
||
| Humanizer follows the sample's rhythm, word choice, punctuation, and deliberate quirks, including dashes if you use them. | ||
| Humanizer checks the sample for AI patterns first, then says what it found. A clean sample sets the voice in full, including dashes if you use them. A sample with a few tells sets sentence length, formality, punctuation rate, and vocabulary, but licenses no pattern. A sample with a tell in every paragraph is refused, so pick writing you know is your own: anything from before November 30, 2022 is safe. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Voice section says the sample outranks every pattern:
So a sample that carries tells teaches the rewrite to keep them. The skill already
says human writing keeps absorbing AI habits, which means "the writer wrote it"
is not proof the sample is clean. Anyone who drafts with an assistant and then
pastes their own recent writing as a voice sample gets the tells locked in.
This is a real path, not a hypothetical: the writer reaches for a sample to make
the output sound like them, and recent writing is the easiest sample to find.
Change
Mark the sample's tells first, then act on one of three results:
The result is reported before anything else, so the writer knows which reference
was used. The pre-2022 date already in "When not to act" is repeated here, since
that is where a writer picks a sample.
No pattern is added, removed, or renumbered. 25 patterns, unchanged.
Also in this change
The Voice line pointed the dash override at §6. Dashes have been §8 since 3.0.0
(#273). The rewritten line says §8. Happy to drop that part and rebase if #274,
#276, or #285 lands first.
Checks
python3 scripts/validate-package.py→Humanizer package v3.1.0 is validclaude plugin validate .→✔ Validation passednpx skills add . --list→Unknown command: "skills"on npm 11 here. Lookslike a local npx resolution problem rather than anything in this change; happy
to retry if you have a working invocation.
Version bumped to 3.1.0 in
SKILL.md,README.md, andplugin.json, with aREADME release note, per AGENTS.md.