Bugfix Without Diagnosis

v1.0.0

A fix is proposed without first identifying the root cause; the symptom is masked rather than resolved.

⭐ 0· 60·1 current·1 all-time

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for mvogt99/bugfix-without-diagnosis.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Bugfix Without Diagnosis" (mvogt99/bugfix-without-diagnosis) from ClawHub.
Skill page: https://clawhub.ai/mvogt99/bugfix-without-diagnosis
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install bugfix-without-diagnosis

ClawHub CLI

Package manager switcher

npx clawhub@latest install bugfix-without-diagnosis

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Benign

high confidence

✓

Purpose & Capability

The name and description describe review/fix guidance and the SKILL.md contains exactly that guidance. No unexpected binaries, env vars, or config paths are requested.

✓

Instruction Scope

SKILL.md provides reviewer/developer guidance (how to reason about root cause versus symptom). It does not instruct the agent to read arbitrary files, access credentials, call external endpoints, or perform system actions.

✓

Install Mechanism

No install specification or code files are present; this is instruction-only so nothing is written to disk or downloaded.

✓

Credentials

The skill requests no environment variables, credentials, or config paths — which is appropriate for a policy/guidance document.

✓

Persistence & Privilege

always is false and the skill is user-invocable. It does not request persistent presence or modify other skills or system settings.

Assessment

This skill is low-risk: it's purely a guideline for proposing bug fixes and asks for no permissions, binaries, or installs. Before installing, confirm you want your agent to have this review-style guidance available (it may influence how the agent suggests fixes). Also remember this is advisory text — it won't enforce checks and the agent could still make incorrect changes if combined with other skills or instructions.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

OSmacOS · Linux · Windows

latestvk978psqpscfxsq00stgdg4cass85hj5e

60downloads

0stars

1versions

Updated 3d ago

v1.0.0

MIT-0

macOS, Linux, Windows

bugfix-without-diagnosis

When a fix goes in without understanding why the bug occurred, the symptom disappears but the cause lingers. It will return under a different shape, or the "fix" will mask a more serious problem upstream.

Symptoms

Fix adds a null check without explaining why the value was null.
Retry loop wrapped around a flaky call with no investigation into why it was failing.
Try/except swallowing a specific exception without stating what conditions produce it.
Condition tweaked (> → >=) to make a test pass, with no explanation of the underlying off-by-one.
PR description says "fix X" with no "because Y".

What to do

Before proposing a fix, write one sentence stating the root cause. If you can't, you don't understand the bug well enough to fix it.
Explain how the symptom follows from the cause — the chain of events from "bad thing happened" to "user saw this".
Confirm the fix addresses the cause, not just the symptom. A null check is valid only if you know why the value was null and concluded that null is acceptable.
Where the cause is upstream, fix it upstream. Only patch downstream if upstream is genuinely out of reach, and say so.
Leave a comment linking the symptom to the cause so future readers don't misread the fix as superficial.

Comments

Loading comments...