diagnose plugins

by Melodic Software

Debug observed failures via a disciplined six-phase loop: build a fast deterministic reproduction signal, reproduce, rank falsifiable hypotheses, instrument, fix with a regression test, then clean up and post-mortem.

by Melodic Software

Test-stage discipline: /testing:plan (coverage gaps, test plans), /testing:write (TDD authoring), /testing:run-e2e (live E2E and smoke checks), /testing:diagnose (failing-test root cause, with a fix-until-green workflow across files), /testing:audit (can't-fail test audit with a fail-closed gate), /testing:cleanup (rewrite, quarantine, or delete low-value tests behind a mutation gate), /testing:setup, and opt-in hooks that scan test files Claude writes and flag edits that weaken tests.

by Sebastian Rädle

Netzwerk-Engineer (Bertram Fritz): vendor-agnostische Netzwerk-Diagnose und -Konfiguration nach dem Reference-first-Prinzip — CLI-Syntax und Best Practices aus der Vendor-Referenz statt aus dem Gedächtnis. L1–L7-Fehlersuche, Config erzeugen/validieren, Dialekt-Übersetzung (Cisco IOS/RouterOS/PAN-OS/Aruba/Junos), Architektur-/Segmentierungs-Design, gestufter Live-Zugriff mit Blast-Radius-Respekt.

by Job Schepers

The five procedures every repository has and no plugin can write: run — how its application is built and comes up; capture — how evidence is taken; diagnose — how a cause is found inside the running application, breakpoints included, without handing the debugger to a person; estimate — how work is sized in story points against the repository's own finished work; prototype — how a feature is sketched, or an existing demo revised, as one standalone HTML file on the repository's demo template, from its design system and Storybook. Each lands as one editable copy under .agents/skills/ with a managed wrapper per host that carries the fixed goal — run as Claude Code's run-<name> recipe from /run-skill-generator, with a Copilot twin: the goal is the plugin's and refreshes on upgrade, the procedure is the repository's and is never overwritten once edited. Two skills, init and update, keyed by components.devbook-procedures.adopted in .devbook/config.json. An L1 extension over devbook: it follows devbook's reconcile protocol and stamp, and names no engine.