debug

Stars0

Forks0

UpdatedJuly 20, 2026 at 19:33

Perform an evidence-based Parallax diagnosis or post-build audit and verify the repair.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

Master0fFate

Master0fFate/parallax-claudecode

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	debug
description	Perform an evidence-based Parallax diagnosis or post-build audit and verify the repair.
argument-hint	[failure, artifact, or audit vectors]
user-invocable	true

Debug

Pass the current Claude session ID to parallax_debug. Audit $ARGUMENTS with professional skepticism.

Establish the expected behavior and reproduce the symptom with the narrowest reliable command.
Separate direct evidence, strong inference, and unknowns. Trace state ownership, feedback, coupling, and timing before proposing a cause.
Rank findings by material impact and likelihood. Cite paths, tests, logs, or command output; ignore cosmetic noise unless requested.
Fix root causes rather than suppressing errors. Keep the patch surgical and add a regression check that fails before the fix when practical.
Run targeted verification, then broader checks proportional to blast radius.

Report diagnosis, root cause, changed files, test evidence, limitations, and remaining risk. If evidence is insufficient, say so rather than assigning a confident verdict.

More from this repository

same repository

horizon

Master0fFate/parallax-claudecode

Run a durable Horizon workflow for a multi-feature goal with bounded autonomous retries and an audit trail.

2026-07-270

parallax

Master0fFate/parallax-claudecode

Compatibility entry point for the Parallax workflow when Claude resolves it as a plugin skill.

2026-07-270

status

Master0fFate/parallax-claudecode

Report the current Claude session's Parallax gate, retries, verification, and trace status.

2026-07-210

build

Master0fFate/parallax-claudecode

Implement a planned change under the Parallax write gate with friction-loop verification.

2026-07-200

check-in

Master0fFate/parallax-claudecode

Record a Parallax protocol checkpoint with concrete evidence before gated implementation work.

2026-07-200

hyperplan

Master0fFate/parallax-claudecode

Harden a non-trivial plan through a three-round adversarial critique and evidence-based synthesis.

2026-07-200

name	debug
description	Perform an evidence-based Parallax diagnosis or post-build audit and verify the repair.
argument-hint	[failure, artifact, or audit vectors]
user-invocable	true

Debug

Pass the current Claude session ID to parallax_debug. Audit $ARGUMENTS with professional skepticism.

Establish the expected behavior and reproduce the symptom with the narrowest reliable command.
Separate direct evidence, strong inference, and unknowns. Trace state ownership, feedback, coupling, and timing before proposing a cause.
Rank findings by material impact and likelihood. Cite paths, tests, logs, or command output; ignore cosmetic noise unless requested.
Fix root causes rather than suppressing errors. Keep the patch surgical and add a regression check that fails before the fix when practical.
Run targeted verification, then broader checks proportional to blast radius.

Report diagnosis, root cause, changed files, test evidence, limitations, and remaining risk. If evidence is insufficient, say so rather than assigning a confident verdict.