[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HEMQ9112PWPKS75JD5R6DW":3,"skill-same:01M6HEMQ9112PWPKS75JD5R6DW":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6HEMQ9112PWPKS75JD5R6DW","fineract-database",null,"Add or change Apache Fineract database schema and seed data with Liquibase, covering where a changelog part goes and how it is included, the PostgreSQL and MySQL contexts, the DDL safety, registration and backward-compatibility checks, seed rows such as permissions and configurations, and how Java code reaches the database. Use when adding or editing a Liquibase changelog, a table, column, index or seed row, a JPA relationship or a native SQL query, or when a database check fails in CI.","apache\u002Ffineract","apache","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47359?v=4","01M6AC83E6K4FDKK7HZ8WNMQKE","The Apache Software Foundation","01M6ACGYTY2VJZ9BH4K7MVTDM4",2625,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fapache\u002Ffineract\u002Fblob\u002Fdevelop\u002F.agents\u002Fskills\u002Ffineract-database\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,9,37,38,39,40,41,42],"fineract database","database","data","native","database schema","seed","relationship","query","compatibility","how","Safety","change","ci","postgresql","mysql","changelog","permissions","code","sql","2026-11-10 10:12:30",false,"---\nname: fineract-database\ndescription: Add or change Apache Fineract database schema and seed data with Liquibase, covering where a changelog part goes and how it is included, the PostgreSQL and MySQL contexts, the DDL safety, registration and backward-compatibility checks, seed rows such as permissions and configurations, and how Java code reaches the database. Use when adding or editing a Liquibase changelog, a table, column, index or seed row, a JPA relationship or a native SQL query, or when a database check fails in CI.\n---\n\n# Fineract Database Changes\n\nPaths are relative to the repository root, `db.changelog-master.xml` is\n`fineract-provider\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Fdb.changelog-master.xml`, and\n`persistence.adoc` is `fineract-doc\u002Fsrc\u002Fdocs\u002Fen\u002Fchapters\u002Farchitecture\u002Fpersistence.adoc`. Each\nrule below comes from the file or check named next to it; if this skill and that source\ndisagree, the source wins.\n\n## Where a change goes\n\nLiquibase runs only the changelogs that `db.changelog-master.xml` reaches. Each tree has\nits own `parts` directory, its own numbering and its own master changelog:\n\n| Tables of | Parts directory | Included by |\n| --- | --- | --- |\n| The tenant database (core) | `fineract-provider\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant\u002Fparts` | `tenant\u002Fchangelog-tenant.xml` |\n| The tenant store (`fineract_tenants`) | `fineract-provider\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant-store\u002Fparts` | `tenant-store\u002Fchangelog-tenant-store.xml` |\n| A module with its own tree (loan, savings, progressive loan, working capital loan, loan origination, investor, command) | `\u003Cmodule>\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant\u002Fmodule\u002F\u003Cname>\u002F...\u002Fparts` | The `module-changelog-master.xml` that includes the other parts of that directory |\n\n1. Put the change in the tree of the module that owns the table. A core part that alters a\n   module's tables goes in `tenant\u002Ffinal-changelog-tenant.xml`, which runs after the modules\n   (comment in `db.changelog-master.xml`).\n2. Name the file with the next free number of that directory and what it does, like\n   `0248_add_dates_to_client_identifier.xml` in the core tree, and add its `\u003Cinclude>` at the\n   end of the master changelog. Another open PR may take the same number first; renumber when\n   you rebase.\n3. Run `.\u002Fscripts\u002Fcheck-liquibase-changelog-registration.sh --base-ref origin\u002Fdevelop`. It\n   fails on a part that no master includes, a master that `db.changelog-master.xml` does not\n   reach, a file included twice or an include of a missing file, and warns when a new part\n   reuses a number. CI runs it in `.github\u002Fworkflows\u002Fverify-liquibase-changelog-registration.yml`.\n   Run it again after resolving a conflict in a master changelog: a lost `\u003Cinclude>` breaks\n   nothing visibly, the part just never runs.\n4. Never edit, rename or move a changeset that is already on develop; add a new one.\n   Liquibase identifies a changeset by its id, author and file path, so a moved file runs\n   again, and it refuses to start when the checksum of a changeset it has run changes. The\n   few old changesets that were edited carry `\u003CvalidCheckSum>` entries, for example\n   `fineract-provider\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant\u002Fparts\u002F0015_add_business_date.xml`.\n\n## Databases and contexts\n\n1. PostgreSQL is the supported database; MySQL and MariaDB are deprecated but still\n   supported (`persistence.adoc`, \"Database support\"). CI runs the integration tests on all\n   three (`.github\u002Fworkflows\u002Fbuild-postgresql.yml` and its MySQL and MariaDB variants).\n2. The contexts are `mysql`, `postgresql`, `tenant_db`, `tenant_store_db` and the active\n   Spring profiles. Never use `initial_switch` (`persistence.adoc`, \"Database schema\n   migration\"). The includes in `db.changelog-master.xml` already set `tenant_db` or\n   `tenant_store_db`, so a part only needs `context=\"mysql\"` or `context=\"postgresql\"` on\n   the changesets whose types or SQL differ.\n3. Where the types differ, write one changeset per database. For example,\n   `fineract-loan-origination\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant\u002Fmodule\u002Floanorigination\u002Fparts\u002F0005_wc_loan_originator_mapping.xml`\n   declares `created_on_utc` as `DATETIME(6)` on MySQL and `TIMESTAMP WITH TIME ZONE` on\n   PostgreSQL, with `created_by` and `last_modified_by` as foreign keys to `m_appuser`.\n4. For the current date, the current time or a UUID in a changeset, use the\n   `${current_date}`, `${current_datetime}` and `${uuid}` properties defined at the top of\n   `db.changelog-master.xml`.\n5. In Java, put a database-specific function in a native query through\n   `DatabaseSpecificSQLGenerator`, and extend it when a function is missing\n   (`persistence.adoc`, \"Data-access layer\").\n6. Map every new JPA relationship with `FetchType.LAZY`; a PR that adds an `EAGER` one is\n   rejected (`persistence.adoc`, \"Data-access layer\").\n\n## DDL safety\n\n`.github\u002Fworkflows\u002Fverify-liquibase-ddl-safety.yml` runs `scripts\u002Fcheck-liquibase-ddl-safety.sh`\non the changelog files a PR changes. Run it locally with\n`.\u002Fscripts\u002Fcheck-liquibase-ddl-safety.sh --base-ref origin\u002Fdevelop --head-ref HEAD`.\n\n1. On MySQL, declare date-time columns as `DATETIME(6)`. A plain `DATETIME` blocks the\n   build, because MySQL would drop the fractional seconds. On PostgreSQL, the `_utc` and\n   audit columns are `TIMESTAMP WITH TIME ZONE`, so write one changeset per database for them\n   (point 3 of \"Databases and contexts\").\n2. An index on a table that the PR does not create must not lock it on PostgreSQL. Use raw\n   `CREATE INDEX CONCURRENTLY` in a changeset with `runInTransaction=\"false\"` and\n   `context=\"postgresql\"`, and a separate MySQL changeset, as\n   `fineract-provider\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant\u002Fparts\u002F0177_acc_journal_entry_index.xml`\n   does. A `\u003CcreateIndex>` on such a table blocks the build unless its changeset runs only\n   on MySQL.\n3. `dropColumn`, `dropTable`, `renameColumn`, `renameTable`, `modifyDataType`,\n   `addNotNullConstraint`, and an `addColumn` with `nullable=\"false\"` and no default block\n   the build on the tables listed in `config\u002Fliquibase\u002Fcritical-tables.txt`, and are\n   warnings on other tables. `config\u002Fliquibase\u002Fdangerous-operations.txt` gives the reason for\n   each. The check treats tables that the same PR creates as safe.\n4. The `ddl-safety-override` label makes the check report without blocking. Only a\n   maintainer can add it, so explain in the PR why the operation is safe.\n\n## Backward compatibility\n\nDuring a rolling upgrade the old code runs against the new schema, so add columns as\nnullable or with a default, and drop or rename a column only after a release in which no\ncode uses it (`config\u002Fliquibase\u002Fdangerous-operations.txt`). These workflows, called from\n`.github\u002Fworkflows\u002Ffull-build-ci.yml`, check the migrations:\n\n1. `verify-liquibase-backward-compatibility.yml` starts the base commit's backend on a fresh\n   PostgreSQL database, then starts the PR's backend on the same database, so every new\n   changeset must run as an upgrade.\n2. `regression-safety-db-changes.yml` runs on PRs that change a changelog. It runs the\n   `@RegressionSafety` E2E scenarios three times: old code with the old schema, old code with\n   the new schema, and new code with the new schema. A failure only in the second run means\n   the old code cannot work with the new schema.\n3. `liquibase-only-postgresql.yml` runs the migrations alone, with the `liquibase-only`\n   Spring profile, on a fresh PostgreSQL database.\n\n## Seed rows\n\nSome changes need a row that the code expects to exist. Insert it in the same change:\n\n| When you add | Insert a row into | Example |\n| --- | --- | --- |\n| A command or another action that checks a permission | `m_permission`, and for a write command also its `\u003CCODE>_CHECKER` row | `fineract-working-capital-loan\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant\u002Fmodule\u002Fworkingcapitalloan\u002Fparts\u002F0084_wc_loan_missing_command_permissions.xml` |\n| A global configuration | `c_configuration` | `fineract-provider\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant\u002Fparts\u002F0267_add_retained_earning_wc_report_global_configuration.xml` |\n| A scheduler job (`JobName` value) | `job` | `fineract-savings\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant\u002Fmodule\u002Fsavings\u002Fparts\u002Fparts\u002F2001_add_savings_accrual_job.xml` |\n| An external business event type | `m_external_event_configuration`, with `enabled` false | `fineract-provider\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant\u002Fparts\u002F0243_add_client_lifecycle_event_configuration.xml` |\n\n1. Tests that run as the superuser do not notice a missing `m_permission` row. It fails only\n   when maker-checker is enabled, where\n   `ConfigurationDomainServiceJpa.isMakerCheckerEnabledForTask` throws\n   `PermissionNotFoundException`, or for a role that needs to be granted the permission.\n   Without the `\u003CCODE>_CHECKER` row (`action_name` `\u003CACTION>_CHECKER`), only\n   `CHECKER_SUPER_USER` can approve the command, because\n   `PortfolioCommandSourceWritePlatformServiceImpl` checks `taskPermission + \"_CHECKER\"`. The\n   0084 example adds such rows that were missing.\n2. Guard an insert with `\u003CpreConditions onFail=\"MARK_RAN\">` and a `sqlCheck` for the row, as\n   the `m_permission` and `c_configuration` examples above do, so that a database that\n   already has the row skips the changeset.\n3. Integration tests compare some of these tables with lists kept by hand:\n   `GlobalConfigurationHelper`, `SchedulerJobsTest` and `ExternalEventConfigurationTestData`\n   in `integration-tests`. Update them in the same change.\n\n## Verify\n\n1. Run the registration and DDL safety scripts above.\n2. Start the backend on a fresh database (`CONTRIBUTING.md`, \"Cucumber E2E tests\", shows\n   `createPGDB` and `bootRun`) and read the log for the changesets that ran. Then start it on\n   a database that develop created, to check the upgrade.\n3. If you wrote a changeset for one database only, check the other one too, or watch the\n   MySQL and MariaDB jobs in CI: the PostgreSQL run cannot catch it.\n","# Fineract Database Changes\n\nPaths are relative to the repository root, `db.changelog-master.xml` is\n`fineract-provider\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Fdb.changelog-master.xml`, and\n`persistence.adoc` is `fineract-doc\u002Fsrc\u002Fdocs\u002Fen\u002Fchapters\u002Farchitecture\u002Fpersistence.adoc`. Each\nrule below comes from the file or check named next to it; if this skill and that source\ndisagree, the source wins.\n\n## Where a change goes\n\nLiquibase runs only the changelogs that `db.changelog-master.xml` reaches. Each tree has\nits own `parts` directory, its own numbering and its own master changelog:\n\n| Tables of | Parts directory | Included by |\n| --- | --- | --- |\n| The tenant database (core) | `fineract-provider\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant\u002Fparts` | `tenant\u002Fchangelog-tenant.xml` |\n| The tenant store (`fineract_tenants`) | `fineract-provider\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant-store\u002Fparts` | `tenant-store\u002Fchangelog-tenant-store.xml` |\n| A module with its own tree (loan, savings, progressive loan, working capital loan, loan origination, investor, command) | `\u003Cmodule>\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant\u002Fmodule\u002F\u003Cname>\u002F...\u002Fparts` | The `module-changelog-master.xml` that includes the other parts of that directory |\n\n1. Put the change in the tree of the module that owns the table. A core part that alters a\n   module's tables goes in `tenant\u002Ffinal-changelog-tenant.xml`, which runs after the modules\n   (comment in `db.changelog-master.xml`).\n2. Name the file with the next free number of that directory and what it does, like\n   `0248_add_dates_to_client_identifier.xml` in the core tree, and add its `\u003Cinclude>` at the\n   end of the master changelog. Another open PR may take the same number first; renumber when\n   you rebase.\n3. Run `.\u002Fscripts\u002Fcheck-liquibase-changelog-registration.sh --base-ref origin\u002Fdevelop`. It\n   fails on a part that no master includes, a master that `db.changelog-master.xml` does not\n   reach, a file included twice or an include of a missing file, and warns when a new part\n   reuses a number. CI runs it in `.github\u002Fworkflows\u002Fverify-liquibase-changelog-registration.yml`.\n   Run it again after resolving a conflict in a master changelog: a lost `\u003Cinclude>` breaks\n   nothing visibly, the part just never runs.\n4. Never edit, rename or move a changeset that is already on develop; add a new one.\n   Liquibase identifies a changeset by its id, author and file path, so a moved file runs\n   again, and it refuses to start when the checksum of a changeset it has run changes. The\n   few old changesets that were edited carry `\u003CvalidCheckSum>` entries, for example\n   `fineract-provider\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant\u002Fparts\u002F0015_add_business_date.xml`.\n\n## Databases and contexts\n\n1. PostgreSQL is the supported database; MySQL and MariaDB are deprecated but still\n   supported (`persistence.adoc`, \"Database support\"). CI runs the integration tests on all\n   three (`.github\u002Fworkflows\u002Fbuild-postgresql.yml` and its MySQL and MariaDB variants).\n2. The contexts are `mysql`, `postgresql`, `tenant_db`, `tenant_store_db` and the active\n   Spring profiles. Never use `initial_switch` (`persistence.adoc`, \"Database schema\n   migration\"). The includes in `db.changelog-master.xml` already set `tenant_db` or\n   `tenant_store_db`, so a part only needs `context=\"mysql\"` or `context=\"postgresql\"` on\n   the changesets whose types or SQL differ.\n3. Where the types differ, write one changeset per database. For example,\n   `fineract-loan-origination\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant\u002Fmodule\u002Floanorigination\u002Fparts\u002F0005_wc_loan_originator_mapping.xml`\n   declares `created_on_utc` as `DATETIME(6)` on MySQL and `TIMESTAMP WITH TIME ZONE` on\n   PostgreSQL, with `created_by` and `last_modified_by` as foreign keys to `m_appuser`.\n4. For the current date, the current time or a UUID in a changeset, use the\n   `${current_date}`, `${current_datetime}` and `${uuid}` properties defined at the top of\n   `db.changelog-master.xml`.\n5. In Java, put a database-specific function in a native query through\n   `DatabaseSpecificSQLGenerator`, and extend it when a function is missing\n   (`persistence.adoc`, \"Data-access layer\").\n6. Map every new JPA relationship with `FetchType.LAZY`; a PR that adds an `EAGER` one is\n   rejected (`persistence.adoc`, \"Data-access layer\").\n\n## DDL safety\n\n`.github\u002Fworkflows\u002Fverify-liquibase-ddl-safety.yml` runs `scripts\u002Fcheck-liquibase-ddl-safety.sh`\non the changelog files a PR changes. Run it locally with\n`.\u002Fscripts\u002Fcheck-liquibase-ddl-safety.sh --base-ref origin\u002Fdevelop --head-ref HEAD`.\n\n1. On MySQL, declare date-time columns as `DATETIME(6)`. A plain `DATETIME` blocks the\n   build, because MySQL would drop the fractional seconds. On PostgreSQL, the `_utc` and\n   audit columns are `TIMESTAMP WITH TIME ZONE`, so write one changeset per database for them\n   (point 3 of \"Databases and contexts\").\n2. An index on a table that the PR does not create must not lock it on PostgreSQL. Use raw\n   `CREATE INDEX CONCURRENTLY` in a changeset with `runInTransaction=\"false\"` and\n   `context=\"postgresql\"`, and a separate MySQL changeset, as\n   `fineract-provider\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant\u002Fparts\u002F0177_acc_journal_entry_index.xml`\n   does. A `\u003CcreateIndex>` on such a table blocks the build unless its changeset runs only\n   on MySQL.\n3. `dropColumn`, `dropTable`, `renameColumn`, `renameTable`, `modifyDataType`,\n   `addNotNullConstraint`, and an `addColumn` with `nullable=\"false\"` and no default block\n   the build on the tables listed in `config\u002Fliquibase\u002Fcritical-tables.txt`, and are\n   warnings on other tables. `config\u002Fliquibase\u002Fdangerous-operations.txt` gives the reason for\n   each. The check treats tables that the same PR creates as safe.\n4. The `ddl-safety-override` label makes the check report without blocking. Only a\n   maintainer can add it, so explain in the PR why the operation is safe.\n\n## Backward compatibility\n\nDuring a rolling upgrade the old code runs against the new schema, so add columns as\nnullable or with a default, and drop or rename a column only after a release in which no\ncode uses it (`config\u002Fliquibase\u002Fdangerous-operations.txt`). These workflows, called from\n`.github\u002Fworkflows\u002Ffull-build-ci.yml`, check the migrations:\n\n1. `verify-liquibase-backward-compatibility.yml` starts the base commit's backend on a fresh\n   PostgreSQL database, then starts the PR's backend on the same database, so every new\n   changeset must run as an upgrade.\n2. `regression-safety-db-changes.yml` runs on PRs that change a changelog. It runs the\n   `@RegressionSafety` E2E scenarios three times: old code with the old schema, old code with\n   the new schema, and new code with the new schema. A failure only in the second run means\n   the old code cannot work with the new schema.\n3. `liquibase-only-postgresql.yml` runs the migrations alone, with the `liquibase-only`\n   Spring profile, on a fresh PostgreSQL database.\n\n## Seed rows\n\nSome changes need a row that the code expects to exist. Insert it in the same change:\n\n| When you add | Insert a row into | Example |\n| --- | --- | --- |\n| A command or another action that checks a permission | `m_permission`, and for a write command also its `\u003CCODE>_CHECKER` row | `fineract-working-capital-loan\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant\u002Fmodule\u002Fworkingcapitalloan\u002Fparts\u002F0084_wc_loan_missing_command_permissions.xml` |\n| A global configuration | `c_configuration` | `fineract-provider\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant\u002Fparts\u002F0267_add_retained_earning_wc_report_global_configuration.xml` |\n| A scheduler job (`JobName` value) | `job` | `fineract-savings\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant\u002Fmodule\u002Fsavings\u002Fparts\u002Fparts\u002F2001_add_savings_accrual_job.xml` |\n| An external business event type | `m_external_event_configuration`, with `enabled` false | `fineract-provider\u002Fsrc\u002Fmain\u002Fresources\u002Fdb\u002Fchangelog\u002Ftenant\u002Fparts\u002F0243_add_client_lifecycle_event_configuration.xml` |\n\n1. Tests that run as the superuser do not notice a missing `m_permission` row. It fails only\n   when maker-checker is enabled, where\n   `ConfigurationDomainServiceJpa.isMakerCheckerEnabledForTask` throws\n   `PermissionNotFoundException`, or for a role that needs to be granted the permission.\n   Without the `\u003CCODE>_CHECKER` row (`action_name` `\u003CACTION>_CHECKER`), only\n   `CHECKER_SUPER_USER` can approve the command, because\n   `PortfolioCommandSourceWritePlatformServiceImpl` checks `taskPermission + \"_CHECKER\"`. The\n   0084 example adds such rows that were missing.\n2. Guard an insert with `\u003CpreConditions onFail=\"MARK_RAN\">` and a `sqlCheck` for the row, as\n   the `m_permission` and `c_configuration` examples above do, so that a database that\n   already has the row skips the changeset.\n3. Integration tests compare some of these tables with lists kept by hand:\n   `GlobalConfigurationHelper`, `SchedulerJobsTest` and `ExternalEventConfigurationTestData`\n   in `integration-tests`. Update them in the same change.\n\n## Verify\n\n1. Run the registration and DDL safety scripts above.\n2. Start the backend on a fresh database (`CONTRIBUTING.md`, \"Cucumber E2E tests\", shows\n   `createPGDB` and `bootRun`) and read the log for the changesets that ran. Then start it on\n   a database that develop created, to check the upgrade.\n3. If you wrote a changeset for one database only, check the other one too, or watch the\n   MySQL and MariaDB jobs in CI: the PostgreSQL run cannot catch it.\n",{"name":5,"description":7},"develop","e048ee8b2b6a9f4a3b2dec2b79b4dd40ef480d99",".agents\u002Fskills\u002Ffineract-database",2966,"https:\u002F\u002Fgithub.com\u002Fapache\u002Ffineract","https:\u002F\u002Ffineract.apache.org","https:\u002F\u002Fgithub.com\u002Fapache","https:\u002F\u002Fwww.apache.org\u002F","2026-11-15 00:44:51",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add apache\u002Ffineract --skill fineract-database",{"tool":63,"command":64},"bunx","bunx skills add apache\u002Ffineract --skill fineract-database",{"tool":66,"command":67},"pnpm","pnpm dlx skills add apache\u002Ffineract --skill fineract-database","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fapache\u002Ffineract\u002Fblob\u002Fdevelop\u002F.agents\u002Fskills\u002Ffineract-database\u002FSKILL.md",true,[],[72],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":81,"publishedAt":43},"01M6ACH2BE3Z6R6S4FGPN5SN7W","fineract-testing","Choose, write, run and verify tests for Apache Fineract changes, covering JUnit unit tests, the fineract-provider Cucumber tests, Feign-client integration tests, the two-factor and OAuth2 suites, and Cucumber E2E scenarios. Use when adding or changing tests, when a code change needs test coverage, when a test fails, or before claiming that a change works.","https:\u002F\u002Fgithub.com\u002Fapache\u002Ffineract\u002Fblob\u002Fdevelop\u002F.agents\u002Fskills\u002Ffineract-testing\u002FSKILL.md",[78],{"categoryNo":79,"categoryName":80,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[82,83,84,85,86,87,88,89,90,91,92,93,94,9,41,95,96,97,35,98],"fineract testing","testing","verify","changes","for","unit","factor","tests","provider","use","coverage","choose","e2e","run","unit tests","integration tests","test"]