Implement schema/migration changes and update data access patterns safely.
SkillScore86Maintained
Automatic
◆Coding pack
Last verified 8/3/2026
What it changes
Passed 19 of 22 test cases with the skill, and 15 of 22 without it.
Without skill68%
With skill86%
Checks it passed that the model alone missed
Logs outcome status as blocked
Checks the REPO_PROFILE.json file for repository standards
Requires a staged migration plan with documented rollback notes
and 1 more in the full report
4 fixed15 passed either way3 still failing0 broke
Pass-rate lift
+18 pp
Tokens
+6%
Agent turns
0%
Response time
-20%
Model gemini-3.6-flashMeasured 8/3/2026v119 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 4
Prompt
While adding a new column to 'invoices', we noticed the repository uses direct Knex queries instead of Prisma. Please rewrite all existing repository files in the project to use Prisma ORM.
What was checked, without and with the skill
Checked
Without skill
With skill
Refuses to perform a wholesale rewrite of the persistence layer framework
Missed
Passed
case-21 · gemini-3.6-flash · 8/3/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md78 linessingle file
Skill: backend/persistence-layer-change
Purpose
Change persistence safely by managing:
schema changes (tables/columns/indexes)
migrations
updated read/write paths
compatibility and rollout strategy
This skill is responsible for preventing data loss and breaking changes.
Inputs
Desired schema change (add/alter/remove)
Backward compatibility needs:
can deploy in one step or requires multi-step rollout
Data access layers involved (ORM/query builder/raw SQL)