القائمة
Analyze failing tests before changing code. Distinguish implementation bugs, test bugs, flaky behavior, and environment problems, then explain the likely root cause.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Turn a specification into a concrete architecture with stable contracts, file boundaries, ownership, and risk analysis. Use this when acting as the architecture writer for a task.
Run the project verification stack after code changes. Trigger on code changes and stop on the first failure, fix it, then rerun the full stack from the top.
Verify that newly created files follow the repo's existing directory layout, naming conventions, and export patterns. Trigger when a new file is created.
Break architecture into execution-ready sub-tasks with clear ownership, dependencies, and contract references. Use this when acting as the planner for a task.
Use Playwright for browser automation, UI validation, E2E tests, and interaction debugging. Useful for flows that need real page navigation, assertions, screenshots, or request interception.
Final merge-readiness check after gates pass. Confirms verification is green, changed files are clean, and obvious release blockers are gone before merge.
| name | test-failure-analysis |
| description | Analyze failing tests before changing code. Distinguish implementation bugs, test bugs, flaky behavior, and environment problems, then explain the likely root cause. |
| owner | any |
| trigger | test_failure |
| version | 2 |
Use this when verification or test commands fail.
For each failure, answer:
Do not blindly rewrite tests just to get green.
