Skip to content
Agentmart
Submit a tool

runtime-debug

Debug broken runtime/environments by checking logs and observability first, then code.

Skill by OutThisLife

IndexedMIT★ 206
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/outthislife-runtime-debug

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Debug broken runtime/environments by checking logs and observability first, then code. Use when a URL, deploy, or ephemeral/CI environment fails at runtime rather than a local code bug.

Use cases: devops

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/runtime-debug

What's inside

Skill name
runtime-debug
Description
Debug broken runtime/environments by checking logs and observability first, then code. Use when a URL, deploy, or ephemeral/CI environment fails at runtime rather than a local code bug.
License
MIT
Instructions
37 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Runtime Debug

When something breaks at runtime (a URL 500s, a deploy is down, an ephemeral env
misbehaves), look at what actually happened before editing code.

## Steps

1. Reproduce and capture the real failure (status, error, request id, time).
2. Check observability first: logs, traces, metrics. Use an observability MCP
   (e.g. Datadog) if one is available/connected; otherwise fall back to the
   platform's log stream (CI job, container, Jenkins, cloud logs).
3. Locate the failing service/line from the evidence, not a guess.
4. Fix the real cause. Don't add logging-only "fixes" and call it done.
5. For intentional lab/ephemeral config (test secrets, fail-open), don't raise
   false alarms — leave required env in place.

## MR local preview

- For a requested local link, start the actual worktree app against existing Docker datastores; do not substitute a screenshot gallery. Check Docker Desktop and existing containers first, then use the worktree's Node 18.20.4 and explicit `NODE_ENV=local` / `NODE_PATH`. Verify `/200` and the requested page separately: a healthy server can still return 404 when Mongo has no CMS content.
- Inspect local CMS collection counts before attempting a restore. An empty Atlas Local container needs sanitized seed data; inspect cached archives and download size before starting a large refresh, especially on constrained connections. Never reset or reseed existing data just to start the server.

## Research preview latency

- Separate middleware TTFB from image/render timing before changing public pages. In the portal app, a local preview with unconfigured Upstash Redis can spend seconds retrying rate-limit calls even when the page itself is static.
- Reuse the existing Docker Redis and serverless-redis-http services and their mapped ports. Verify the HTTP pipeline and then the page's rate-limit headers after reconnecting the preview; never bypass production limiting to make a local timing look fast.
- Use headed Chrome when Vercel's preview checkpoint rejects curl/headless requests. Attribute third-party preview-toolbar exceptions by their stack URL rather than hiding all page errors. Compare an exact artwork element crop for reduced-motion proof; full screenshots include animated preview chrome.

## pnpm deployment installs

- Treat a failed frozen install as a deployment blocker even if invoking Next directly builds successfully. For `ERR_PNPM_IGNORED_BUILDS`, inspect the exact dependency lifecycle scripts and the tracked `pnpm-workspace.yaml`; pnpm may generate ignored placeholder decisions locally. Commit explicit reviewed version-scoped allow/deny decisions, keep strict checking enabled for unknown versions, and verify the normal frozen-install/build path before redeploying.

## Don't

- Rewrite code speculatively before reading logs.
- Report fixed without re-checking the runtime.

From OutThisLife/brooklyn-skills, MIT.

More from OutThisLife/brooklyn-skills

Compare and alternatives

    Featured in

    Signals

    Stars
    206
    Forks
    6
    Open issues
    0
    Last commit (this folder)
    Sep 25, 2026 (1 month ago)

    From GitHub (fetched Oct 24, 2026).

    Details

    License
    MIT
    First seen
    Oct 24, 2026
    Last checked
    Oct 24, 2026

    More from OutThisLife

    Cite this page

    runtime-debug skill. Agent Mart. https://agentmart.dev/skills/outthislife-runtime-debug (last updated 2026-10-24)