skills.rest
tale-project
tale-projectOFFICIAL
Explore all skills by this author →
WebsiteGitHub

verify

Verify backend and frontend outcomes via Convex MCP and Playwright MCP.

20|5|Updated Nov 30, 2025
Search Tags:#testing#e2e#playwright#ci-cd#verify#convex
One-click install
npx skills add https://github.com/tale-project/tale --skill verify-tale-project
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/tale-project/tale/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/tale-project/tale --skill verify-tale-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifying changes requires evidence from real execution across backend and frontend rather than reliance on diffs. This Skill guides teams to observe outcomes, ensure tests pass, and codify findings into repeatable checks before shipping.

Core Features & Use Cases

  • Escalates from static checks to live backend verification on Convex MCP and UI validation via Playwright MCP.
  • Produces rerunnable tests that codify manual verifications into CI-ready artifacts.
  • Supports end-to-end verification for fixes, PRs, and feature changes across backend and frontend.
  • Guides tracing and evidence collection (logs, screenshots) to justify acceptance.

Quick Start

Run the /verify command after making changes to observe the actual outcome and attach the resulting evidence.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify code changes by observing real outcomes instead of just checking diffs?▼

To verify changes by real outcomes, you run the /verify command to escalate from static checks to live backend verification on Convex MCP and UI validation via Playwright MCP, ensuring observed results match expectations.

How do I automate end-to-end UI and backend verification for my PRs?▼

You can automate end-to-end verification by running the /verify command after making changes, which validates the backend on Convex MCP and the frontend UI via Playwright MCP to confirm tests pass.

Can I use Playwright MCP to validate frontend changes during CI-CD pipelines?▼

Yes, the verification process uses Playwright MCP for frontend UI validation and codifies the verified outcomes into rerunnable tests and CI-ready artifacts that guard future changes in your pipeline.

What's the best way to codify manual backend verifications into rerunnable tests?▼

The best way to codify manual verifications is to run the /verify command, which traces outcomes on Convex MCP and produces rerunnable tests and CI-ready artifacts from the collected evidence.

Why should I verify changes through real execution rather than relying on diffs?▼

Verifying changes through real execution provides evidence from actual backend and frontend behavior, ensuring tests pass and justifying acceptance with traced evidence like logs and screenshots rather than relying on diffs.

Does verification work with Convex MCP for live backend checks?▼

Yes, the verification process escalates from static checks to live backend verification directly on Convex MCP, confirming that the observed backend results match your expectations before shipping.

Related Skills

Explore More Software Engineering Skills→
treesus6treesus6
1

erne-setup-device

Install and configure the ERNE agent-device MCP server for iOS and Android simulator control.

Community
Intermediate
heaptracetechnologyheaptracetechnology
13

contract-test

Automate API contract testing with schema validation and OpenAPI checks.

Community
Advanced
krzemienskikrzemienski
2

web-validation

Automates browser-based validation of web applications for runtime issues, visual regressions, and more.

Community
Advanced
robertzengcnrobertzengcn

browse

Automate headless browser navigation, interaction, and visual verification with Playwright-based Chromium.

Community
Advanced