debug-e2e-test

スター38

フォーク5

更新日2026年7月15日 14:44

How to debug the e2e test failure

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

lawrenceching

lawrenceching/SMM

ダウンロード

Debug e2e test

Create Document - Draft the bug document using template in .agents/docs/bug/[brief-the-bug].md
Fill Document Accurately - Understand the codebase and update "Code Path" section with accurate description. This is the key part for debugging.
Start Debugging - Move the document status from "draft" to "wip". Analyze the suspicious one by one, and update their status to "proved" or "rejected" accordingly. If information is not enough, add logs, reproduce the bug, collect new logs to help debugging.
Fix - If suspicious was proved, propose the solution, update the bug document , and ask use to review and approved. Apply the fix ONLY WHEN user is approved
Wrap Up - Update bug document to "done" status, suspicious to "fixed" status

このリポジトリの他の Skills

同じリポジトリ

Have thorough understanding of codebase and describe the context like a professional developer

How to architect or design like a PROFESSIONAL developer or architect

How to architect, design, code and test the complex requirement like a professional developer

How to review changes like a professional developer

How to write automation test like a professional developer

Have thorough understanding of codebase and describe the context like a professional developer

name	debug-e2e-test
version	0.0.1
description	How to debug the e2e test failure
user-invocable	true
disable-model-invocation	true
allowed-tools	["Read","Write","Edit","Bash","Glob","Grep","WebFetch","WebSearch","AskQuestion"]

Create Document - Draft the bug document using template in .agents/docs/bug/[brief-the-bug].md
Fill Document Accurately - Understand the codebase and update "Code Path" section with accurate description. This is the key part for debugging.
Start Debugging - Move the document status from "draft" to "wip". Analyze the suspicious one by one, and update their status to "proved" or "rejected" accordingly. If information is not enough, add logs, reproduce the bug, collect new logs to help debugging.
Fix - If suspicious was proved, propose the solution, update the bug document , and ask use to review and approved. Apply the fix ONLY WHEN user is approved
Wrap Up - Update bug document to "done" status, suspicious to "fixed" status