Skip to content
Agentmart
Submit a tool

route-diagnostics

Route multi-step bug, regression, CI, CUDA, or performance diagnosis when failure isolation requires choosing a method.

Skill by linjuhon

IndexedMIT
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/linjuhon-route-diagnostics

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

Route multi-step bug, regression, CI, CUDA, or performance diagnosis when failure isolation requires choosing a method. Default to diagnosis only; do not use for an already authorized narrow fix.

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/route-diagnostics

What's inside

Skill name
route-diagnostics
Description
Route multi-step bug, regression, CI, CUDA, or performance diagnosis when failure isolation requires choosing a method. Default to diagnosis only; do not use for an already authorized narrow fix.
License
MIT
Instructions
24 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • openai.yaml · agents/

SKILL.md (first lines)

# Route Diagnostics

Isolate the first trustworthy failure before proposing a repair.

## Select the path

1. Hard bug, regression, flake, or unknown failure → `diagnosing-bugs`; establish a tight failing loop first.
2. A runtime may not match the current source or build → `binary-identity`.
3. Numeric correctness needs a known expected result → `oracle-validation`.
4. An active CUDA correctness gate has a reproducible failure → `cuda-kernel-debug` after identity and oracle prerequisites are available.
5. A performance regression remains after correctness is closed → `performance-profiling`.
6. A GitHub Actions failure is the observable symptom → `github:gh-fix-ci`; retain diagnosis-only scope unless repair is authorized.

## Boundaries

- Do not use performance evidence to explain an unverified correctness failure.
- Do not invoke CUDA debugging for a generic GPU concern without the active correctness gate.
- Do not patch source merely because the cause is known; hand off to `route-engineering` only after authorization.

## Return

State the reproduction, first failing observation, selected leaf skill, semantic owner or uncertainty, and whether a repair handoff is now warranted.

From linjuhon/codex-personal-skills, MIT.

More from linjuhon/codex-personal-skills

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Aug 8, 2026 (2 months ago)
Last release
Aug 8, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

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

More from linjuhon

Cite this page

route-diagnostics skill. Agent Mart. https://agentmart.dev/skills/linjuhon-route-diagnostics (last updated 2026-10-24)