wellmate-verification

Validates WellMate code changes through build checks, architecture review, and UI verification.

Updated Jan 1, 2026

Search Tags:#typescript #code review #verification #quality gate #ui testing #git diff #local-first

Ready to run

npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill wellmate-verification-sarkarshivaditya-lab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wellmate-verification
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/wellmate/verification
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill wellmate-verification-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes that merely compile locally often hide regressions in architecture, offline behavior, or UI quality. This Skill enforces a structured verification gate so no WellMate change is marked complete without proper validation. ## Core Features & Use Cases - Build Verification: Runs TypeScript build commands, inspects compiler errors, lint output, and the final Git diff before sign-off. - Architecture Guardrails: Confirms local-first and offline behavior remain intact, Convex is not made authoritative, authentication is not required for local features, and locked files stay untouched. - UI Verification: Checks mobile layout, touch targets, responsiveness, accessibility, animations, and reduced-motion behavior for visual changes. - Use Case: After implementing a new offline-first feature in the WellMate app, run this verification checklist to confirm the build passes, no unnecessary dependencies were added, and the diff matches the requested scope. ## Quick Start Verify my recent WellMate changes against the completion gate before marking the task done.

Frequently Asked Questions about wellmate-verification

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

FAQPage Schema

How do I verify TypeScript changes before marking a task complete?▼

Run the relevant TypeScript build command, inspect compiler errors and lint output, then review the final Git diff. Only claim completion after implementation exists, validation has been performed, and known failures are reported.

What should I check for local-first architecture changes?▼

Confirm local-first and offline behavior remain intact, Convex is not accidentally made authoritative, and authentication is not required for local functionality. Also verify locked files were not modified and no unnecessary dependencies were introduced.

How do I verify UI changes for mobile and accessibility?▼

Check mobile layout, touch targets, responsive behavior, accessibility, and animation behavior including reduced-motion support. Also confirm there is no visual regression in surrounding components.

When is a code change actually considered complete?▼

A change is complete only when implementation exists, validation has been performed, the diff has been reviewed, known failures have been reported, and scope remains aligned with the request. Compiling locally is not sufficient.

Why does local compilation not guarantee a change is done?▼

Local compilation only proves the code builds, not that architecture constraints, offline behavior, or UI quality are preserved. Hidden regressions in dependencies, locked files, or accessibility require explicit verification steps.