Install the Playwright CLI skill for Codex and other agents, not only Claude Code
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 80/100
Línea de trabajo
Empieza por config.playwright-cli.yaml para ver cómo el hook posterior al inicio instala la skill; después, lee el README y tests/test.bats para conocer la configuración y las aserciones existentes. Añade compatibilidad para elegir los destinos claude y agents mediante PLAYWRIGHT_CLI_SKILLS, manteniendo claude como valor predeterminado y haciendo que los fallos del hook no sean fatales. La tarea estará completa cuando el README documente ambos destinos y las pruebas cubran el comportamiento configurado y el predeterminado, incluidas las rutas de skill esperadas.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Is there an existing issue for this?
- I have searched the existing issues
Is your feature request related to a problem?
Problem
The post-start hook in config.playwright-cli.yaml runs playwright-cli install --skills without a value:
- exec: "which playwright-cli > /dev/null 2>&1 && playwright-cli install --skills || true"
Playwright CLI treats that as claude:
$ playwright-cli install --help
--skills install skills, possible values: claude (default), agents.
So the skill only lands in .claude/skills/playwright-cli/. Codex, and other agents that read .agents/skills/, never get it, although the CLI and Chromium are installed and work for them.
Steps to reproduce
ddev add-on get e0ipso/ddev-playwright-cli && ddev restartddev exec ls .agents/skills: there's noplaywright-cli.- In Codex inside the web container, the skill isn't listed (
codex debug prompt-input "hi"doesn't mention it).
Running ddev exec playwright-cli install --skills agents by hand writes .agents/skills/playwright-cli/, and Codex picks it up.
Versions: add-on v1.2.3, @playwright/cli 0.1.24, Codex CLI 0.169.0, DDEV ≥ 1.25.
Current workaround
A project-owned .ddev/config.playwright-cli-codex.yaml:
hooks:
post-start:
- exec: "which playwright-cli > /dev/null 2>&1 && playwright-cli install --skills agents || true"
DDEV runs the hooks from every config.*.yaml file, so the add-on's own hook still runs too.
Describe your solution
Let projects choose the targets with an environment variable, keeping today's behavior as the default:
#ddev-generated
hooks:
post-start:
# Install the Playwright CLI skill for each target in PLAYWRIGHT_CLI_SKILLS
# ("claude", "agents"; default "claude"), if the CLI is available.
- exec: 'which playwright-cli > /dev/null 2>&1 && for target in ${PLAYWRIGHT_CLI_SKILLS:-claude}; do playwright-cli install --skills "$target"; done || true'
web_environment:
- PLAYWRIGHT_MCP_CONFIG=/var/www/html/.ddev/playwright-cli/cli.config.json
A project opts in with:
ddev dotenv set .ddev/.env.web --playwright-cli-skills="claude agents"
ddev restart
Setting web_environment in a project config.*.yaml file would work too.
- Default unchanged: existing projects don't suddenly get an
.agents/skills/folder they would need to ignore in Git. - Failures stay non-fatal:
|| truekeeps the hook from breakingddev start, as it does today. - README: document the variable and the two targets.
- Test: extend
tests/test.bats. WithPLAYWRIGHT_CLI_SKILLS="claude agents", assert that.agents/skills/playwright-cli/SKILL.mdexists. With the default, keep the current.claude/skills/playwright-cliassertion and check that.agents/skills/playwright-clidoesn't exist.
Describe alternatives
No response
Additional context
- Always install both targets: no configuration, but every project gets
.agents/skills/playwright-cli/and has to ignore it in Git. - Detect the agents in use from folders such as
.codex/or.agents/: works without configuration, but it's implicit and easy to get wrong.
- Lenguaje dominante
- Shell
- Estrellas
- 6
- Forks
- 2
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Issues similares
-
bump version [nginx2root]Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Update: sanitize-htmlAbierto📦 Update Request
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
cdnjs/packages#2225 · 1 comentario ·
Los mantenedores suelen responder en 3 días
-
good first issue help wanted testing
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
-
[issue]: Ventoy2Disk.sh can leave the end of VTOYEFI unwritten (xzcat | dd without iflag=fullblock)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
bot:ai-assisted component:platform-js status:untriaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
midnightntwrk/platform-js#69 ·
Los mantenedores suelen responder en 1 día