Menu
Verify that a fix resolved the finding without introducing regression.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | debt-verify |
| description | Verify that a fix resolved the finding without introducing regression. |
| license | MIT |
verify-<id>.json : structured report.debt-history.json:
resolvedregressedTo prevent an agent from "resolving" a finding by modifying code to make the detector silent (without actually fixing the problem):
critical and high severity fixes{
"verify_id": "v-2026-06-17-001",
"finding_id": "f-001",
"timestamp": "2026-06-17T15:00:00Z",
"finding_resolved": true,
"tests_passed": true,
"regressions_detected": [],
"new_debt_introduced": [],
"human_review_status": "pending | approved | rejected",
"critic_validation": { ... }
}
Conventional Commits 1.0 enforcer. Two complementary modes: (1) AUTO-SUGGEST — when you say "commit", "commit my changes", "commit this", or invoke `/commit`, the skill inspects `git diff --staged`, proposes 1–3 conventional commit messages (type + optional scope + subject), and asks which one to use. You never have to remember the format. (2) VALIDATOR — every `git commit` passes through a PreToolUse hook that validates the first line of the message against the Conventional Commits regex. Non-conformant commits trigger a confirm prompt — they cannot slip through silently. Types allowed: feat, fix, refactor, perf, docs, test, chore, build, ci, style, revert. Optional scope in parentheses (lowercase kebab-case, ≤ 20 chars). Optional `!` and `BREAKING CHANGE:` footer. Use when: "commit", "commit my changes", "make a commit", "commit this", "validate commit", "/commit". Proactively invoke whenever the user says "commit" or runs `git commit` through the agent, and after a logical unit
Check for and apply AI-Native Dev Stack updates, non-destructively. Detects whether the stack repo is behind upstream, shows what changed, and fast-forwards the shared clone — without ever touching your personalized configs (CLAUDE.md, Mavis agent.md, config.sh). Use when: "upgrade the stack", "update ai-native-dev-stack", "is the stack up to date?", "get the latest rules/method". Proactively suggest at the start of a session if an update is available.
Detect architecture-level technical debt: coupling, cycles, boundary violations, layer leaks. Outputs findings conforming to the debt-finding schema.
CRUD operations on the Debt Registry. Manages the active list of accepted debts, decisions, and resolution status. Persists to the KG (Layer 0).
Generate preventive rules (linters, tests, CI checks) from detected findings. Stops the same pattern from re-appearing after a fix.
Scan a codebase to detect technical debt (code, security, dependencies, tests, architecture). Orchestrate deterministic tools + LLM. Produce a `.debt-scan.json` file conforming to the schema.