database-schema-migrations
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Data
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: database-schema-migrations
description: > Use when this capability is needed. Manage schema design, migrations, and database operations.…
category: data
runtime: no special runtime
---
# database-schema-migrations output preview
## PART A: Task fit
- Use case: > Use when this capability is needed. Manage schema design, migrations, and database operations. CREATE TABLE IF NOT EXISTS resources ( id TEXT PRIMARY KEY, title TEXT NOT NULL, runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Key Responsibilities / Migration Pattern / Naming Convention” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “> Use when this capability is needed. Manage schema design, migrations, and database operations. CREATE TABLE IF NOT EXISTS resources ( id TEXT PRIMARY KEY, title TEXT NOT NULL, runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Key Responsibilities / Migration Pattern / Naming Convention” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Key Responsibilities / Migration Pattern / Naming Convention”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: database-schema-migrations
description: > Use when this capability is needed. Manage schema design, migrations, and database operations.…
category: data
source: tomevault-io/skills-registry
---
# database-schema-migrations
## When to use
- > Use when this capability is needed. Manage schema design, migrations, and database operations. CREATE TABLE IF NOT E…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Key Responsibilities / Migration Pattern / Naming Convention” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "database-schema-migrations" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Key Responsibilities / Migration Pattern / Naming Convention
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Database Schema Migrations
Manage schema design, migrations, and database operations.
Key Responsibilities
- Design and version schema changes.
- Write migration scripts.
- Ensure database compatibility.
- Provide rollback-safe migration steps.
Migration Pattern
-- Good: Idempotent migration
CREATE TABLE IF NOT EXISTS resources (
id TEXT PRIMARY KEY,
title TEXT NOT NULL,
owner_id TEXT NOT NULL,
created_at INTEGER DEFAULT (unixepoch())
);
-- Good: Safe index addition
CREATE INDEX IF NOT EXISTS idx_resources_owner ON resources(owner_id);Naming Convention
- Migration files:
YYYYMMDD_description.sql - Tables: snake_case, plural (e.g.,
resources,permissions) - Columns: snake_case (e.g.,
resource_id,created_at)
Constraints
- Migrations must be idempotent and reversible.
- Indexes must be added in a way that doesn't break existing queries.
- Use timestamp-prefixed filenames.
- Always provide rollback scripts.
Checklist
- Migration is idempotent (can run multiple times safely).
- Rollback migration tested.
- Indexes use
IF NOT EXISTS. - Foreign keys defined where applicable.
- Migration logged in migration history table.
References
references/migration-patterns.md- Common migration patterns by database typereferences/rollback-strategies.md- Safe rollback strategies
Source: d-o-hub/github-template-ai-agents — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review