القائمة
Transform the findings of a debt-scan into a prioritized, complete action plan. Produce `plan.json` conforming to the schema + a readable `plan.md`.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | debt-plan |
| description | Transform the findings of a debt-scan into a prioritized, complete action plan. Produce `plan.json` conforming to the schema + a readable `plan.md`. |
| license | MIT |
debt-scan validated by the Criticschemas/debt-triage.schema.json, produced by
critic_v2.build_triage): findings already sorted into accept/review/reject
tiers by score. I turn that triage into a remediation plan that requires
JUDGMENT — grouping findings into actions, justifying accepted debt.plan.json conforming to schemas/debt-plan.schema.json (DebtPlan — distinct
from the triage: actions + accepted_debt, not raw tiers)plan.md readable summaryaccepted_debt with justification.mvp-debt-report.md in parallel (see skills/mvp-debt-report/SKILL.md)accepted_debt findings with explicit justificationSee skills/mvp-debt-report/SKILL.md for the parallel report structure.
Validate the produced plan.json against its schema — judgment output is not
guaranteed to be well-formed:
python3 tools/validate_plan.py plan.json # exit 0 = valid
Do not publish a plan that fails validation.
critic_validation.passed = false, refuse to publish and address concerns