Enforces quality standards for BodyLife CRM. Validates domain logic, database consistency, and UI flows.
Install
mkdir -p .claude/skills/bodylife-quality-gates && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18295" && unzip -o skill.zip -d .claude/skills/bodylife-quality-gates && rm skill.zipInstalls to .claude/skills/bodylife-quality-gates
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Implementation guidance for BodyLife CRM quality gates across the v1 roadmap. Use when Codex defines, adds, or reviews tests for domain rules, application commands, PostgreSQL integration, migrations, report consistency, audit matrix coverage, Playwright tablet/phone E2E, restore rehearsals, go-live checks, or milestone acceptance criteria.Key capabilities
- →Define domain tests for membership math
- →Define application command tests for permissions and idempotency
- →Define PostgreSQL integration tests for migrations and FKs
- →Define report consistency tests for daily totals
- →Define audit tests for event matrix coverage
- →Define UI E2E tests for Playwright tablet and phone flows
How it works
The skill provides guidance on defining and reviewing various types of quality gates for BodyLife CRM, ensuring that implementations are proven through testing rather than assumptions.
Inputs & outputs
When to use bodylife-quality-gates
- →Verifying membership logic
- →Testing database migrations
- →Checking E2E Playwright flows
About this skill
BodyLife Quality Gates
Use this skill whenever implementation needs proof, not just code. The risky parts of BodyLife CRM are membership math, command atomicity, audit, reports, PostgreSQL constraints, UI double submits, and restore readiness.
Start Here
Read references/source-map.md, then pick the gate that matches the milestone or workflow.
Gate Types
- Domain tests: inclusive dates, remaining visits, negative visits, first negative date, freeze/non-working union days, canceled facts, backdated entries, snapshot immutability.
- Application command tests: permissions, validation, idempotency, stale/concurrency behavior, transaction rollback, recalculation hook, business audit, canonical reread target.
- PostgreSQL integration tests: migrations, FKs/checks, partial unique indexes, row locks, source facts vs derived cache rebuild, report query indexes.
- Report consistency tests: daily totals equal drill-down rows, corrections/cancellations are visible, Memberships state matches profile and reports.
- Audit tests: event matrix coverage, required fields, append-only policy, shared account/session labeling, backfill/fallback labels.
- UI E2E tests: Playwright tablet and phone flows for search, profile, issue membership, mark/cancel visit, payment correction, freeze, daily report, audit/history, busy/disabled duplicate-submit behavior.
- Operations tests: health check, structured log correlation, PII masking review, restore rehearsal, restore-check, paper fallback reconciliation drill.
Milestone Rule
Every milestone should finish in a deployable, testable state. Do not accept code that only works through manual DB edits, UI optimism, or untested assumptions about PostgreSQL/hosting.
Minimum Regression Shape
- Run build/analyzers and unit tests.
- Run PostgreSQL-backed integration and migration checks for persistence changes.
- Run relevant command/domain/report tests for changed workflows.
- Run Playwright on tablet and phone viewports for reception UI changes.
- Run restore rehearsal checks before production readiness claims.
Guardrails
- Do not use SQLite/EF InMemory as proof for production persistence behavior.
- Do not skip tests around recalculation, audit, reports, or idempotency because the UI looks right.
- Do not call production ready before backup retention is configured and restore rehearsal has passed.
- Do not approve reports that duplicate Memberships formulas.
- Do not accept command success when source facts, recalculation, audit, and canonical reread can diverge.
When not to use it
- →When the task is not related to BodyLife CRM quality gates
- →When the user wants to use SQLite/EF InMemory as proof for production persistence
- →When the user wants to skip tests around recalculation, audit, or reports
Limitations
- →Specific to BodyLife CRM quality gates
- →Does not accept code that only works through manual DB edits or UI optimism
- →Does not approve reports that duplicate Memberships formulas
How it compares
This workflow enforces a complete testing strategy across multiple layers of BodyLife CRM, ensuring reliable quality assurance unlike a fragmented or incomplete testing approach.
Compared to similar skills
bodylife-quality-gates side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| bodylife-quality-gates (this skill) | 0 | 20d | No flags | Advanced |
| generating-database-seed-data | 10 | 10d | Review | Intermediate |
| test-with-postgres | 1 | 2mo | Review | Intermediate |
| managing-database-tests | 1 | 10d | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
generating-database-seed-data
jeremylongshore
Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.
test-with-postgres
storj
Run unit tests that require PostgreSQL. Use this skill when the user wants to run tests with PostgreSQL database backend. Automatically handles checking for and configuring a PostgreSQL Docker container.
managing-database-tests
jeremylongshore
Test database testing including fixtures, transactions, and rollback management. Use when performing specialized testing. Trigger with phrases like "test the database", "run database tests", or "validate data integrity".
sql-optimization-patterns
wshobson
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.
drizzle-orm
EpicenterHQ
Drizzle ORM patterns for type branding and custom types. Use when working with Drizzle column definitions, branded types, or custom type conversions.
postgres-patterns
affaan-m
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices.