Bugfix Without Test

v1.0.0

A fix is applied without a reproduction test, leaving no proof the bug is fixed and no regression coverage.

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

by@mvogt99

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-test.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Bugfix Without Test" (mvogt99/bugfix-without-test) from ClawHub.
Skill page: https://clawhub.ai/mvogt99/bugfix-without-test
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-test

ClawHub CLI

Package manager switcher

npx clawhub@latest install bugfix-without-test

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Benign

high confidence

✓

Purpose & Capability

The name/description (encouraging adding regression tests) matches the SKILL.md content. There are no unrelated environment variables, binaries, or installs requested.

✓

Instruction Scope

SKILL.md contains procedural guidance (reproduce bug as failing test, apply fix, keep test). It does not instruct the agent to read arbitrary files, call external endpoints, access credentials, or run specific system commands.

✓

Install Mechanism

There is no install spec and no code files; nothing is written to disk or downloaded.

✓

Credentials

No environment variables, credentials, or config paths are requested—requirements are minimal and appropriate for a documentation/guidance skill.

✓

Persistence & Privilege

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

Assessment

This skill is simply best-practice guidance for adding tests when fixing bugs and appears safe to install. It's instruction-only (no code or downloads) and requests no credentials. Consider whether you want an agent to act on these instructions autonomously: if your agent has repository write or CI access, it could create/modify tests and code—so retain normal review and access controls. Otherwise, there are no disproportionate permissions or hidden behaviors to worry about.

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

Runtime requirements

OSmacOS · Linux · Windows

latestvk97cph5ydhj0wv446rzqr2ymax85gmm9

56downloads

0stars

1versions

Updated 2d ago

v1.0.0

MIT-0

macOS, Linux, Windows

bugfix-without-test

Fixing a bug without a test means (a) you don't know the fix actually works, and (b) there's nothing to stop the bug from coming back next refactor. A fix without a regression test is provisional at best.

Symptoms

Diff contains code changes but no test changes.
Existing tests still pass, but none of them would have failed under the original bug.
PR description describes a bug scenario that no test exercises.
The fix is a one-liner and no one will remember why it exists six months later.

What to do

Reproduce the bug as a failing test first. Run it. Confirm it fails for the right reason.
Apply the fix. Run the test again. Confirm it passes.
Keep the test in the suite. It becomes the regression guard.
If the bug is hard to test (timing, environment, flaky), say so explicitly and describe what manual verification was done. Don't silently skip.
For bugs discovered in production, add the test at the lowest level that reproduces the issue — unit if possible, integration if not.

Comments

Loading comments...