Stats
Actions
Tags
From agentforge
Complete a Drizzle schema / table change end-to-end (the schema-change chain)
How this command is triggered — by the user, by Claude, or both
Slash command
/agentforge:schema-complete (no arguments — operates on your current schema changes)commands/This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Run the **schema-change** chain (`agent-os/skills/chains.json`) for the schema/table you added or changed, in order: 1. **schema-generator** — co-located Drizzle schema (snake_case columns, `pgSchema` from `pg-schemas.ts`, standard `id`/`public_id`/timestamps/soft-delete). 2. **sql-design-guard** — indexes, partitioning, constraint names, column types, and SQL formatting. 3. **db-migration-maintainer** — a matching SQL migration in `migrations/`; run `pnpm db:migrate:lint`. 4. **rls-tenant-isolation-guard** — tenant-owned tables `ENABLE` + `FORCE` RLS with an org-scoped policy carrying bot...
Run the schema-change chain (agent-os/skills/chains.json) for the schema/table you added or changed, in order:
pgSchema from pg-schemas.ts, standard id/public_id/timestamps/soft-delete).migrations/; run pnpm db:migrate:lint.ENABLE + FORCE RLS with an org-scoped policy carrying both USING and WITH CHECK; the app.current_organization_id GUC set on every query path.Finish green: pnpm validate + pnpm db:migrate:lint. Report the tables and migrations touched.
npx claudepluginhub nikunjmavani/core-be