hoppscotch Debugging Prompt

debuggingvery high Token Costbeginner

Prompt provenance

Inspired by hoppscotch/hoppscotch.

Reverse-engineered from real GitHub workflow.

Updated 2 weeks ago·0 copies

Debug API client workflows by tracing request construction, environment and secret resolution, auth headers and params, interceptor selection, REST and GraphQL execution, websocket events, scripting, tests, and shareable reproduction reports.

What this solves

API client request debugging and reproduction

Best used when

You need an agent to reproduce a failing API request from client state, generated headers, auth configuration, environment variables, and network response evidence.
You are debugging REST, GraphQL, websocket, collection-runner, pre-request script, post-request test, or interceptor behavior in an API client workflow.
You want a structured failure report that a backend, frontend, or platform maintainer can act on without guessing which request state was actually sent.

Avoid using when

You only need a generic HTTP status-code explanation.
You are reviewing backend API implementation internals rather than the client-side request construction and execution path.
You want to publish production prompt rows directly without maintainer review.

Prompt Variants

Use this when Claude has broad repo-reading access and should produce a source-cited API client failure report with effective request reconstruction.