Repository navigation
feat: add bounded human-voice review - #4
Merged
Merged
Conversation
what: Add an explicit, repository-guided human-voice pass to the Zola editorial reference, planning records, provenance note, and review scenario. why: Bring the useful Zensical tone-review boundary to Zola without imposing a house style, phrase ban, or automated gate.
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.
what: Add an optional, repository-guided human-voice pass to Zola editorial review, with matching planning and scenario records.
why: Preserve technical author voice while catching clustered AI-like prose without imposing a house style or phrase ban.
validation: bash tests/run.sh; python3 scripts/check_commit_messages.py HEAD; npx --yes skills-ref validate skills/zola; git diff --check.