test(lint-skills): cover check_skill and check_command, not just settings

The linter's main job - frontmatter keys, allowed-tools targets, the
command title rule - had zero assertions; deleting the missing-
allowed-tools error left the suite green. The fixture's yaml stub now
parses the flat frontmatter the fixtures write instead of returning a
canned mapping, and four new cases pin both check functions.
Mutation-verified against the real linter. Review finding F23
(2026-08-19).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Mads Lorentzen
2026-08-19 19:59:22 +02:00
co-authored by Claude Opus 5
parent c20458d768
commit 9a074b262d
2 changed files with 74 additions and 2 deletions
+6
View File
@@ -15,6 +15,12 @@ per-file diff commands.
### Added
- **Tests for `lint_skills.py`'s skill and command checks** - only `check_settings()`
had coverage; the linter's main job (frontmatter keys, `allowed-tools` targets
existing, the `# /<name>` command title rule) was unasserted, so deleting the
missing-allowed-tools error survived the whole suite. Four new cases in
`tests/test_lint_skills.py`, with the fixture's yaml stub upgraded to parse the real
frontmatter. Mutation-verified.
- **Discriminating tests for `robots_check`'s tie-break and browser-UA fallback** - the
existing tie test put Disallow first, the one ordering that cannot detect deletion of
the tie-break clause; and the browser-readback recovery that `09-web-research.md`