test-naming-and-fixture-clarity

What problem does it solve? Test titles that describe the fixture setup instead of the failing condition mislead maintainers into trimming fixtures that look bloated, silently widening guards while tests still pass. This Skill keeps test names, fixture intent comments, and assertions aligned with the actual guard under test. ## Core Features & Use Cases - Condition-based naming: Rewrites test titles to state the rejected condition rather than the fixture state, so the fixture reads as required rather than padded. - Fixture intent comments: Adds in-test comments explaining which earlier guards each retained fixture part clears, preventing accidental removal during cleanup. - Guard-specific assertions: Pins each test to a message fragment unique to its guard instead of reusing one broad failure assertion. - Use Case: A Bats gate test titled "empty static dir" actually keeps a populated directory and removes only .js files to reach the no-JS guard; this Skill retitles it to the failing condition and documents why the populated fixture must stay. ## Quick Start Review this Bats gate test and rename it so the title states the failing condition while adding a comment explaining what the retained fixture parts clear.