Expose the routes that debug blind
Works out which routes log, which trace and which swallow errors, then drafts the fixes in your repo's own conventions.
I want to do this: Which routes swallow errors or log nothing? Show the gaps and the fixes. ## Setup (skip if Polylane is already set up) Read and follow https://polylane.com/auth.md for non-interactive signup and setup. Start by checking whether I am already signed in; reuse my account and workspace. If the CLI is missing, bootstrap it without starting the interactive wizard: curl -fsSL 'https://polylane.com/setup?ref=prompts' | bash -s -- --install-only Then follow the guide through email verification, workspace selection, source connections, and MCP authentication. Ask me for an email code or OAuth consent only when needed. Verify each step; report pending setup instead of claiming success from installation alone. ## How to work Over MCP: searchTools lists what this workspace exposes, with each tool's schema; call it first. runTool runs one tool, runCode chains several in one call and returns just the answer. search and execute cover the full Polylane REST API: threads, issues, investigations, autofixes, memories. From the terminal: the polylane CLI wraps the same API, with structured output and non-interactive flags everywhere. Reads always work. Write tools appear only if I have opted in, and every write is screened. ## Task: Expose the routes that debug blind Steps: 1. Read the routes across the connected repos 2. Classify each: logs with context, traces, logs nothing, swallows errors 3. Rank the gaps by the traffic and tier of the route 4. Draft fixes using the repo's existing logger and conventions, no new dependencies 5. Deliver the coverage map with the drafts ready for review Ground every claim in data you actually pulled: the query, the log line, the change record. If the data is inconclusive, say so. Ask me before anything that writes.
Coverage is wherever someone happened to care.
The instrumented routes were instrumented by whoever got burned on them. The rest emit nothing, and you find out which is which during the incident.
- The catch block that eats the error and says nothing
- Routes whose only telemetry is customer complaints
- New endpoints shipping with zero instrumentation, again
One prompt, this much work. Every step on your real data.
- 1 Read the routes across the connected repos
- 2 Classify each: logs with context, traces, logs nothing, swallows errors
- 3 Rank the gaps by the traffic and tier of the route
- 4 Draft fixes using the repo's existing logger and conventions, no new dependencies
- 5 Deliver the coverage map with the drafts ready for review
Blind spots found before they hide an incident
A route-by-route coverage report and the fixes already drafted in your style. The next 2am debug has the log line it needs.
The quiet failure 
“Find things that look wrong but never alerted: error spikes, dead crons, growing queues.” Know the account 
“Map our AWS account: what's running, what depends on what, and what's critical?” Risky config 
“Find the risky configuration: public buckets, missing alarms, single points of failure.” The cron audit “List every scheduled job across our clouds and when each one last succeeded.” Close the gaps “Which critical services have no logs or traces? Show the gaps and write the fixes.” Read my dashboards 
“Go through our dashboards and tell me what's drifting from normal this week.” Query to check “Write the query for checkout error rate by region over 24 hours, and save it as a check.” The weekly read 
“Summarise what our telemetry says about last week: regressions, improvements, anything odd.” Watch this deploy “We're deploying checkout-api at 5pm. Watch the metrics after and flag anything that moves.” Onboard me “I'm new here. Walk me through the architecture: the critical path, the data stores, what talks to what.” Instrument the launch “payments-v2 ships next week. What instrumentation should it have before launch? Draft it.”
“Find things that look wrong but never alerted: error spikes, dead crons, growing queues.” Know the account “Map our AWS account: what's running, what depends on what, and what's critical?” Risky config “Find the risky configuration: public buckets, missing alarms, single points of failure.” The cron audit “List every scheduled job across our clouds and when each one last succeeded.” Close the gaps “Which critical services have no logs or traces? Show the gaps and write the fixes.” Read my dashboards “Go through our dashboards and tell me what's drifting from normal this week.” Query to check “Write the query for checkout error rate by region over 24 hours, and save it as a check.” The weekly read “Summarise what our telemetry says about last week: regressions, improvements, anything odd.” Watch this deploy “We're deploying checkout-api at 5pm. Watch the metrics after and flag anything that moves.” Onboard me “I'm new here. Walk me through the architecture: the critical path, the data stores, what talks to what.” Instrument the launch “payments-v2 ships next week. What instrumentation should it have before launch? Draft it.”