[ 
https://issues.apache.org/jira/browse/FINERACT-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhishek Chaudhary updated FINERACT-3010:
-----------------------------------------
    Description: 
Following the dev list discussion on AI-assisted development ([James's request 
for early 
versions|https://lists.apache.org/thread/vg50m7kjrhxh3tqto8dgrzr00n80f3lo], 
[the proposal for the testing and database 
skills|https://lists.apache.org/thread/f7rbkkxcx1nv0tjovlb908pn5thkvfjm]), add 
an early version of the database skill, after the testing skill 
(FINERACT-2970), so AI coding agents follow Fineract's existing Liquibase and 
persistence conventions.

New file {{.agents/skills/fineract-database/SKILL.md}} (Agent Skills format), 
covering:
* where a changelog part goes: the tenant, tenant store and module changelog 
trees, their numbering, and the include in each master changelog
* the PostgreSQL and MySQL contexts, one changeset per database where types 
differ, and the properties in {{db.changelog-master.xml}}
* the DDL safety check: {{DATETIME(6)}}, indexes that do not lock tables on 
PostgreSQL, and the operations that block on the critical tables
* backward compatibility during rolling upgrades, and the CI jobs that check 
the migrations
* seed rows the code expects: permissions, global configurations, scheduler 
jobs and external event types

Every step points to the existing doc, script or CI check it comes from: 
{{persistence.adoc}}, the changelogs themselves, 
{{scripts/check-liquibase-ddl-safety.sh}}, 
{{scripts/check-liquibase-changelog-registration.sh}} and the workflows. It 
adds no new rules.

{{.claude/skills/fineract-database}} is a symlink to 
{{.agents/skills/fineract-database}}, as for the testing skill.

{{AGENTS.md}} gets a Skills section that lists both skills and when to use 
them, so an agent that does not load skills from {{.agents/skills}} still finds 
them.

  was:
Following the dev list discussion on AI-assisted development ([James's request 
for early 
versions|https://lists.apache.org/thread/vg50m7kjrhxh3tqto8dgrzr00n80f3lo], 
[the proposal for the testing and database 
skills|https://lists.apache.org/thread/f7rbkkxcx1nv0tjovlb908pn5thkvfjm]), add 
an early version of the database skill, after the testing skill 
(FINERACT-2970), so AI coding agents follow Fineract's existing Liquibase and 
persistence conventions.

New file {{.agents/skills/fineract-database/SKILL.md}} (Agent Skills format), 
covering:
* where a changelog part goes: the tenant, tenant store and module changelog 
trees, their numbering, and the include in each master changelog
* the PostgreSQL and MySQL contexts, one changeset per database where types 
differ, and the properties in {{db.changelog-master.xml}}
* the DDL safety check: {{DATETIME(6)}}, indexes that do not lock tables on 
PostgreSQL, and the operations that block on the critical tables
* backward compatibility during rolling upgrades, and the CI jobs that check 
the migrations
* seed rows the code expects: permissions, global configurations, scheduler 
jobs and external event types

Every step points to the existing doc, script or CI check it comes from: 
{{persistence.adoc}}, the changelogs themselves, 
{{scripts/check-liquibase-ddl-safety.sh}}, 
{{scripts/check-liquibase-changelog-registration.sh}} and the workflows. It 
adds no new rules.

{{.claude/skills/fineract-database}} is a symlink to 
{{.agents/skills/fineract-database}}, as for the testing skill.


> Add an agent skill for database changes
> ---------------------------------------
>
>                 Key: FINERACT-3010
>                 URL: https://issues.apache.org/jira/browse/FINERACT-3010
>             Project: Apache Fineract
>          Issue Type: Improvement
>          Components: Docs
>            Reporter: Abhishek Chaudhary
>            Assignee: Abhishek Chaudhary
>            Priority: Major
>             Fix For: 1.17.0
>
>
> Following the dev list discussion on AI-assisted development ([James's 
> request for early 
> versions|https://lists.apache.org/thread/vg50m7kjrhxh3tqto8dgrzr00n80f3lo], 
> [the proposal for the testing and database 
> skills|https://lists.apache.org/thread/f7rbkkxcx1nv0tjovlb908pn5thkvfjm]), 
> add an early version of the database skill, after the testing skill 
> (FINERACT-2970), so AI coding agents follow Fineract's existing Liquibase and 
> persistence conventions.
> New file {{.agents/skills/fineract-database/SKILL.md}} (Agent Skills format), 
> covering:
> * where a changelog part goes: the tenant, tenant store and module changelog 
> trees, their numbering, and the include in each master changelog
> * the PostgreSQL and MySQL contexts, one changeset per database where types 
> differ, and the properties in {{db.changelog-master.xml}}
> * the DDL safety check: {{DATETIME(6)}}, indexes that do not lock tables on 
> PostgreSQL, and the operations that block on the critical tables
> * backward compatibility during rolling upgrades, and the CI jobs that check 
> the migrations
> * seed rows the code expects: permissions, global configurations, scheduler 
> jobs and external event types
> Every step points to the existing doc, script or CI check it comes from: 
> {{persistence.adoc}}, the changelogs themselves, 
> {{scripts/check-liquibase-ddl-safety.sh}}, 
> {{scripts/check-liquibase-changelog-registration.sh}} and the workflows. It 
> adds no new rules.
> {{.claude/skills/fineract-database}} is a symlink to 
> {{.agents/skills/fineract-database}}, as for the testing skill.
> {{AGENTS.md}} gets a Skills section that lists both skills and when to use 
> them, so an agent that does not load skills from {{.agents/skills}} still 
> finds them.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to