Skip to content

btseytlin/ultrapack / skills/try

Manually test the latest change with one realistic positive case and one adversarial negative case, capturing evidence before any further fix. Use when the user asks for a quick confidence check or wants to test a recent implementation.

Fast manual test

Use this as the Codex and Pi equivalent of /up:try.

  1. Identify the latest relevant change from the conversation and git status.
  2. Design exactly two fast probes: one realistic happy path and one likely misuse or edge case that should fail or be rejected.
  3. Run both and capture their actual output. Do not fix unexpected failures before reporting them.
  4. Report exactly:
Pos: [PASS/FAIL] — <what happened>
Neg: [PASS/FAIL] — <what happened>
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 318kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 318kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 318kUpdated Claude CodeCodexVerifiedInstall
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: 196kUpdated Claude CodeCodexVerifiedInstall