Click Path Audit

Traces user interactions through their complete state change sequences to catch bugs that static analysis misses. The classic case: a "New Email" button calls setComposeMode(true) then selectThread(null), but selectThread has a hidden side effect that resets composeMode to false, so the button does nothing. Works by mapping every state store action's side effects first, then auditing each clickable element to see if later function calls undo earlier ones. Use this after systematic debugging finds nothing but users still report broken buttons, or after refactoring shared state stores. Expensive to run comprehensively but deadly accurate for the "button does nothing" class of bugs that come from sequential function calls silently canceling each other out.

skills.sh installs: 5.5K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --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.