Click Path Audit

Tracks what actually happens when users click buttons by tracing every state change in sequence, specifically looking for functions that undo each other. The kind of bug where setComposeMode(true) gets immediately canceled by selectThread's hidden reset to false. Systematic debugging won't catch these because each function works fine in isolation. You'd use this when users report buttons that do nothing, or after touching any shared Zustand or Redux store. Expensive to run (maps every state side effect first), so scope it to specific pages or flows. The skill literally exists because 54 bugs were found the normal way but one stayed hidden until someone traced the actual click path.

skills.sh installs: 4.2K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill click-path-audit --agent claude-code

Installs into .claude/skills of the current project.

Files

/click-path-audit — Behavioural Flow Audit

Find bugs that static code reading misses: state interaction side effects, race conditions between sequential calls, and handlers that silently undo each other.

The Problem This Solves

Traditional debugging checks:

Does the function exist? (missing wiring)
Does it crash? (runtime errors)
Does it return the right type? (data flow)

But it does NOT check:

Does the final UI state match what the button label promises?
Does function B silently undo what function A just did?
Does shared state (Zustand/Redux/context) have side effects that cancel the intended action?

Real example: A "New Email" button called setComposeMode(true) then selectThread(null). Both worked individually. But selectThread had a side effect resetting composeMode: false. The button did nothing. 54 bugs were found by systematic debugging — this one was missed.