mirror of https://github.com/Donchitos/Claude-Code-Game-Studios.git synced 2026-10-16 01:37:05 +00:00

Files

T

DonchitosandClaude Opus 5.5 be8993bbc5 Release 1.1.3 — long skills keep their later steps

Fix release for 1.1.2: the 14 longest skills keep their later phases
after a compaction, a question nobody answered is never taken as an
answer, settings read the same from a subfolder, the commit check works
for a project in a subfolder of a larger repository, every skill opens
with a title, and the shipped allow rules no longer approve deleting a
branch or writing files without asking. Details in CHANGELOG.md; upgrade
steps in UPGRADING.md (v1.1.2 → v1.1.3).

Refs #83
Refs #133

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0185en4t76fPn7315q4c3nko

2026-10-08 17:52:48 +11:00

1.6 KiB

Raw Permalink Blame History

/smoke-check — Phase 3: Check Test Coverage

Part of /smoke-check. SKILL.md names when to read this file; the settings it resolved and the rules under its later headings still apply here.

Phase 3: Check Test Coverage

Draw the story list from, in priority order:

The QA plan found in Phase 1 (its Test Summary table lists expected test file paths per story)
The current sprint plan from production/sprints/ (most recently modified file)
If the quick argument was passed, skip this phase entirely and note: "Coverage scan skipped — run /smoke-check sprint for full coverage analysis."

For each story in scope:

Extract the system slug from the story's file path (e.g., production/epics/combat/story-001.md → combat)
Glob tests/unit/[system]/ and tests/integration/[system]/ for files whose name contains the story slug or a closely related term
Check the story file itself for a Test file: header field or a "Test Evidence" section

Assign a coverage status to each story:

Status	Meaning
COVERED	A test file was found matching this story's system and scope
MANUAL	Story type is Visual/Feel or UI; a test evidence document was found
MISSING	Logic or Integration story with no matching test file
EXPECTED	Config/Data story — no test file required; spot-check is sufficient
UNKNOWN	Story file missing or unreadable

MISSING entries are advisory gaps. They do not cause a FAIL verdict but must appear prominently in the report and must be resolved before /story-done can fully close those stories.

1.6 KiB Raw Permalink Blame History

/smoke-check — Phase 3: Check Test Coverage

Phase 3: Check Test Coverage

1.6 KiB

Raw Permalink Blame History