foreman-web-testing
Headless end-to-end / web-app testing for the Foreman e2e stage. Derive end-to-end tests from the PRD's User Flows, drive the real application the way a user would (browser flows, screenshots, accessibility checks for web apps), make them pass via the configured e2e command, and emit the FOREMAN-SUMMARY block Foreman parses.
npx skills add VisionForge-OU/foreman --skill foreman-web-testing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# foreman-web-testing (Adapted from Anthropic's `web-app-testing` skill and the e2e half of `foreman-tdd` — see NOTICE. Made stack-agnostic: the e2e runner is injected by Foreman from `config.yaml` (`commands.e2e`), not hard-coded to Playwright; for non-browser projects the same flow-driven discipline applies through whatever e2e command the project declares. Added Foreman's evidence + FOREMAN-SUMMARY contract.) You run **headless** in the integration worktree after every issue has landed. Your job is to prove the *whole feature works end-to-end* along the journeys the PRD promised — not to re-run unit tests. Implement the e2e tests, make them pass, save evidence, then stop with exactly one FOREMAN-SUMMARY block. ## Inputs (injected by Foreman in the prompt) - The approved **PRD body** — its **`## User Flows`** section is your test charter. - The **e2e command** for the project (`commands.e2e`, e.g. `npx playwright test` or `pytest -m e2e`). Foreman re-runs it itself to verify, so your tests must actually pass under it. - The **evidence directory** you must populate before claiming done. ## Workflow ### 1. Derive flows from the PRD Turn each user flow into a concrete end-to-end sce
- Inputs (injected by Foreman in the prompt)
- Workflow
- 1. Derive flows from the PRD
- 2. Drive the real application
- 3. Make them pass, then verify
- 4. Save evidence and summarise
- Required output: FOREMAN-SUMMARY
What does the foreman-web-testing skill do?
Headless end-to-end / web-app testing for the Foreman e2e stage. Derive end-to-end tests from the PRD's User Flows, drive the real application the way a user would (browser flows, screenshots, accessibility checks for web apps), make them pass via the configured e2e command, and emit the FOREMAN-SUMMARY block Foreman parses.
How do I install it?
Run `npx skills add VisionForge-OU/foreman --skill foreman-web-testing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From VisionForge-OU/foreman, a repository with 421 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.