القائمة
Generate preventive rules (linters, tests, CI checks) from detected findings. Stops the same pattern from re-appearing after a fix.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | debt-prevention |
| description | Generate preventive rules (linters, tests, CI checks) from detected findings. Stops the same pattern from re-appearing after a fix. |
| license | MIT |
debt-verify reports success)Read .debt-scan.json (V1) or query the KG (V2). Find:
For each pattern, generate the appropriate rule:
| Pattern | Language | Rule type | Tool |
|---|---|---|---|
code.complexity | Python | ruff config rule | ruff |
code.complexity | Rust | clippy.toml config | cargo clippy |
code.complexity | TS/JS | .eslintrc rule | eslint |
security.secrets_in_code | Any | gitleaks config | gitleaks |
security.known_vulns | Any | dependabot.yml | GitHub |
dependencies.circular | Python | pydeps config | pydeps |
dependencies.circular | TS/JS | dependency-cruiser config | depcruise |
tests.coverage_gaps | Any | CI coverage threshold | coverage.py, tarpaulin, jest |
For each pattern, generate a regression test that fails if the pattern re-appears.
For each rule, generate a CI step that runs the tool on every PR.
Each preventive rule becomes a Convention node in the KG, with blocks edge to the Component it protects.
Critic reviews generated rules for:
prevention-rules/<pattern>.toml|yaml|json : config files for lintersprevention-tests/test_<pattern>.py : regression tests.github/workflows/prevention-<pattern>.yml : CI stepsprevention-report.md : summary of generated rules + their rationaletools/prevent_finding.py : orchestratorkg_store.py (Layer 0) : persistencekg_sync.py (Layer 0) : vault projectionskills/critic/SKILL.md : mandatoryConvention nodeConventional 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).
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.