ibank-worklog-generator

Generate versioned iBank tb_worklog seed SQL from team MDs and persona files.

Updated Jun 5, 2026

Search Tags:#automation #versioning #generate #worklog #ai-summary #ibank #seed-sql

Ready to run

npx skills add https://github.com/KangJiSseok/ACODIAN --skill ibank-worklog-generator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ibank-worklog-generator
Source: https://github.com/KangJiSseok/ACODIAN/tree/main/.codex/skills/ibank-worklog-generator
Command: npx skills add https://github.com/KangJiSseok/ACODIAN --skill ibank-worklog-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The iBank Worklog Generator automates creating versioned tb_worklog seed SQL from team MDs and persona files, saving time and ensuring consistency across releases.

Core Features & Use Cases

Generate seed SQL for new worklog versions with a chosen base variant and version tag.
Produce matching predecessor/dependency SQL and optional ai_summary updates for cohesive versioning.
Apply to scenarios like fresh seeds, new version tags (e.g., v7), or refreshing content while preserving existing data.

Quick Start

Run the iBank Worklog Generator with a base variant and a version tag to produce a seed SQL file and its dependency outputs.

Frequently Asked Questions about ibank-worklog-generator

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

FAQPage Schema

How do I generate versioned seed SQL for database worklogs?▼

To generate versioned seed SQL, provide a base variant and a version tag. The generator processes team MDs and persona files to output reproducible worklog seeds and dependency SQL for that specific version.

Can I refresh ai_summary data without losing existing worklog records?▼

You can refresh ai_summary data by applying a new version tag to an existing base variant. This preserves current data while generating updated predecessor links and dependency outputs for the new version.

How do worklog version tags and dependency SQL work together?▼

Worklog version tags group seed SQL with matching dependency SQL and predecessor links. This ensures cohesive versioning so all related outputs are tied to the same chosen version tag for reproducible historical data.

What is the best way to automate reproducible historical data seeding from markdown files?▼

Automating reproducible historical data seeding involves processing team MDs and persona files to generate seed SQL. This ensures consistency across releases by automatically producing versioned outputs ready for review.

Do I need specific persona files to produce worklog seed SQL?▼

Yes, team MDs and persona files are required inputs. The generator applies a chosen base variant and version tag to these source files to produce the final seed SQL and its dependency outputs.

Why does my generated worklog SQL include predecessor links?▼

Generated worklog SQL includes predecessor links to support cohesive versioning. These links connect the current version tag to previous data, ensuring end-to-end workflow requirements are satisfied for reproducible outputs.