القائمة
Create an Architectural Decision Record (ADR) under documentation/docs/adr/. Use when making or documenting an architectural decision.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/Cosmian/kms --skill adrيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Scan Rust code for every form of panic or brutal process exit: panic!, todo!, unimplemented!, unreachable!, .unwrap(), .expect() in production, process::exit/abort, integer overflow, and out-of-bounds indexing. Produces a ranked report with patches. Use when reviewing Rust code quality, before any PR, or when adding new Rust code.
Hardcore Rust code review gate: orchestrates ALL Rust review skills in sequence (panic audit, error propagation, async refactor, simplify, refactor, patterns, security, cryptography). Each skill writes its report to ./review/. Produces a unified go/no-go verdict. Use before submitting any significant Rust PR or after large code generation.
Write the next version entry at the top of CHANGELOG.md by summarizing all changes since the last tagged release. Use when preparing release notes.
| name | adr |
| description | Create an Architectural Decision Record (ADR) under documentation/docs/adr/. Use when making or documenting an architectural decision. |
Create an ADR document for the Eviden KMS repository.
Save ADRs at: documentation/docs/adr/adr-YYYY-MM-DD-[title-slug].md
Where YYYY-MM-DD is the current date.
If the documentation/docs/adr/ directory doesn't exist yet, create it and add a nav entry in documentation/mkdocs.yml.
Ask the user for:
If any required input is missing, ask before proceeding.
---
title: "ADR-YYYY-MM-DD: [Decision Title]"
status: "Proposed"
date: "YYYY-MM-DD"
authors: "[Stakeholder Names/Roles]"
tags: ["architecture", "decision"]
supersedes: ""
superseded_by: ""
---
# ADR-YYYY-MM-DD: [Decision Title]
## Status
**Proposed** | Accepted | Rejected | Superseded | Deprecated
## Context
[Problem statement, technical constraints, business requirements, and environmental factors requiring this decision.]
## Decision
[Chosen solution with clear rationale for selection.]
## Consequences
### Positive
- **POS-001**: [Beneficial outcome]
- **POS-002**: [Performance, maintainability, or security improvement]
### Negative
- **NEG-001**: [Trade-off or limitation]
- **NEG-002**: [Technical debt or complexity introduced]
## Alternatives Considered
### [Alternative 1 Name]
- **ALT-001 Description**: [Brief technical description]
- **ALT-002 Rejection Reason**: [Why this option was not selected]
### [Alternative 2 Name]
- **ALT-003 Description**: [Brief technical description]
- **ALT-004 Rejection Reason**: [Why this option was not selected]
## Implementation Notes
- **IMP-001**: [Key implementation consideration]
- **IMP-002**: [Migration or rollout strategy if applicable]
- **IMP-003**: [Monitoring and success criteria]
## References
- **REF-001**: [Related ADRs or prior decisions]
- **REF-002**: [External documentation, RFCs, specifications]
- **REF-003**: [Relevant codebase files: e.g. `crate/server_database/src/`, `crate/server/src/config/`]