ClaudeHack

Testing / Debugging

6 hacks

  1. 1.
    Verify frontend work in a real browser with Claude in Chrome(code.claude.com)

    Connect the Claude in Chrome extension so Claude can open your app, click through flows, read console errors, and iterate until the UI actually works.

    0 points·13 hours ago·intermediate·discuss
  2. 2.
    Build a verification-loop skill that must run tests before done(claude.com)

    Create a skill that forces a red→green verification loop so Claude cannot claim done without running the suite.

    0 points·13 hours ago·medium·discuss
  3. 3.
    Append /simplify after edits for a multi-agent quality pass(support.claude.com)

    End implementation prompts with /simplify so parallel agents review reuse, efficiency, quality, and CLAUDE.md compliance in one sweep.

    0 points·13 hours ago·easy·discuss
  4. 4.
    Use pushback prompts so Claude proves the change before you ship(support.claude.com)

    Force verification with prompts like “prove this works” and “grill me before the PR” so Claude has to validate instead of declaring done.

    0 points·13 hours ago·easy·discuss
  5. 5.
    Auto-format after edits with a PostToolUse hook(code.claude.com)

    Run prettier/ruff/gofmt automatically after Edit/Write tools so Claude never leaves unformatted files.

    0 points·13 hours ago·medium·discuss
  6. 6.
    Block dangerous Bash with a PreToolUse hook(code.claude.com)

    Add a deterministic PreToolUse hook that rejects destructive shell patterns before Claude can run them.

    0 points·13 hours ago·hard·discuss