Files
EVOLV/.agents/skills/evolv-quality-technical-debt/SKILL.md
znetsixe 6a6c04d34b Migrate to new Gitea instance (gitea.wbd-rd.nl)
- Update all submodule URLs from gitea.centraal.wbd-rd.nl to gitea.wbd-rd.nl
- Add settler as proper submodule in .gitmodules
- Add agent skills, function anchors, decisions, and improvements
- Add Docker configuration and scripts
- Add manuals and third_party docs
- Update .gitignore with secrets and build artifacts
- Remove stale .tgz build artifact

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-04 21:07:04 +01:00

2.5 KiB

name, description
name description
evolv-quality-technical-debt Drive code quality, regression prevention, and technical debt management for EVOLV nodes. Use when reviewing changes for bugs, maintainability, test completeness, architectural drift, and when creating prioritized remediation plans for JavaScript/CommonJS Node-RED modules.

EVOLV Quality Technical Debt

Mission

Raise delivery reliability by detecting defects early and systematically reducing technical debt in EVOLV nodes.

Harness Execution Contract

  • Anchor findings to concrete file/line evidence.
  • Separate correctness risk from style preferences.
  • Require regression-proof evidence for fixes (tests that fail-before/pass-after when feasible).
  • Feed recurring failure patterns back into the relevant skill guidance.

Scope

  • Node implementation quality in nodes/<nodeName>/src/
  • Editor/runtime contract consistency in .html + runtime wrappers
  • Shared utility hygiene in nodes/generalFunctions/
  • Test depth in nodes/<nodeName>/test/

Test Policy Baseline

All code changes require tests under nodes/<nodeName>/test/.

Cover at minimum:

  • config default/override behavior and numeric coercion
  • each supported msg.topic handler with edge cases
  • child registration and dedupe side effects
  • tick/output boundaries and error paths
  • regression tests for fixed bugs

Execution:

  • preferred: node --test nodes/<nodeName>/test/*.test.js
  • fallback: node nodes/<nodeName>/test/<file>.test.js

Review Workflow

  1. Assess correctness risks first (runtime errors, logic regressions, broken topic contracts).
  2. Assess maintainability (duplication, unclear ownership, implicit behavior).
  3. Assess test adequacy against EVOLV policy:
  • config defaults/overrides
  • topic handlers and edge cases
  • tick/output boundaries
  • regressions for fixed bugs
  1. Create a prioritized debt backlog with effort and impact.

Quality Criteria

  • Domain logic remains testable without full Node-RED runtime.
  • Complex logic is explicit and minimally coupled.
  • Backward compatibility is deliberate and documented.
  • New behavior includes tests that fail before and pass after.

Deliverables

Return:

  • findings by severity
  • test gaps and specific cases to add
  • debt backlog (now/next/later)
  • recommended refactors with expected payoff

Decision interview triggers:

  • tradeoff between delivery speed and known high-severity risk
  • acceptance of temporary risk with deferred remediation
  • testing scope reductions that materially raise regression risk