القائمة
L5 pre-flight — map the blast radius of a change BEFORE editing high-risk paths.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/Maestra-Tech/ContextDevKit --skill source-command-simulate-impactيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Generate, validate, and explicitly accept a canonical ContextDevKit ADR.
Open a multi-agent deliberation — a council of specialist voices debate a hard question with tiered research, a synthesizer converges, the result feeds an ADR. (ADR-0035 / ADR-0070)
Start a mutation-focused session on one objective and keep its scope bounded.
عرض SKILL.md
| name | source-command-simulate-impact |
| description | L5 pre-flight — map the blast radius of a change BEFORE editing high-risk paths. |
Use this skill when the user asks to run the migrated source command simulate-impact.
Objective: $ARGUMENTS
Produce a Blast Radius Report before material changes on high-risk paths.
Identify what the change touches. List the concrete files/dirs you expect to modify. Cross-
reference contextkit/config.json → l5.highRiskPaths to see which are gated.
Map the blast radius. For each touched area, reason about downstream effects: public contracts/exports, API/route signatures, data schema, auth surface, shared types, anything that other modules or external consumers depend on. If agents are installed (Level 4), delegate focused sub-analyses to the relevant specialists in parallel and consolidate.
Materialize the reviewed prediction with the explicit write flag:
node contextkit/tools/scripts/mark-simulation.mjs --write "$ARGUMENTS" <covered-path-or-dir/> [more ...]
Use trailing slashes for directory coverage (e.g. src/services/). Then fill
the generated Predicted blast radius section with the concrete risks,
order of changes, rollback, and evidence from steps 1–2.
Summarize the report to the user and proceed with the change in the suggested order.
This report is advisory evidence. It never grants a hidden bypass and never replaces host or platform safety controls.