ibank-sql-pack

Generate ordered .sql INSERT seed data for iBank dummy entities.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill ibank-sql-pack-jsplix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ibank-sql-pack
Source: https://github.com/Jsplix/ACODIAN-ORIGIN/tree/main/.codex/skills/ibank-sql-pack
Command: npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill ibank-sql-pack-jsplix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating consistent, valid SQL seed data for iBank's dummy database (including users, teams, staffing records, and worklogs) is time-consuming, error-prone, and difficult to align with existing approved drafts and strict business rules like team department ownership alignment and primary team assignment validation.

Core Features & Use Cases

  • Ordered SQL Output: Produces .sql-ready INSERT statements for core iBank tables in the required dependency order, with optional support for worklog dependency and status history tables.
  • Rule Enforcement: Automatically enforces critical business rules including stable ID preservation, shared BCrypt hash reuse, valid primary team assignment per user, and correct team department alignment with non-director admin users.
  • Flexible Batch Support: Handles both single-team and large multi-team batch generation workflows, making it suitable for small local test setups and large-scale test environment provisioning.
  • Use Case: A backend developer or QA engineer setting up a test iBank instance can use this skill to generate consistent, valid seed data that adheres to all team and worklog rules, without manually writing hundreds of lines of error-prone SQL.

Quick Start

Use the ibank-sql-pack skill to generate ordered .sql seed inserts for iBank dummy users, teams, and worklogs from your approved draft content.

Frequently Asked Questions about ibank-sql-pack

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

FAQPage Schema
How do I generate SQL INSERT seed data for iBank test environments?

To generate SQL INSERT seed data for iBank test environments, use this skill to produce ordered, .sql-ready statements for dummy users, teams, staffing, and worklogs. It automatically enforces business rules for team ownership and primary team assignment.

What is the correct table dependency order for iBank SQL inserts?

The correct table dependency order for iBank SQL inserts places core entities like users and teams before staffing and worklogs. This skill automatically outputs INSERT statements in the required dependency sequence, optionally including worklog dependency and status history tables.

Can I generate dummy SQL data for large multi-team batch testing?

Yes, you can generate dummy SQL data for large multi-team batch testing. This skill supports both single-team and large multi-team batch generation workflows, making it suitable for small local test setups and large-scale test environment provisioning.

How do I preserve existing approved draft data when generating new SQL inserts?

To preserve existing approved draft data when generating new SQL inserts, this skill maintains stable record IDs and integrates your approved draft content. It ensures new generated dummy data aligns with existing records without overwriting valid database entities.

Does iBank seed data generation enforce primary team assignment and department alignment?

Yes, iBank seed data generation enforces primary team assignment and department alignment. This skill automatically validates business rules, ensuring correct team department alignment with non-director admin users and valid primary team assignment per user.

What are the limitations of manual SQL seed data generation for iBank dummy databases?

Manual SQL seed data generation for iBank dummy databases is time-consuming and error-prone, often failing to align with strict business rules like team department ownership and primary team assignment. Automated generation ensures consistent, valid ordering and rule compliance.