القائمة
Implement work from a spec, ticket, or agreed conversation. Use explicitly when the user wants an existing plan carried through to working code.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/stevesolun/ctx --skill implementيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Repo-aware recommendation manager for ctx. Scans the active repository, identifies stack and workflow signals, recommends a capped set of skills, agents, and MCP servers, and unloads helpers that no longer match the current work after user confirmation. Harnesses are recommended by the custom-model onboarding flow or loop adapters and then attach to the same recommendation layer.
Recommend the smallest Matt Pocock skill or short skill sequence that fits the user's current goal.
Review a Git diff against repository standards and its originating requirements. Use for pull requests, branches, work-in-progress changes, or changes since a commit, tag, or merge-base.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | implement |
| description | Implement work from a spec, ticket, or agreed conversation. Use explicitly when the user wants an existing plan carried through to working code. |
Confirm the intended outcome and inspect the relevant code, tests, and repository conventions. Resolve ambiguity only when it would materially change the result; otherwise make a reasonable scoped assumption and proceed.
Implement the smallest coherent change that satisfies the source requirements. Use test-first development when requested or when a focused failing test is the clearest feedback loop. Avoid speculative abstractions and unrelated cleanup.
Validate the changed surface proportionally: start with focused evidence and expand to broader checks when risk or repository contracts justify it. Use a separate review when semantic risk remains or the user requests one.
Report what changed, what was verified, and any remaining uncertainty. Commit, publish, or mutate tracker state only when requested or clearly included in the active workflow.
