القائمة
Use when implementation is complete or review is requested and the user may want a focused security review of the changed code
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/alicankiraz1/Codex-Sentinel --skill security-review-gateيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Use when a repository wants stage-aware cybersecurity guidance during planning, risky implementation changes across authentication, authorization, tokens, secrets, middleware, outbound requests, file handling, CI, deployment, and other trust boundaries, post-implementation review, or pre-release hardening; do not trigger for doc-only, naming-only, formatting-only, or UI-only changes that do not affect a trust boundary
Use when defining plans, specs, or task breakdowns for web application work that may be missing security requirements
Use when a feature or project is nearing handoff or release and the user may want a stack-aware security check plan without automatic setup
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | security-review-gate |
| description | Use when implementation is complete or review is requested and the user may want a focused security review of the changed code |
Run an advisory-only security review after implementation. This skill reports findings but does not block progress by default.
../codex-sentinel/references/interaction-model.md for language behavior when available.references/review-categories.md.../codex-sentinel/references/active-analysis.md. If git-backed active analysis is unavailable but shell reads still work, you may inspect files already visible in context or explicitly named by the user as a limited current-source fallback. If shell access is unavailable, stay description-based and note the fallback in assumptions.../shared/common-web-threats.md, ../shared/finding-schema.md, and a stack profile when relevant.../shared/finding-schema.md. Include evidence_source whenever code, diff, heuristic, or description evidence materially affected the conclusion.