Skip to content

Skills suchen.../

Agent Skill Search Engine

Suche

Suche
Kategorien
Berufe

About

About
Privacy
Terms

© 2026 Skills Pool. Alle Rechte vorbehalten.

Debugging Network | Skills Pool

Skill-Datei

Debugging Network

Investigate network-related replay failures and divergences. Use when replays fail due to network errors, stubbing issues, or request ordering problems.

alwaysmeticulous26 Sterne12.03.2026

Beruf
Kategorien: Debugging

Skill-Inhalt

Debugging Network Issues

Use this guide when replays fail or diverge due to network request problems.

Investigation Steps

1. Check Logs for Network Errors

Search logs.concise.txt for "network", "fetch", "xhr", "request", "response", "timeout".
Look for failed requests, unexpected status codes, or missing responses.
Check for CORS errors or SSL issues.

2. Compare Network Activity in Timeline

In timeline.json, look for network-related events.
Compare the sequence and timing of network requests between head and base.
Look for requests in one replay that are missing in the other.

3. Examine Session Data

Read session data in debug-data/sessions/<id>/data.json.

Verwandte Skills

Schnellinstallation

Debugging Network

npx skillvault add alwaysmeticulous/alwaysmeticulous-meticulous-sdk-packages-debug-workspace-src-templates-skills-debugging-network-skill-md

Skill herunterladen Repository öffnen

Autor: alwaysmeticulous
Sterne: 26
Aktualisiert: 12.03.2026
Beruf

Auf dieser Seite

01Debugging Network Issues

Check recordedRequests for the original HAR entries captured during recording.

Compare recorded requests with what was replayed.

4. Look for Stubbing Issues

Network requests are stubbed during replay using recorded data.
Check if new API endpoints were added that don't have recorded responses.
Look for requests with dynamic parameters (timestamps, tokens) that may not match stubs.

5. Check for Request Ordering Dependencies

Some applications depend on requests completing in a specific order.
Look for race conditions where parallel requests resolve differently.
Check for waterfall dependencies (request B depends on response from request A).

6. Verify API Compatibility

If the API was changed, recorded responses may no longer be valid.
Check for schema changes, new required fields, or renamed endpoints.

02Investigation Steps

031. Check Logs for Network Errors

042. Compare Network Activity in Timeline

053. Examine Session Data

064. Look for Stubbing Issues

075. Check for Request Ordering Dependencies

086. Verify API Compatibility

Computer Network Support Specialists

Session Logs

Search and analyze your own session logs (older/parent conversations) using jq.

OpenClaw Test Heap Leaks

Investigate `pnpm test` memory growth, Vitest worker OOMs, and suspicious RSS increases in OpenClaw using the `scripts/test-parallel.mjs` heap snapshot tooling. Use when Codex needs to reproduce test-lane memory growth, collect repeated `.heapsnapshot` files, compare snapshots from the same worker PID, triage likely transformed-module retention versus likely runtime leaks, and fix or reduce the impact by patching cleanup logic or isolating hotspot tests.

Node Connect

Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.

Openclaw Qa Testing

Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.

Openclaw Secret Scanning Maintainer

Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.

Flags

Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.

Computer Network Support Specialists