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 wa

Files1

View on GitHub

SKILL.md

GitHub

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>

Related in other

limits-colimits

Context management for Claude Code. Hooks maintain state via ledgers and handoffs. MCP execution without context polluti...

by parcadei
3,392

ddttom-allaboutv2-claude-skills-block-collection-and-party

The Block Collection and Block Party are repositories for existing AEM blocks, build tools, code snippets, integration p...

by mattnigh
20

nodnarbnitram-claude-code-extensions-claude-skills-esphome-confi

This skill should be used when the user asks to "create an esphome config", "set up an esp32 device", "configure esphome...

by mattnigh
20