open/repo-standard
1
0
Fork 0
Code Issues Releases 7 Activity

docs: the skill stopped contradicting itself about what a SKIP is

Browse source 
SKILL.md's opening list still glossed `SKIP` as "the check could not run" and
then contradicted itself five lines later, where 0.8.0 had added the two kinds.
A session reading only the list reports every deliberate skip as something that
failed to run, and sends someone to fix fixture links that are deliberate on
purpose. 0.7.1 exists because 0.7.0 shipped the same class of defect; this is
the check that was supposed to stop it happening twice.

README's `--offline` note and its bilingual-undecidable paragraph now name which
kind their skips are, and what resolves them. Both were true and incomplete —
incomplete in the one direction that matters now that the summary line names
only one of the two.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DHaQTcaD3w2C6PqVsAmrcv
This commit is contained in:
Kjell Tore Guttormsen 2026-08-09 21:55:58 +02:00
commit 9a566240e8
5 changed files with 31 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

19
CHANGELOG.md
View file

@ -4,6 +4,25 @@ All notable changes to this project are documented here.
Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/);
versioning is [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [0.8.1] — 2026-08-09
### Fixed
- `SKILL.md` glossed `SKIP` as "the check could not run" in its opening list and
then contradicted itself five lines later, where 0.8.0 had added the two
kinds. A session reading only the list would report every `byDesign` skip as
something that failed to run, and send someone to fix fixture links that are
deliberate. Shipping 0.7.0 without its skill update produced the same class of
defect; this is the check that was supposed to stop it happening twice.
- README's `--offline` note said the dependent checks "report `SKIP`, not `OK`"
without saying which kind, now that the summary line only names one of them.
They are `notRun` and clear on a networked re-run — an offline pass is never a
fully judged one, which is the whole reason the qualifier exists.
- README's bilingual-undecidable paragraph likewise names its kind, and the
action that resolves it.
## [0.8.0] — 2026-08-09
### Added