you-might-not-need-a-callback

You need useCallback when passing callbacks to memoized child components to preserve referential stability, or when hook dependencies require stable function references; otherwise, wrapping functions adds wasted overhead without performance gains.

Analyze a scoped target like current changes or a full repository to detect useCallback anti-patterns such as unstable dependencies or empty deps causing stale closures, then apply deterministic refactoring fixes based on React's official guidance.

Stale closures in useCallback happen when empty dependency arrays prevent the hook from capturing updated state or props, freezing the callback to initial values; fixing the dependency array restores correct memoization behavior.

Yes, you can run scoped analysis on current changes, a specific folder, a pull request, or the whole repository to identify incorrect memoization targets and event handlers on native elements within that selected scope.

Wrapping event handlers on native DOM elements with useCallback is an anti-pattern that creates wasted memoization because native elements do not use referential equality checks, adding complexity without performance benefits.