export-scripts

Consolidate pending SQL migrations into a single documented bundle with rollback.

Updated May 2, 2026
One-click install
npx skills add https://github.com/Tacuchi/agent-workflow-cli --skill export-scripts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: export-scripts
Source: https://github.com/Tacuchi/agent-workflow-cli/tree/main/skills/w/exports/export-scripts
Command: npx skills add https://github.com/Tacuchi/agent-workflow-cli --skill export-scripts

SYSTEM DOCUMENTATION & REQUIREMENTS

Consolida las migraciones SQL pendientes del workspace en un único bundle docs/scripts/NNN-export-scripts-YYYY-MM-DD/ con numeración continua tras 00-ROLLBACK.sql. Lee migraciones tipo-B (DDL/DML) desde dos fuentes: .workflow/sessions/<folder>/SCRIPTS.sql de N sesiones y docs/scripts/*.sql standalone (excluyendo bundles previos). Ignora el tipo-A read-only (consultas de diagnóstico, no entregables). Headers SQL mínimos + README simple (3 secciones: Archivos / Aplicar / Revertir). El rollback se deriva de los forwards. Read-only/reporte: NUNCA ejecuta SQL ni commitea — el bundle es para que un humano/DBA lo aplique. Compone la capacidad sql. Úsalo para 'bundle SQL del release', 'preparar paso a prod', 'consolidar SQLs pendientes'. Invocado por el usuario vía /w:export-scripts.

Frequently Asked Questions about export-scripts

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

FAQPage Schema
How do I consolidate pending SQL migrations into a single release bundle?▼

To consolidate pending SQL migrations, this Skill bundles workspace DDL and DML scripts from session artifacts and standalone files into a numbered distribution folder with forward and rollback scripts for review.

What is the best way to generate a rollback script for a grouped SQL release?▼

Generating a rollback script for a grouped SQL release is handled automatically by deriving the rollback SQL from the consolidated forward migrations, placing it as 00-ROLLBACK.sql within the bundle.

Does the export-scripts workflow execute SQL directly against the database?▼

No, the workflow does not execute SQL directly against the database. It operates in read-only mode, strictly producing a documentation bundle for a human or DBA to apply later.

Can I include diagnostic read-only queries in my SQL migration bundle?▼

You cannot include diagnostic read-only queries in your SQL migration bundle. The process specifically ignores type-A read-only queries, focusing only on type-B DDL and DML deliverable changes.

How are SQL scripts classified and documented when preparing a production release?▼

When preparing a production release, SQL scripts are classified into canonical categories, enumerated by source, and documented with a simple README containing file descriptions, apply steps, and revert instructions.

What sources are supported for grouping SQL changes by category for review?▼

Supported sources for grouping SQL changes include pending type-B migrations from session SCRIPTS.sql artifacts and standalone .sql scripts, while explicitly excluding previously generated export bundles.