القائمة
CRUD operations on the Debt Registry. Manages the active list of accepted debts, decisions, and resolution status. Persists to the KG (Layer 0).
التثبيت باستخدام 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.
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.
Challenge every finding and plan before validation. Reduce hallucinations, force proofs, verify completeness.
| name | debt-manage |
| description | CRUD operations on the Debt Registry. Manages the active list of accepted debts, decisions, and resolution status. Persists to the KG (Layer 0). |
| license | MIT |
Operations:
register : add a new debt to the registry (with reason)update_status : change status (open → in_progress → resolved)assign_owner : set an owner (user/team)set_due_date : schedule a re-evaluationquery : list debts with filters (status, owner, severity, due_date)archive : move to cold storage after 1 year resolvedregister MUST have accepted_reason if status is "accepted"update_status to "resolved" MUST be paired with a fix_id (verified)All operations are persisted to the KG as:
Debt node metadataassigned_to if owner is a Component/ADR)accepted_reason)After every operation, sync the relevant slice of the KG to the vault (per ADR-0023).
Critic validates:
accepted_reason must be non-trivial (≥ 50 chars, not "TODO" or "later")due_date must be in the futureowner must exist in the system (else flagged as orphan)debt-registry.json (V1 compat)debt-manage.log : audit trailtools/registry.py : CRUD operationskg_store.py (Layer 0) : persistencekg_sync.py (Layer 0) : vault projectionskills/critic/SKILL.md : validation