SkillPublic
qa-data-integrity
Verify persistence, constraints, migrations, duplicates, orphans, and cleanup of test data. Use when testing anything that writes data or after schema changes and deploys.
71
Quality
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Securityby
Passed
No findings from the security scan
Data Integrity
Procedure
- For each write in a journey, read the row back and check owner, status, timestamps (with timezone), and foreign keys.
- Constraints: uniqueness under concurrent requests, and no null in required fields.
- Orphans: runs without owners, payments without orders, and files without records (pattern G1).
- Migrations: apply on a copy, check row counts and checksums before and after, and check rollback.
- Retention: paid and active records are protected from cleanup jobs.
- Cleanup: delete only rows tagged with the run ID. Log every deletion and every failure in
cleanup.csv. - Verify cleanup: query or count leftover records by tag after deleting. A 200 response from DELETE is not proof.
Exit criteria
Integrity queries return zero violations, and the cleanup ledger is reconciled.
- Repository
itsablabla/qa-bug-agent-skills
- Revision
9a6f628
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.