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/c08-two-dot-is-not-ancestry/prompt.md
View on GitHub---
max_turns: 8
allowed_tools: [Read, Glob, Grep, Skill]
---
In the Puck repository, while verifying a lane against the landing bar, you concluded that the lane branch was cut from the current integration tip because `git log origin/integration..HEAD` listed only the lane's own commits. The lead asks if that is proof of the lane's base. Is it, and what commands do you run to test ancestry, find the actual base, and count how far behind the integration tip that base is?
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 |