rpg-file-writer

Generate structured SQL migration files with enforced naming and section ordering.

Updated Feb 15, 2025
One-click install
npx skills add https://github.com/Ciabatos/sybath --skill rpg-file-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rpg-file-writer
Source: https://github.com/Ciabatos/sybath/tree/main/.opencode/skills/sql-file-writer
Command: npx skills add https://github.com/Ciabatos/sybath --skill rpg-file-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all SQL migration files are named, structured, and written according to a strict, standardized format, preventing errors and maintaining consistency in the database schema evolution process.

Core Features & Use Cases

  • Standardized Naming: Enforces a <NNN>_<feature_slug>.sql format for clear identification.
  • Structured Content: Dictates the exact order of sections (Reference, State, Read, Action functions) and formatting within SQL files.
  • Header Compliance: Ensures all migration files include a mandatory, detailed header block.
  • Use Case: When creating new database tables for a 'Player Inventory' feature, this Skill will generate a file named 002_player_inventory.sql (assuming 001 was for guilds) with the correct header and SQL structure.

Quick Start

Use the rpg-file-writer skill to create a new SQL migration file for the 'Quest System' feature.

Frequently Asked Questions about rpg-file-writer

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

FAQPage Schema
How do I structure SQL migration files for consistent database schema evolution?

To structure SQL migration files for database schema evolution, enforce a strict `<NNN>_<feature_slug>.sql` naming convention and dictate the exact order of internal SQL sections like Reference, State, Read, and Action functions.

What is the correct format for writing a Postgres database schema migration file?

A correct Postgres database schema migration file format requires a mandatory detailed header block, a standardized naming convention, and a structured internal ordering of SQL objects for tables and functions to maintain consistency.

How do I split complex database migrations into multiple SQL files?

You can split complex database migrations into multiple SQL files based on schema count, function count, or feature modules, ensuring each file independently adheres to the required header and SQL object ordering conventions.

Does this SQL migration generator support custom naming conventions for database tables?

This SQL migration generator enforces a strict `<NNN>_<feature_slug>.sql` naming convention rather than supporting custom naming, ensuring clear identification and preventing errors during database schema evolution.

Why do my database migration files fail during schema evolution?

Database migration files often fail during schema evolution due to inconsistent naming, missing mandatory headers, or incorrect ordering of SQL objects, which this Skill standardizes to prevent such errors.

Can I use rpg-file-writer to generate SQL for both tables and functions?

Yes, rpg-file-writer generates and structures SQL objects for both tables and functions, enforcing internal ordering and header compliance to maintain standardized migration files across feature modules.