fix(lint): reword the two Vale errors this branch put where nothing lints
`Kyberforge.SentenceOpenerThereIs` is `level: error`, but `.vale.ini` scopes the style to `[**/SKILL.md]`, so no hook can see a violation in `references/`. This branch's own remedy — move prose out of the body into `references/` — is what carried these two there: - `provider-adapter-author/references/provider-matrix.md:31` - `agent-audit/references/finding-criteria.md:95` Both confirmed by copying the file to `SKILL.md` and running the audit's own `vale-wrap.sh`: 1 error each before, 0 after. Reworded to name the subject directly, which is what the rule asks for. Five further occurrences exist in `references/` files already on `main`. Those are the pre-existing corpus, not this branch's regression, and stay with #117 — which is the real fix: widen the Vale scope so the gate can see this class at all, and make the wrapper distinguish "0 alerts in 1 file" from "0 files matched". Source and generated mirror move together so the commit passes `check-plugin-content-sync` standalone. Refs: #117 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ktx4QJzTXZtw35m6T9WhcK
This commit is contained in:
@@ -28,5 +28,5 @@ This skill is reached two ways: invoked directly by a user, and composed into by
|
||||
once it has written or updated the repo's `AGENTS.md`. Behave identically either way — do not
|
||||
assume a caller skill exists. Detect the provider file yourself, confirm `AGENTS.md` yourself, and
|
||||
run the closeout validator yourself, rather than treating any step as already done by the caller or
|
||||
as something the caller will do afterwards. There is no handshake to rely on and no state passed
|
||||
in beyond the file paths.
|
||||
as something the caller will do afterwards. No handshake exists to rely on, and no state is
|
||||
passed in beyond the file paths.
|
||||
|
||||
@@ -28,5 +28,5 @@ This skill is reached two ways: invoked directly by a user, and composed into by
|
||||
once it has written or updated the repo's `AGENTS.md`. Behave identically either way — do not
|
||||
assume a caller skill exists. Detect the provider file yourself, confirm `AGENTS.md` yourself, and
|
||||
run the closeout validator yourself, rather than treating any step as already done by the caller or
|
||||
as something the caller will do afterwards. There is no handshake to rely on and no state passed
|
||||
in beyond the file paths.
|
||||
as something the caller will do afterwards. No handshake exists to rely on, and no state is
|
||||
passed in beyond the file paths.
|
||||
|
||||
Reference in New Issue
Block a user