ByteTerrace/Puck / .claude/skills/verification
verification
VerifiedVerifies Puck changes: landing bar, builds, stale DLLs, flaky tests, GPU/heavy leases, coverage, source-scan or regex laws versus type/compiler enforcement, and writing tests.
evals/c13-scan-law-cannot-fail/prompt.md
View on GitHub---
max_turns: 8
allowed_tools: [Read, Glob, Grep, Skill]
---
When verifying a C# change in the Puck repository (`tests/Puck.World.Tests`), a test law enforces "every consumer is handed a `Foo`" by scanning C# source files for calls that omit the `foo:` argument using a regular expression. During verification, a reviewer shows a real C# call site the regular expression cannot see, so deleting the argument there escapes the law. Under Puck's verification rules, how do you fix this?
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |