verify-fix

Map code changes to Playwright E2E tests and execute them against production.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/coopeverything/TogetherOS --skill verify-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-fix
Source: https://github.com/coopeverything/TogetherOS/tree/main/.claude/skills/verify-fix
Command: npx skills add https://github.com/coopeverything/TogetherOS --skill verify-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature fix or feature completion claims by validating that changes actually work end-to-end in production-like environments before you declare a fix deployed or a feature complete.

Core Features & Use Cases

  • End-to-end verification: Run the relevant verification tests against production to confirm fixes.
  • Automated test mapping: Identify affected modules from recent changes and map them to the appropriate verification tests.
  • Clear reporting: Consolidate results so you can confidently claim completion or iterate.

Quick Start

After deploying a fix, run:

  • Identify affected modules from recent commits: git diff HEAD~3 --name-only | grep -E "^(apps|packages)" | cut -d'/' -f3 | sort -u
  • Run verification tests for affected modules: BASE_URL=https://coopeverything.org npx playwright test tests/e2e/verify/ --grep "<module>"
  • If tests pass, THEN claim fix is complete
  • If tests fail, fix the issue and repeat

Frequently Asked Questions about verify-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify that a bug fix actually works before declaring it complete?

End-to-end verification confirms fixes work by running Playwright-based tests against production-like environments. Identify affected modules from your recent commits, map them to relevant E2E tests, execute authenticated tests, validate UI and database outcomes, then clean up test data before claiming success.

Can I automate testing to verify fixes across multiple modules?

Yes. Automated test mapping identifies affected modules from code changes and routes them to appropriate Playwright E2E tests. The Skill executes these tests, validates results across UI and database layers, and reports outcomes so you can confidently confirm or iterate on fixes.

What's the best way to prevent incomplete fix claims in release management?

Run end-to-end verification tests before marking fixes deployed. This Skill maps recent changes to test suites, executes authenticated E2E tests in production environments, validates both UI and data layer outcomes, and cleans up afterward—blocking premature completion claims.

Do I need to manually identify which tests to run for each code change?

No. The Skill automates test mapping by analyzing affected modules from your commits and identifying the relevant Playwright tests to execute. You only need to deploy your change; the Skill handles test discovery and execution.

How does end-to-end testing with Playwright validate database changes alongside UI changes?

Playwright E2E tests execute authenticated user workflows and validate outcomes across both UI interactions and database state. The Skill runs these tests against production, checks UI rendering and data integrity, then cleans up test data before reporting pass or fail.

What happens if verification tests fail after deploying a fix?

The Skill reports test failures clearly so you can iterate. Fix the underlying issue and re-run verification—the Skill re-executes tests and cleans up test data again until all verifications pass before confirming completion.