skills.rest
BlocUnited-LLC
BlocUnited-LLCOFFICIAL
Explore all skills by this author →
GitHub

persistence-change

Review and implement persistence contract changes with structured impact reports.

14|1|Updated Jan 8, 2026
Search Tags:#migrations#code generation#persistence#contract review#runtime integration#test impact#database-intent
One-click install
npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill persistence-change
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: persistence-change
Source: https://github.com/BlocUnited-LLC/mozaiks/tree/main/.claude/skills/persistence-change
Command: npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill persistence-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persistence contract changes are easy to get wrong, causing mismatched artifacts, broken runtime storage behavior, and inconsistent database intent and migration outputs.

Core Features & Use Cases

  • Contract-focused review and implementation: Examine and update database_intent, database_migrations, and backend persistence support files (backend/repo.py, backend/policy.py, backend/schemas.py) to ensure generated artifacts remain consistent.
  • Generated module boundary guidance: Validate how ModuleContext.persistence maps to ctx.persistence and prevents non-canonical runtime usage (e.g., avoiding ctx.db).
  • Change routing and impact assessment: Identify which companion routing skills to add (runtime-change vs appgenerator-change) and enumerate layer, runtime/platform impact, workspace impact, affected persistence artifacts, required tests, and compatibility risk.

Quick Start

Ask the AI to review and implement the requested persistence contract change while reporting which artifacts and tests are impacted.

Frequently Asked Questions about persistence-change

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

FAQPage Schema
How do I update persistence contracts without breaking database migrations?▼

Updating persistence contracts safely requires reviewing database_intent, database_migrations, and backend support files to ensure generated artifacts remain consistent and prevent drift between planning objects and runtime artifacts.

What causes drift between database intent and runtime persistence artifacts?▼

Drift between database intent and runtime artifacts occurs when persistence contract changes bypass canonical support files, reintroduce deprecated locations like ctx.db, or fail to align ModuleContext.persistence mappings with generated module boundaries.

How do I assess the impact of changing database intent configurations?▼

Assessing database intent configuration changes involves generating a structured impact report that enumerates affected layers, runtime and platform effects, workspace impacts, impacted persistence artifacts, required tests, and compatibility risk.

When do I need to review generated module boundaries for persistence updates?▼

You need to review generated module boundaries when updates touch config/database_intent.json or config/database_migrations outputs, requiring validation that ModuleContext.persistence maps correctly to ctx.persistence and prevents non-canonical runtime usage.

Can I use persistence-change for backend schema and policy file updates?▼

Yes, persistence-change applies to backend persistence support files including backend/repo.py, backend/policy.py, and backend/schemas.py, ensuring contract-focused review and implementation keeps generated artifacts consistent across the stack.

What are the limitations of automated persistence contract reviews?▼

Automated persistence contract reviews must strictly follow repository persistence truth rules and avoid reintroducing deprecated persistence locations, meaning manual verification is still needed for complex compatibility risks across runtime and platform effects.

Related Skills

Explore More Software Engineering Skills→
hachejhachej
45

setup-matt-pocock-skills

Configure repository issue tracking, triage labels, and domain documentation layouts.

Community
Intermediate
BlocUnited-LLCBlocUnited-LLC
14

appgenerator-change

Review AppGenerator changes against canonical app-bundle contracts and UI quality gates.

Official
Advanced
BlocUnited-LLCBlocUnited-LLC
14

control-plane-refinement-change

Evaluates Tailwind code and produces a report of detected smells and inconsistencies.

Official
Advanced
KamiJeongKamiJeong

docguard-review

Analyze documentation collections for drift, coverage gaps, and broken cross-references.

Community
Advanced