fix-bug

Silent integration failures occur when systems execute without errors but expected side effects drop due to swallowed exceptions or fail-soft constructs. This Skill extracts endpoints, auth, and payload shape to map the runtime contract and identify where the event gets lost.

Debug a missing callback by mapping the concrete trigger, dispatch, and receiver sequence using file-and-line references. This verifies the runtime contract seams are connected and surfaces swallowed errors or empty catches that silently drop the expected trigger.

The fastest way to diagnose silent error handling is requesting one decisive piece of runtime evidence, such as receiver log output during reproduction. This disambiguates hypotheses quickly and ranks likely swallow-sites with honest confidence levels.

Yes, you can trace a webhook integration failure using the expected payload shape. The workflow extracts endpoints, auth, required env vars, and log locations to satisfy contract-first requirements, then identifies swallow-sites even without a failing test.

Common patterns that cause a system to run but drop the expected side effect include swallowed errors, empty catches, fail-soft constructs like OR-true operators, and output redirection. These patterns mask integration failures by preventing error propagation.

To fix a config write or env injection that didn't change state, grep for swallowed errors and fail-soft constructs to surface likely drop locations. Then verify the runtime contract by checking on-disk artifacts and requesting one disambiguating diagnostic log.