Humanize README prose - #231
Merged
Merged
Conversation
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
1 participant
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.
What changed
What stayed the same
Commands, links, pattern tables, quoted examples, numbers, and release notes are unchanged. This is a prose-only documentation edit with no change to the skill's 35 patterns or runtime behavior.
Why
The README should model the writing style that Humanizer asks agents to produce. Several passages still used the tidy lists, repeated framing, and polished summary cadence that the skill is designed to remove.
Validation
git diff --checkpython3 scripts/validate-package.pypython3 skill-creator/scripts/quick_validate.py .origin/main