Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

debug-e2e-test

Estrellas38

Forks5

Actualizado15 de julio de 2026 a las 14:44

How to debug the e2e test failure

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

lawrenceching

lawrenceching/SMM

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

Explorador de archivos

2 archivos

SKILL.md

readonly

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"]

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

Más de este repositorio

mismo repositorio

wlap-context

lawrenceching/SMM

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

2026-07-1438

wlap-plan

lawrenceching/SMM

How to architect or design like a PROFESSIONAL developer or architect

2026-07-1438

wlap-plan

lawrenceching/SMM

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

2026-07-1438

wlap-review

lawrenceching/SMM

How to review changes like a professional developer

2026-07-1438

test-like-a-pro

lawrenceching/SMM

How to write automation test like a professional developer

2026-07-1438

wlap-wrapup

lawrenceching/SMM

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

2026-07-1438

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"]

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