メニュー
Use when incrementing the Trovara app version before a release — updates the semver and build number in pubspec.yaml following the project's versioning convention.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when inserting a new i18n key into Trovara's locale files — adds the key to both en.json and km.json under the correct nested path and verifies parity.
Use when reviewing a Trovara code change — checks correctness, MVVM layering, security, performance, i18n parity, file-size limits, and test coverage like a senior engineer.
Use when a developer needs orientation to the Trovara codebase — new team member, returning after a gap, or asking "how does X work", "where is Y", or "how do I add a new feature".
Use when a new service, repository, or subsystem needs documentation — CLAUDE.md for new directories, dartdoc for public APIs, or updating existing architecture docs after a structural change.
Use when adding a new screen, modifying existing feature behavior, or wiring new business logic end-to-end in Trovara — creates MVVM scaffold, route, ServiceLocator wiring, and i18n keys.
Use when adding a new persistable data entity to Trovara — scaffolds the ObjectBox model class, repository interface, ObjectBox implementation, and ServiceLocator wiring, then runs codegen.
| name | bump-version |
| description | Use when incrementing the Trovara app version before a release — updates the semver and build number in pubspec.yaml following the project's versioning convention. |
| allowed-tools | Read, Edit, Bash |
| disable-model-invocation | false |
Updates version in pubspec.yaml following the format MAJOR.MINOR.PATCH+BUILD.
1.0.0+6
│ │ │ └── build number (increment on every release; iOS + Android share this counter)
│ │ └───── patch (bug fixes)
│ └─────── minor (new features)
└───────── major (breaking changes — rare)
| Change type | Bump |
|---|---|
| Bug fix / crash fix | patch (1.0.1+7) |
| New feature (notes import, graph, quiz, etc.) | minor (1.1.0+7) |
| Breaking data migration or API change | major (2.0.0+7) |
| Release candidate / re-submit with no feature change | build only (1.0.0+7) |
Always increment the build number regardless of which semver part changes.
grep '^version:' pubspec.yaml
pubspec.yaml# Before
version: 1.0.0+6
# After (example: minor bump)
version: 1.1.0+7
Only the version: line changes — nothing else in pubspec.yaml.
flutter pub get # will fail loudly if pubspec.yaml is malformed
The version is read at runtime via package_info_plus:
final info = await PackageInfo.fromPlatform();
print('${info.version}+${info.buildNumber}'); // e.g. "1.1.0+7"
No code changes are needed — package_info_plus reads from the platform manifest, which is populated by Flutter from pubspec.yaml during build.
2.0.0). After a minor bump, reset patch to 0 (1.1.0).