Skip to content
Skills Library
Programming · Building & coding

bug-fix

/bug-fix

Fix a Device bug the project's way - reproduce it, write a small failing test, find the root cause, fix it, prove the test now passes. Use for any bug report or broken feature; escalates to a spec when the cause or fix is not obvious.

Repository
device ↗
Licence
AGPL-3.0
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.

What it does and when to use it

Fix a Device bug the project's way - reproduce it, write a small failing test, find the root cause, fix it, prove the test now passes. Use for any bug report or broken feature; escalates to a spec when the cause or fix is not obvious.

Original author description

Fix a Device bug the project's way - reproduce it, write a small failing test, find the root cause, fix it, prove the test now passes. Use for any bug report or broken feature; escalates to a spec when the cause or fix is not obvious.

How it works

  1. 1. Reproduce
  2. 2. Pin it with a failing test
  3. 3. Find the cause
  4. 4. Fix and prove
  5. 5. Pull request
Original SKILL.md headings · 39 lines, 295 words
SKILL.md preview
---
name: bug-fix
description: Fix a Device bug the project's way - reproduce it, write a small failing test, find the root cause, fix it, prove the test now passes. Use for any bug report or broken feature; escalates to a spec when the cause or fix is not obvious.
---

# Fix a bug

## 1. Reproduce

Turn the report into exact steps, on `origin/main`. Use the cheapest path that shows it: a core
test, an engine test, the app with `--demo` or a `--state` review state, or the self-test. Note the
platform; Linux GCC and Windows MSVC catch mistakes macOS clang lets through. If you can't
reproduce it, say so with what you tried, rather than guessing a fix.

## 2. Pin it with a failing test

Write the smallest test that fails because of the bug, at the lowest layer that shows it:

- model, command or persistence logic: `crates/dstudio-core/tests/`
- engine behaviour or DSP: `engine/tests/` (devices: `engine/tests/devices/`, with `DeviceRig`)
- Rust and engine together: `crates/dstudio-engine/tests/`
- a UI flow: a step in the app self-test (`crates/dstudio-app/src/selftest.rs`)

Run it and watch it fail for the right reason. A few sharp tests beat many shallow ones; add the
neighbouring cases the same root cause could break, and stop there.

## 3. Find the cause

Fix the cause, not the symptom. If the cause turns out to be a design problem, or the fix crosses
layers or changes behaviour users rely on, stop and write a spec (`spec-write`) instead; put what
you learned in its Problem section.

## 4. Fix and prove

Make the fix, run the new test (it passes), then the fast checks for the touched area and the full
gate from `spec-verify` § 3 before the pull request. If the bug was a performance regression, show
the benchmark before and after (`dstudio-bench`), and add a benchmark row if none caught it.

## 5. Pull request

Follow `dstudio-pr`. The description says how to reproduce the bug, what the cause was, and which
test now guards it. Visible bugs get before and after screenshots.

Versions

RepositoryScoreLicence
This page · devicedaw/device100AGPL-3.0
nexus-substrate/nexus-agents100MIT
ramboz/jig100MIT
ramboz/jig100MIT
ramboz/jig100MIT
sd0xdev/sd0x-harness100MIT
mtvrkan/senior-dev-kit100MIT
pronskiy/php-src-developer100MIT
chrisallenlane/claude-swe-workflows100MIT

Database snapshot: 13.11.2026 · package version c954a8830bf2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 96fix-bug
    Fix a defect: reproduce it, write a failing test, find the root cause, fix it and record the lesson. Use for each bug.
  • 100fix
    Use when fixing a bug test-first: write a failing test to reproduce it, find the root cause, fix, and add a regression test.
  • 100fix-bug
    Reproduce the bug, find the root cause, fix it there, and verify against the repro with prove-it-works. Use for any defect report; not for a direct fix in Normal mode when no repro-first loop is needed, and not for a performance regression (use tune-perf).
  • 95pstack-bug-fix
    pstack bug-fix playbook: reproduce a defect, root-cause it with runtime evidence, land a failing test before the smallest fix, and verify on the same surface. Use for /pstack-bug-fix or when asked to fix a bug the pstack way.
  • 96fix
    Fix a bug the Concordia way — reproduce it with a failing test first, find the root cause, apply the smallest fix, and prove it. Use when the user reports a bug, a wrong result, an exception or a failing test.
  • 100debug
    Debug a bug, failing test or build, crash, or error. Reproduce it, find the root cause before proposing a fix, prove the fix with the smallest check, add a regression test. Use when something is broken and you need to know why.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.