.vale.ini

StylesPath = styles
MinAlertLevel = warning
Vocab = vale-ai-tells

Packages = Google, write-good, proselint

[*.md]
BasedOnStyles = Vale, Google, proselint, write-good, \
  ai-tells, ai-tells-experimental
# Repo docs use run-in bold labels ("**Note:** ..."), which ColonUsage
# flags once Vale strips the markup.
ai-tells.ColonUsage = NO
ai-tells-experimental.HeadingTitleCase = NO
Google.Colons = NO
Google.Headings = NO
Google.Passive = NO
Google.Semicolons = warning
Google.We = NO
write-good.E-Prime = NO
write-good.Passive = NO

[README.md]
BasedOnStyles = Vale, Google, proselint, write-good, \
  ai-tells, ai-tells-experimental
ai-tells.ColonUsage = NO
ai-tells.FormalRegister = NO
ai-tells-experimental.HeadingTitleCase = NO
Google.Colons = NO
Google.Headings = NO
Google.Passive = NO
Google.Semicolons = warning
Google.We = NO
write-good.E-Prime = NO
write-good.Passive = NO

# COMMIT_AGENTMSG is the repo-root draft `mise run lint-commit-msg` reads,
# and SQUASH_AGENTMSG the one `mise run lint-squash-msg` reads before a
# squash merge. None of the three carries a suffix, and vale keys [formats]
# on a file extension, so no entry here can name a parser for them:
# `COMMIT_AGENTMSG = md`, `.COMMIT_AGENTMSG = md`, and `* = md` each leave
# the buffer parsed as plain text. This file used to carry a [formats] block
# claiming otherwise. It was inert on every path that runs, and its comment
# is where the wrong assumption reached the repotools vale-commit-msg hook.
#
# Plain-text parsing is why a backticked CLI flag still trips DoubleHyphen
# in a commit message while it stays clean in a document: nothing strips the
# code span, so the backticks are ordinary characters. The parser has to be
# named at the vale invocation with `--ext=.md`, which the hook owns rather
# than this file. See TODO.md.

# The glob covers the drafting paths and the buffer git hands the hook,
# each in the root and .git/ form the tools use. A squash message becomes
# a commit like any other, so it answers to the same styles.
[{COMMIT_EDITMSG,.git/COMMIT_EDITMSG,COMMIT_AGENTMSG,.git/COMMIT_AGENTMSG,SQUASH_AGENTMSG,.git/SQUASH_AGENTMSG}]
BasedOnStyles = ai-tells, ai-tells-commits
# Commit bodies use run-in bold labels ("- **Rule**: Catches ..."), the
# convention the changelog is generated from, and the trailer pair
# (Assisted-by:/Signed-off-by:) reads the same way to ColonUsage.
ai-tells.ColonUsage = NO

[{styles/**/*.md,tmp/**/*.md,.repotools/**,.config/mise/conf.d/**}]
BasedOnStyles =
# Rule-level overrides from [*.md] (Google.Semicolons = warning) leak into
# this section because Packages loads them globally. BasedOnStyles = clears
# the style binding but not the inherited rule level; suppress explicitly.
Google.Semicolons = NO

# Skill and rule prose under .claude/ is agent-facing documentation, not
# this project's docs. Most of it arrives from tbhb/repotools pinned by
# content hash in apm.lock.yaml, where upstream owns the wording; the
# glob covers this repo's own doc-lint and release skills too, whose
# numbered-step headings otherwise trip Google.HeadingPunctuation for no
# gain. The `**` reaches the references/ subtrees the newer skills ship
# alongside their SKILL.md.
[{.claude/rules/worktree-wip.md,.claude/skills/**/*.md}]
BasedOnStyles =
Google.Semicolons = NO