Humanizer: reduced size of the skill, trimmed some examples, prioriti…#19
Merged
Merged
Conversation
…sed removing em dashes and other tweaks
Contributor
Author
|
1, 2, 3, probando.... probando.... |
tute
approved these changes
May 20, 2026
Owner
|
Gracias! |
Owner
|
CI fallo con:
Pero no veo problema en mantener version ahi mismo. Por ahora hago merge igual. |
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.
Humanizer: shrink and reprioritize
Problem. The skill ran ~530 lines. The em-dash rule sat at place 14, and the model kept emitting em dashes anyway.
What changed.
How decisions were made. A 9-agent vote (3 Opus 4.7, 3 Opus 4.6, 3 Sonnet 4.6). Only unanimous and 8/9 cuts shipped in v0.2.5; 6-7/9 cuts shipped in v0.2.6 after manual review.
Outcome. The em-dash rule sits at the top. The full instruction set fits inside any plausible attention window.