cantiere

Repairs defects in an AI self-audit registry using behavioral tests and gated delivery.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/NicolaeRotaru/ad-mycity --skill cantiere-nicolaerotaru
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cantiere
Source: https://github.com/NicolaeRotaru/ad-mycity/tree/main/.claude/skills/cantiere
Command: npx skills add https://github.com/NicolaeRotaru/ad-mycity --skill cantiere-nicolaerotaru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an AI system maintains a registry of its own defects (cantiere-difetti.json), fixing them one by one produces unreadable pull requests, regressions, and fixes that pass shallow checks while the underlying cause survives. This Skill provides the operating manual for repairing those defects in batches grouped by root cause, with mandatory behavioral tests, mutation checks, and an exit gate that blocks delivery until everything is green. ## Core Features & Use Cases - Root-cause batching: Groups open defects by how they broke (not by count), prioritizing diseases that block revenue or corrupt the control panel, and sizes each batch to the shared fix module. - Behavioral verification: Requires executable tests on real data, a non-vacuity mutation check (the test must turn red when the fix is deliberately broken), and a sibling sweep that caps how widely a defect class may spread. - Gated delivery with independent review: Runs a lot gate (cancello-lotto.mjs) with hard blockers, mandates an independent acceptance pass by an agent that did not build the fix, and supports parallel lanes with disjoint file territories. - Use Case: Nicola says "risolvi i difetti principali" — the Skill loads, measures open defects by disease, picks the costliest cluster, extracts the decision logic into a pure module, writes per-defect tests with mutations, runs the gate, and delivers a reviewable PR without merging. ## Quick Start Ask the assistant to resolve the open defects in the machine's self-awareness registry, starting from the most blocking ones.

Frequently Asked Questions about cantiere

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix defects in an AI self-audit registry?▼

Group open defects by root cause rather than count, verify each defect card against the real code, extract the decision logic into a pure testable module, and write one executable test per defect. Run the lot gate script and deliver only when it exits green.

What is a mutation-based non-vacuity check in testing?▼

It deliberately breaks the fix and requires the test to turn red, proving the test actually exercises the fix. Each repaired defect needs a mutation entry describing the exact code piece that makes the fix true, or the delivery gate blocks with a missing-mutation violation.

When is runtime verification with Playwright required?▼

Runtime verification is mandatory when a fix touches panel frontend code or shell scripts and the changed decision was not extracted into a pure function with its own test. Without it, the defect stays open and must be declared as such in the pull request.

Can multiple agents repair defects in parallel?▼

Yes, but the parallel unit is the root cause, not the individual defect, and each lane gets a disjoint file territory it may not leave. Shared registries are never written by lanes; each lane delivers a JSON fragment that the orchestrator merges, and only the orchestrator commits.

Why does the exit gate return exit code 2?▼

Exit 2 means everything measurable is green but some checks could not run, such as shallow-clone-blind proof checks or a missing typecheck install. Those gaps must be declared in the pull request; exit 2 is not equivalent to exit 0 and blocks CI.

What are the limitations of this defect repair workflow?▼

It only covers defects in the machine's own self-awareness registry, not bugs in the marketplace or control panel code. It also cannot prove a fix is permanent for defects closed with pattern-based tests that can never turn red.