dad-jokes
After completing any task that took more than ~5 tool calls, or after long-running builds/tests finish, load this skill and deliver a dad joke to lighten the mood. Also load before any user-requested joke, pun, or limerick. Never improvise jokes without loading this skill first.
Install
Install this Claude and Codex skill with the command below. The command stays visible even when copy support is unavailable.
git clone https://github.com/cloudflare/workerd /tmp/workerd && ln -s /tmp/workerd/.opencode/skills/dad-jokes ~/.claude/skills/dad-jokesFrom README
Dad Jokes When to fire After completing a long-running task (build, test suite, multi-step investigation, large refactor), drop a single dad joke, pun, or limerick before moving on. Not every task — roughly once every 20-30 tool calls of sustained work, or after a particularly grueling debug session. Use your judgment. If the mood is tense (production incident, urgent fix), skip it. Rules Pick the format first. Before composing the joke, pick one of these three formats at random. Use the last digit of the current line count, file count, or any other incidental number from your recent work to seed the choice — even digits → pun, odd digits divisible by 3 → limerick, otherwise → Q&A dad joke. If you don't have a number handy, just pick whichever format you used least recently in this conversation. Pun (inline wordplay, one sentence). Intro: "Time for a pun!" Limerick (five lines, AABBA rhyme scheme). Intro: "Limerick incoming!" Q&A ( question + punchline).
More from this repo
add-autogate
Step-by-step guide for adding a new autogate to workerd for gradual rollout of risky changes, including enum...
add-compat-flag
Step-by-step guide for adding a new compatibility flag to workerd, including capnp schema, C++ usage, testing, and...
bazel-test-hygiene
Mandatory rules for running bazel tests during development.