name	bump-version
description	Bump the knowledgebuilder app version across package.json and both environment files, refresh the release date, verify the build, and optionally create a release commit. Invoke when the user asks to bump/release/version the app.

Bump Version

The version string lives in three places that must stay in sync, plus a releasedate field in the two environment files:

File	Field(s)
`package.json`	`version`
`src/environments/environment.ts`	`version`, `releasedate`
`src/environments/environment.prod.ts`	`version`, `releasedate`

The footer (src/app/shared/footer) displays both version and releasedate.

Version scheme

Semver MAJOR.MINOR.PATCH (e.g. 1.8.419). PATCH is a running number, not strictly +1 - always confirm the target with the user.

Steps

Determine the target version. If the user gave an explicit version (e.g. 1.8.420), use it. Otherwise ask whether to bump patch / minor / major and compute it from the current package.json version.
Apply the bump by running the helper script that ships with this skill - never edit the version fields by hand, so the three files cannot drift:
```
node .claude/skills/bump-version/bump-version.mjs <X.Y.Z>
```
This updates package.json, both environment files, and sets releasedate to today's date (YYYY-MM-DD).

Verify sync - confirm all three files report the same version:

grep -nE "version|releasedate" package.json src/environments/environment.ts src/environments/environment.prod.ts

Verify the build (recommended):
```
ng build --configuration development
```
Commit only if the user explicitly asks. Follow the repo convention from git history:
```
chore: bump version to <X.Y.Z>
```
Stage package.json, src/environments/environment.ts, src/environments/environment.prod.ts. Per project rules, never commit unless requested.

Notes

If the user also wants a git tag, the repo currently has no tagging convention - ask first.
The helper script lives next to this file at .claude/skills/bump-version/bump-version.mjs so the skill is self-contained.

Bump Version

The version string lives in three places that must stay in sync, plus a releasedate field in the two environment files:

File

Field(s)

package.json

version

src/environments/environment.ts

version, releasedate

src/environments/environment.prod.ts

version, releasedate

The footer (src/app/shared/footer) displays both version and releasedate.

Version scheme

Semver MAJOR.MINOR.PATCH (e.g. 1.8.419). PATCH is a running number, not strictly +1 - always confirm the target with the user.

Steps

Determine the target version. If the user gave an explicit version (e.g. 1.8.420), use it. Otherwise ask whether to bump patch / minor / major and compute it from the current package.json version.

Apply the bump by running the helper script that ships with this skill - never edit the version fields by hand, so the three files cannot drift:

node .claude/skills/bump-version/bump-version.mjs <X.Y.Z>

This updates package.json, both environment files, and sets releasedate to today's date (YYYY-MM-DD).

Verify sync - confirm all three files report the same version:

grep -nE "version|releasedate" package.json src/environments/environment.ts src/environments/environment.prod.ts

Verify the build (recommended):

ng build --configuration development

Commit only if the user explicitly asks. Follow the repo convention from git history:

chore: bump version to <X.Y.Z>

Stage package.json, src/environments/environment.ts, src/environments/environment.prod.ts. Per project rules, never commit unless requested.

Notes

If the user also wants a git tag, the repo currently has no tagging convention - ask first.

The helper script lives next to this file at .claude/skills/bump-version/bump-version.mjs so the skill is self-contained.