click-path-audit — Skills — getagentictools

What it does

Does the function exist? (missing wiring)

Does it crash? (runtime errors)

Does it return the right type? (data flow)

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?

What fields does it set?

click path audit

Source

Repository: https://github.com/affaan-m/everything-claude-code

click-path-audit FAQ

What does the click-path-audit skill do?

Trace every user-facing button/touchpoint through its full state change sequence to find bugs where functions individually work but cancel each other out, produce wrong final state, or leave the UI in an inconsistent state. Use when: systematic debugging found no bugs but users report broken buttons, or after any major refactor touching shared state stores. Does the function exist? (missing wiring) Does it crash? (runtime errors)

What does click-path-audit require?

// Result: final loading state depends on which resolves first

How do I install click-path-audit?

Run: npx -y skills add https://github.com/affaan-m/everything-claude-code --skill click-path-audit --agent claude-code — the source lives at github.com/affaan-m/everything-claude-code.

Maintain click-path-audit?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

[click-path-audit on getagentictools](https://getagentictools.com/skills/affaan-m-everything-claude-code-click-path-audit?ref=badge)

npx agentictools info skills/affaan-m-everything-claude-code-click-path-audit

The second line is the CLI lookup for this page — handy in READMEs and docs.