القائمة
after making changes, run end-to-end tests to ensure that the product still works
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/ForceInjection/domain-driven-design-skills --skill end-to-end-testsيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Conduct deep academic research for philosophy, neuroscience, cognitive science, and theoretical computer science (computability, complexity, AI theory, logic). Use when user asks to: research academic topics, find scholarly papers, conduct literature reviews, analyze citations, synthesize research findings, explore philosophical arguments, investigate consciousness/cognition, study computability/decidability/Turing machines, or analyze academic debates. Triggers on: 'research papers', 'literature review', 'academic sources', 'scholarly articles', 'philosophy of mind', 'computability theory', 'neuroscience studies', 'find papers on', 'what does the research say'.
Create clear action plans with steps, success criteria, and risk awareness. Use before implementing features, making changes, starting projects, or anytime you need a roadmap to success. Triggers on "plan this", "how should we approach", "what's the strategy", "steps to complete", or when facing complex multi-step work.
Add keyboard navigation to a feature using CommandRegistryService. Use when implementing keyboard shortcuts, vim-style navigation, or hotkeys for a page or component.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | end-to-end-tests |
| description | after making changes, run end-to-end tests to ensure that the product still works |
| allowed-tools | make, go |
When you are done making changes, run all end-to-end tests through this command:
make cuke
If the exit code is 1, read the error messages and fix all errors, then re-run the end-to-end tests until they run successfully and exit with code 0.
End-to-end tests are defined in the "features" folder. They are written in the Gherkin language and execute using Cucumber for Go.
If an end-to-end test fails, you can re-run only this test to verify that your fix works:
@debug @this tag to a specific scenariomake cukethis to execute only the tagged scenario@debug @this tags