بنقرة واحدة
test-driven-development
Drive changes with Red→Green→Refactor; ensure behavior is verifiable and regression-safe.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Drive changes with Red→Green→Refactor; ensure behavior is verifiable and regression-safe.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use 4-phase root cause analysis (Observe, Hypothesize, Verify, Fix); avoid unverified patches.
Use Git worktrees to create parallel working directories safely; avoid branch-switch contamination.
Behavioral guidelines to reduce common LLM coding mistakes — Think Before Coding, Simplicity First, Surgical Changes, Goal-Driven Execution.
Enforce "no evidence = no completion"; run Gate Function verification before declaring done.
Pre-ship observability readiness checklist — ensures errors reach production monitoring, not just debug consoles.
Adversarial security and resilience analysis — auto-triggered during /review and /test based on task classification. Provides attack surface analysis, boundary testing, auth bypass attempts, dependency chain attacks, and Beast Mode stress testing.
| name | test-driven-development |
| description | Drive changes with Red→Green→Refactor; ensure behavior is verifiable and regression-safe. |
TDD uses the Red → Green → Refactor micro-cycle. First, define expected behavior. Next, use a minimal implementation to pass the test. Finally, organize the code structure.