القائمة
Review current changes for architecture risk, boundary pressure, coupling, duplication, and maintainability impact.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/SeemSeam/agent-roles-spec --skill archi-diffيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Review a declared code change or code scope with evidence-backed findings and five independent quality scores. Use for pull requests, diffs, commits, patches, file sets, modules, bug fixes, refactors, and implementation-review requests.
Diagnose and recover a CCB agent whose provider context is corrupted, stale, overloaded, or semantically off-track when the user wants more than a plain clear: clear the agent only after safety checks, reconstruct the active task context from CCB lineage/runtime evidence, and resume or resubmit the interrupted work with a compact handoff. Use for requests like "clear this agent then restore its task", "context is broken but continue the current job", "repair talk1/worker context and inherit current state", or "after clear, recover the task".
Diagnose and recover CCB communication and reply delivery stalls. Use when a user reports a missing CCB_REPLY, stuck ask, agent stuck busy/delivering, queued work behind an active job, cancelled/incomplete reply, empty artifact, chain not continuing, rejected active-turn followup, duplicate retry after success, or a CCB mailbox/communication backend that appears stuck.
| name | archi-diff |
| description | Review current changes for architecture risk, boundary pressure, coupling, duplication, and maintainability impact. |
Use this skill for change-scoped architecture review.
archi-evidence-map first when the evidence source is unclear or when
tools are unavailable.code-review-and-quality when the diff needs broad quality
coverage beyond architecture-only findings.requesting-code-review when the user wants an independent
review lane or review handoff..architec/architec-summary.md first when present..architec/architec-analysis.json for exact scores, concerns, signals,
hotspots, and artifact paths.Lead with the verdict:
Verdict
- diff status:
- incremental score:
Blocking Issues
- ...
Impacted Areas
- ...
Required Changes
- ...
Do not paste raw JSON. Use direct code references for findings that need engineering action.
If no architecture-analysis tool is available, continue with direct diff and source review, and state the missing evidence as residual risk.