J0r33

Beat 3 — Development skill for Claude Code

Development community

Beat 3 — Prove it.

How to install Beat 3

Installs to ~/.claude/commands/j0r33-agentic-workflow-beat-3.md

Terminal

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/J0r33/agentic-workflow/HEAD/.claude/commands/beat-3.md -o ~/.claude/commands/j0r33-agentic-workflow-beat-3.md

Restart Claude Code, or start a new session, for it to be picked up.

What Beat 3 does

description: Beat 3 — Prove it. Run the local gates, then prove the change in the running app using a fixed menu keyed to what the diff touches. argument-hint: [optional note on which flows to exercise]

/beat-3 — Prove it

The third of the five beats in `AGENTS.md`. Beat 2 must already have run: the work is built and committed.

The proof step below is a **fixed menu keyed to what the diff touches**, not a judgement call. Most tickets in a real product are migrations, server functions

Alternatives in Development

Dashclaw Quality — Recurring find-and-fix quality pass over the whole DashClaw app — browser smoke (frontend-verify) + code gates 297 ★
Quosparr — 🐦 Native menu bar & tray app for macOS, Windows and Linux: track Codex, Claude Code and Grok quotas, resets 288 ★
Pair Verify — Use after you fix a bug and before you claim it fixed — it spawns ONE skeptic sibling session via CCC that mus 130 ★