Skip to content
Skills Library
Programming · Testing

node-craft-fix

/node-craft-fix

Fixes a bug, failing test or regression in a Node.js/TypeScript backend with evidence: record the current test state, reproduce the failure through the real entry point (route, job, webhook, migration), write a regression test that fails for the right reason, make the smallest correct fix, prove it with the related tests, and report what was and was not verified. Never weakens, skips or deletes tests to get green and never turns a fix into an unrequested architecture change. Use when something is broken, a test fails, an endpoint returns the wrong status or data, a job misbehaves, or a product

Repository
node-craft ↗
Licence
MIT
Last repository change
04.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
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

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

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Fixes a bug, failing test or regression in a Node.js/TypeScript backend with evidence: record the current test state, reproduce the failure through the real entry point (route, job, webhook, migration), write a regression test that fails for the right reason, make the smallest correct fix, prove it with the related tests, and report what was and was not verified. Never weakens, skips or deletes tests to get green and never turns a fix into an unrequested architecture change. Use when something is broken, a test fails, an endpoint returns the wrong status or data, a job misbehaves, or a product

Original author description

Fixes a bug, failing test or regression in a Node.js/TypeScript backend with evidence: record the current test state, reproduce the failure through the real entry point (route, job, webhook, migration), write a regression test that fails for the right reason, make the smallest correct fix, prove it with the related tests, and report what was and was not verified. Never weakens, skips or deletes tests to get green and never turns a fix into an unrequested architecture change. Use when something is broken, a test fails, an endpoint returns the wrong status or data, a job misbehaves, or a product

How it works

  1. 1. Baseline
  2. 2. Reproduce
  3. 3. Regression test (Red)
  4. 4. Smallest correct fix (Green)
  5. 5. Prove it
  6. 6. Report
Original SKILL.md headings · 49 lines, 406 words
SKILL.md preview
---
name: node-craft-fix
description: "Fixes a bug, failing test or regression in a Node.js/TypeScript backend with evidence: record the current test state, reproduce the failure through the real entry point (route, job, webhook, migration), write a regression test that fails for the right reason, make the smallest correct fix, prove it with the related tests, and report what was and was not verified. Never weakens, skips or deletes tests to get green and never turns a fix into an unrequested architecture change. Use when something is broken, a test fails, an endpoint returns the wrong status or data, a job misbehaves, or a production incident needs a code fix."
---

# Fix a backend bug

Follow `node-craft` for the working rules. A fix is a small, proven change, not a refactor of everything nearby.

| Step | Read |
|---|---|
| Reproduce, isolate, regression test, fix, prove | `references/reproduce-regress.md` |
| When a test may change and when it may not | `references/test-preservation.md` |

## 1. Baseline

Run the related tests before touching anything and record the result. Note which failures already existed. They are
reported as pre-existing, not silently fixed and not blamed on your change.

## 2. Reproduce

Reproduce through the same entry point that failed: the HTTP route (`app.inject`), the job handler with a real queue
when the bug is about retries, the webhook with the recorded payload, the migration on a copy of the previous schema.
Use real PostgreSQL for anything involving queries, constraints, transactions or concurrency. Note the inputs, the
actual result and the expected result. If you cannot reproduce it, say what you tried and what evidence is missing
(logs with the request id, payload, version); do not guess a fix.

## 3. Regression test (Red)

Write the test that captures the expected behaviour and fails on the current code **for the reason in the report**.
A test that fails because of an import, an env var or a missing container is not Red yet.

## 4. Smallest correct fix (Green)

- Fix the cause, not the symptom. A `try/catch` that hides the error, a default that masks missing data, or a retry
  that hides a race is not a fix.
- Keep the change inside the area of the bug. If the right fix needs a wider change (a missing constraint, a
  transaction boundary in another module, a contract change), make it with its own tests and say why. A rewrite or
  framework switch is a proposal, not part of the fix.
- Data already damaged by the bug (duplicates, wrong states) needs its own reviewed migration or script, with the
  impact stated and approval before running it on shared data.

## 5. Prove it

Run the regression test, the module's tests, and the tests of anything that shares the changed code. For a contract
change, regenerate OpenAPI and check compatibility (`node-craft-contract`). For a performance bug, before and after
numbers (`node-craft-perf`).

## 6. Report

Root cause in one or two sentences, the fix, the regression test, the commands run with results, pre-existing
failures, and what could not be verified.
Files in this package (3)
  • SKILL.md 3 KB
  • references/reproduce-regress.md 2 KB
  • references/test-preservation.md 1 KB

Versions

The database has no other skills named node-craft-fix.

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

Downloads in the last 30 days: 0 · ranking

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

Similar skills

  • 100sdlc-debug
    Bug track: reproduce, find the root cause with evidence, write a failing regression test, apply the smallest fix, check siblings, verify on the real surface. Use when something behaves wrongly, a test fails, an error is reported, or the user says 'debug', 'fix this bug' or 'why does X happen'.
  • 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.
  • 100bug-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.
  • 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.
  • 90debug-a-failing-test
    Finds out why a test fails and fixes the cause, not the test: reproduce it alone, read the error, narrow it down, fix, and prove it with a run. Use when a test fails, a check is red, a test is flaky, or the owner says the tests broke.
  • 100tdd
    Drive a fix with /tdd when the user asks for a failing test or a regression test, or when a cheap local test path exists. Write the failing test, confirm the intended failure, apply the smallest fix, and rerun.

Feedback and reports

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