One function
check_description_conformance in tw93/Waza
The author described this change as “fix: polish skill descriptions”. It counts as a record because the check below fails on the code as it stood at a0c6d2b4c and passes on fcc21e93f, with nothing else changed between the two runs.
Projecttw93/Waza
Fix saved2026-06-19
Sharing licenceMIT · LICENSE
Change size+5 −0
What the code was meant to do, written into the code itself as a docstring
Every skill needs a triggerable opening, a 'Use when' cue, a 'Not for' exclusion, and a sane length. Locks the convention so new skills can't drift into vague descriptions that agent resolvers can't match before they read when_to_use.
The change
| 28 | 28 | f"DESCRIPTION MISSING EXCLUSION CLAUSE: {skill}\n" | |
| 29 | 29 | f" Must contain a 'Not for ...' clause so the resolver learns when NOT to fire. Got: {clean[:120]!r}" | |
| 30 | 30 | ) | |
| 31 | + | if CJK_RE.search(clean): | |
| 32 | + | fail( | |
| 33 | + | f"DESCRIPTION CONTAINS CJK: {skill}\n" | |
| 34 | + | f" Keep public-facing description metadata English-only. Put multilingual trigger phrases in when_to_use." | |
| 35 | + | ) | |
| 31 | 36 | print(f"ok: description {skill} ({length} chars)") |
The check that tells the two apart
fail→pass·tests/python/test_skill_checks.py::test_description_rejects_cjk_triggers
Check file tests/python/test_skill_checks.py, taken without changes from the fix and copied onto the older code, so the exact same check runs against both versions.
Origin and history
The code before ita0c6d2b4c6eb458a1e25ca3fc6b885e9349b98ce
Broken version dated2026-06-18
Modulescripts.skill_checks
Units changedcheck_description_conformance
Fingerprint03fe24b9a92f355d
Checked2026-08-18 by goldset/0.1
Every field above is generated by our program. None of it is written by hand.