docs(humanizer): reconcile with blader/humanizer upstream, v0.3 -> v0.4 - #28
Draft
yulonglin wants to merge 1 commit into
Draft
docs(humanizer): reconcile with blader/humanizer upstream, v0.3 -> v0.4#28yulonglin wants to merge 1 commit into
yulonglin wants to merge 1 commit into
Conversation
Reviewed upstream blader/humanizer (33 patterns) and folded in the genuinely new ones. 25 -> 31 patterns, 7 -> 8 categories. New patterns: - Knowledge-cutoff disclaimers (97%) - Promotional language / puffery (84%) - Superficial '-ing' significance clauses (86%) - Decorative emoji (88%), excessive boldface (78%), Title Case headings (72%) New category 8: Formatting Tells - presentation-layer signals that survive paraphrasing, so they still fire on lightly-edited LLM prose. Key decision: adopted upstream's patterns but NOT its philosophy. blader is a rewriter that mandates stripping every em-dash; we stay a detector with frequency-based em-dash scoring (1-2/page fine, 3+/page a signal). Recorded in a new 'Deliberately Rejected' table alongside diff-anchored writing (out of scope) and copula avoidance (deferred - no characterisation precise enough to hit the >90% precision bar). Also fixes a three-way drift: the patterns JSON had gone stale at 15 patterns while the doc and agent carried 25, and the agent claimed both 25 and 23 in different sections. This doc is now the canonical source and names its two derived consumers inline.
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Reviewed upstream blader/humanizer (now 33 patterns, up from 24 at first analysis) and folded in the genuinely new ones.
25 -> 31 patterns, 7 -> 8 categories.
New patterns
-ingsignificance clausesCategory 8 (Formatting Tells) covers presentation-layer habits rather than word choice. These survive paraphrasing, so they still fire on lightly-edited LLM prose.
Key decision: patterns yes, philosophy no
blader/humanizer is a rewriter that transforms text and mandates stripping every em-dash. This is a detector that flags and scores. Patterns port across that boundary; the em-dash policy does not.
Kept the frequency-based stance: 1-2 em-dashes per page is normal human writing, 3+ per page is the signal. Adopting zero-tolerance would tank precision against the >90% target.
Added a "Deliberately Rejected" table so the reasoning survives:
Drift fix
The three artifacts had diverged:
claude/docs/humanizer-patterns.mdai-safety-pluginsagent promptai-safety-pluginspatterns JSONThis doc is now the canonical source and names its two derived consumers inline, so the fix is structural rather than a one-time sync.
This PR contains the dotfiles doc only. The two derived artifacts in
ai-safety-pluginsare regenerated and validated locally but uncommitted - that repo was never isolated into a worktree, so it needs a look before committing.Verification
Counts checked programmatically across all three: per-category declared vs actual, category totals, and header claims all agree at 31 / 8. JSON parses.
https://claude.ai/code/session_01HZxdsbK7sYFNJCP8VyBSDj