Menu
Repository-specific workflow for creating or modifying Graft live Atlas/PostgreSQL migration SQL with Chinese database comments, globally unique versions, live/legacy boundaries, and deterministic validation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Repository-specific loop orchestrator for Graft multi-agent tasks. Use when one bounded task should run through repeated same-session serial worker-subagent rounds of `graft-multi-agent-task` under the default `topic-completion-loop` mode until the topic reaches `archive-ready`, becomes `blocked`, or no remaining batches stay in scope.
Repository-specific multi-agent coordination workflow for Graft. Use when the user explicitly wants subagent delegation, or when the current task cleanly splits into two or more disjoint slices across server, web, docs, or automation, and the main agent should keep ownership of review, validation, and final integration. `graft-boot` should assess whether this skill is justified before delegation starts.
Repository-specific workflow wrapper for Graft multi-agent tasks. Use when a task should be executed through `graft-multi-agent-batch`, and the slice may need `graft-task-closeout` plus `graft-commit` to finish with a safe handoff after validation.
Repository-specific end-of-task closeout workflow for Graft. Use when a task slice is ending and the agent needs to decide whether to emit only a next-step startup prompt or to commit the current validated slice first and then hand off safely. This is the default slice-end path for work started through `graft-boot`.
Manage reusable Graft AI-agent worktrees through guarded status, acquire, and release commands without treating directories or task branches as long-lived ownership.
Repository-specific Playwright browser workflow for inspecting, authenticating into, and interacting with the local Graft web UI. Use when Codex needs Graft browser screenshots, DOM text snapshots, login/auth verification with temp credentials, or simple click/fill/wait checks before normal web validation.
| name | graft-sql-migration |
| description | Repository-specific workflow for creating or modifying Graft live Atlas/PostgreSQL migration SQL with Chinese database comments, globally unique versions, live/legacy boundaries, and deterministic validation. |
Use this skill whenever a task creates or modifies migration SQL in Graft.
This skill owns SQL comment and migration validation workflow details. It does not replace root AGENTS.md,
server/AGENTS.md, ai-plan/design/governance/backend/数据库表设计与迁移规范.md, graft-table-design, Ent generation, Atlas migration
generation, or backend validation.
Use this skill when the task touches any of:
AGENTS.md.server/AGENTS.md.ai-plan/design/governance/backend/数据库表设计与迁移规范.md.graft-table-design first.CREATE TABLE must have Chinese COMMENT ON TABLE in the same migration file.CREATE TABLE column must have Chinese COMMENT ON COLUMN in the same migration file.ALTER TABLE ... ADD COLUMN column must have Chinese COMMENT ON COLUMN in the same migration file.id, created_at, updated_at, and deleted_at are not exempt.JSON / JSONB, enum, status, boolean, and foreign key fields must explain business semantics.TODO, TBD, placeholder, 待补充, or 临时说明.server/internal/ent/migrate/migrations/** replay chain has been removed and is no longer a fallback
authority.scripts/validate_sql_migrations.py discovery when registry/core-dir
discovery would not include it.After modifying migration SQL, run:
python3 scripts/validate_sql_migrations.py
If the migration directory contents changed, also recompute the touched directory checksum immediately:
cd server/modules/<module>/migrations && atlas migrate hash --dir file://.
If that migration directory is embedded through server/internal/moduleregistry/generated.go, regenerate it in the
same slice:
cd server && go generate ./internal/moduleregistry
Treat validate migration dir ...: checksum mismatch as a task failure, not as a deferred follow-up.
Also run the appropriate direct validation for the changed slice, such as:
python3 scripts/check_migration_versions.py --mode all
python3 scripts/validate_ai_governance.py
python3 -m unittest discover -s scripts -p 'test_*.py'
Do not claim completion while scripts/validate_sql_migrations.py fails. If a stronger backend validation is expected
but cannot run, report the exact command and blocker.
Final closeout for migration SQL work must include:
COMMENT ON TABLE / COMMENT ON COLUMN coverage.