القائمة
Guard check to confirm the summary report file exists on disk before ending a failure-analysis session. Use as the final check in step 7 of the orchestration workflow.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | report-state |
| description | Guard check to confirm the summary report file exists on disk before ending a failure-analysis session. Use as the final check in step 7 of the orchestration workflow. |
Verify that the summary report has been written to disk before closing the session.
SummaryReports/summary-report.md existssummary-report skill and write the file before proceeding"Summary report written to SummaryReports/summary-report.md" — include the file pathIf SummaryReports/summary-report.md already existed from a previous session:
summary-report-2.md)This skill is a hard gate. The session must not end until one of these is true:
SummaryReports/summary-report.md was created this session, ORsummary-report-N.md) was created this sessionA chat message summarising the session does NOT satisfy this gate.
Triage and analyze Playwright test failures. Use when: test failures need diagnosis, cross-pattern analysis of shared root causes, categorizing UI vs API failures, reading test-results/ error reports, proposing fixes for broken tests.
Generate a detailed failure analysis summary report. Use when: creating summary-report.md, documenting test fixes, generating effort savings analysis, producing iteration summaries, writing failure analysis documentation.