Context
The operator pointed out that ticket-create and pull-request skills (along with unit-test and whitebox-e2e) often prompt agents to run npx playwright test by default to verify changes. However, Neo.mjs uses Playwright in a highly custom way with multiple specific configuration files (e.g., unit test mode, workers, explicit chromium settings).
The Problem
Default npx playwright test calls ignore these custom configs unless specifically pointed to them. This creates a risk where tests that should work suddenly fail, confusing agents and leading to false-negative test cycles and hallucinated "fixes" before PR submission or ticket creation.
The Architectural Reality
The workspace contains multiple custom configurations (playwright.config.unit.mjs, playwright.config.e2e.mjs, playwright.config.integration.mjs, etc.) in test/playwright/. The default Playwright CLI commands do not map to these correctly without explicit --config arguments.
The Fix
Harden the skill triggers (the frontmatter description fields) in .agents/skills/ticket-create/SKILL.md, .agents/skills/pull-request/SKILL.md, .agents/skills/unit-test/SKILL.md, and .agents/skills/whitebox-e2e/SKILL.md to explicitly warn agents:
CRITICAL: Do NOT run default npx playwright test to verify changes; Neo uses multiple custom playwright configs which must be explicitly targeted.
Acceptance Criteria
Out of Scope
Modifying the Playwright configurations themselves. Changing how tests are executed by the CI.
Origin Session ID: a15ded93-0e4c-4b09-a2cf-21db6e765841
Retrieval Hint: "custom playwright config skill triggers ticket-create pull-request unit-test whitebox-e2e false negative"
Context The operator pointed out that
ticket-createandpull-requestskills (along withunit-testandwhitebox-e2e) often prompt agents to runnpx playwright testby default to verify changes. However, Neo.mjs uses Playwright in a highly custom way with multiple specific configuration files (e.g., unit test mode, workers, explicit chromium settings).The Problem Default
npx playwright testcalls ignore these custom configs unless specifically pointed to them. This creates a risk where tests that should work suddenly fail, confusing agents and leading to false-negative test cycles and hallucinated "fixes" before PR submission or ticket creation.The Architectural Reality The workspace contains multiple custom configurations (
playwright.config.unit.mjs,playwright.config.e2e.mjs,playwright.config.integration.mjs, etc.) intest/playwright/. The default Playwright CLI commands do not map to these correctly without explicit--configarguments.The Fix Harden the skill triggers (the frontmatter
descriptionfields) in.agents/skills/ticket-create/SKILL.md,.agents/skills/pull-request/SKILL.md,.agents/skills/unit-test/SKILL.md, and.agents/skills/whitebox-e2e/SKILL.mdto explicitly warn agents:CRITICAL: Do NOT run default npx playwright test to verify changes; Neo uses multiple custom playwright configs which must be explicitly targeted.Acceptance Criteria
.agents/skills/unit-test/SKILL.mdfrontmatter is updated with the custom Playwright warning..agents/skills/whitebox-e2e/SKILL.mdfrontmatter is updated with the custom Playwright warning..agents/skills/ticket-create/SKILL.mdfrontmatter is updated with the custom Playwright warning..agents/skills/pull-request/SKILL.mdfrontmatter is updated with the custom Playwright warning.Out of Scope Modifying the Playwright configurations themselves. Changing how tests are executed by the CI.
Origin Session ID: a15ded93-0e4c-4b09-a2cf-21db6e765841 Retrieval Hint: "custom playwright config skill triggers ticket-create pull-request unit-test whitebox-e2e false negative"