Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Raise the proof standard in create-verification-skill and add a Playwright reference

Abierto
  • ¿Algo no está bien?
#29 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
playwright, typescript
Área
testing, tooling

Línea de trabajo

Start with the implementation of create-verification-skill and the existing generated skill content; the issue does not name file paths, so trace the generator's entry point and its web-surface detection. Check current Playwright documentation for the required reference details, then run the generator on web and non-web projects. Done means the generated skill applies the new proof standards, links the reference only for web surfaces, and passes the stated validation and build.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

ready-for-agent

Parent

#15

What to build

The verification skill that create-verification-skill generates holds a stricter proof standard. Any new console error blocks done. Accessibility violations on changed routes block done, and results that axe marks incomplete go to a human to review. Visual baselines change only in the same commit as an intentional UI change, never to make a test pass.

For web surfaces, the generated skill links a Playwright reference with the course's rules: the locator order, banned waits, storage-state auth, HAR recording, and test.step. The reference opens by saying that Playwright drives the browser to prove a change and Chrome DevTools is for debugging. It names the project's Playwright test runner for proof, and @playwright/cli for an interactive loop when the agent works in a shell. Playwright MCP is the fallback when the host has no shell loop.

Acceptance criteria

  • The proof standards in the generated skill include the console-error, accessibility, and baseline rules.
  • The Playwright reference exists and is linked only for web surfaces.
  • Run on a web project, create-verification-skill produces a skill with the new standards and the reference link. Run on a non-web project, it produces no reference link.
  • Playwright facts match current docs, including @playwright/cli and npx playwright test --debug=cli.
  • The skill passes the authoring-a-skill validation and the build.
Lenguaje dominante
TypeScript
Estrellas
0
Forks
0
Merge medio
3 h 33 min
PR fusionados (30 d)
13

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de gregogun/gstack

Todos los issues de gregogun/gstack

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.