Menü
Bump version, update changelog, commit, and tag a new DepVault CLI release
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Create a pull request with a well-structured title and description based on branch commits.
Migrate a React @tanstack/react-form codebase from the prop-drilled `useForm` + erased-form-type pattern to the official `createFormHook` composition API (`useAppForm` / `withForm` / `field.X`). Use when a project threads a `form` object (often cast to an `any`-erased type like `ReactFormExtendedApi<any,...>`) through field-wrapper components that take `form`+`name` props, and you want typed field names/values, no casts, and reusable bound field components. Triggers: "migrate forms to createFormHook", "adopt useAppForm/withForm", "remove AnyReactForm cast", "type-safe tanstack form fields".
Best practices for Remotion - Video creation in React
Create GitHub issues from user requirements, a PRD document, or conversation context, and add them to a GitHub Project with priority, size, and type fields.
Basierend auf der SOC-Berufsklassifikation
| name | release-cli |
| description | Bump version, update changelog, commit, and tag a new DepVault CLI release |
| user-invocable | true |
Create a new DepVault CLI release by bumping the version, adding a CHANGELOG
entry, committing, and creating a git tag that triggers the Release CLI
workflow.
The user provides a version number (e.g. 1.6.0) or a bump type (major,
minor, patch). If no argument is given, default to a patch bump.
apps/cli/DepVault.Cli.csproj — the <Version> elementapps/cli/CHANGELOG.md — Keep a Changelog format, newest on topcli/vX.Y.Z (matches .github/workflows/release-cli.yml trigger cli/v*)## [X.Y.Z] section from
apps/cli/CHANGELOG.md and uses it as the GitHub Release body. If no section
exists for the tag's version, the release job fails — so the changelog entry
is not optional.linux-x64, osx-x64,
osx-arm64, win-x64 and attaches archives to the GitHub ReleaseDetermine the new version:
apps/cli/DepVault.Cli.csproj (the <Version> element)1.6.0), use itmajor, minor, patch), calculate from currentPre-flight checks:
git status reports no changes)main (or ask the user if on another branch)cli/vX.Y.Z already exists (git tag -l)Bump version:
<Version>CURRENT</Version> with <Version>NEW</Version> in
apps/cli/DepVault.Cli.csprojUpdate apps/cli/CHANGELOG.md:
Read the existing file
Ask the user what changes to include in this release (or confirm entries they've already drafted)
Insert a new section at the top (above any existing version sections) in the form:
## [X.Y.Z] - YYYY-MM-DD
- Bullet 1
- Bullet 2
Use today's date in YYYY-MM-DD
Do NOT modify or remove existing entries
The new section must be non-empty — the release workflow will fail without it
Commit the changes:
apps/cli/DepVault.Cli.csproj and apps/cli/CHANGELOG.mdchore(cli): release vX.Y.ZCreate an annotated tag:
git tag -a cli/vX.Y.Z -m "DepVault CLI vX.Y.Z"Report the result:
git push && git push origin cli/vX.Y.Z to trigger
the Release CLI workflow, which will publish the GitHub Release with
the CHANGELOG section as the body and AOT binaries for all four RIDs--no-verify or --no-gpg-sign if hooks fail — report the failure instead