القائمة
Release a new beta version - bumps versions in both package.json files, commits, tags, and pushes
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when writing tests for peek-stash-browser. Covers Vitest + React Testing Library (client) and Vitest + integration testing (server). Follow these conventions exactly.
Run all validation checks before tagging a new release
Use when starting a new coding session, beginning work on a branch, or resuming after a context reset. Gathers branch context, in-progress work, plan documents, and recent history to produce a briefing before any code is written.
Perform a code quality review before creating a PR. Use when reviewing changes, checking code quality, or doing a self-review of the current branch. Invoked as part of the work-ticket lifecycle after verification-before-completion and before finishing-a-development-branch.
Use when preparing or executing a release of peek-stash-browser. Covers the full release lifecycle from validation through Docker image publishing.
Express 5 patterns for peek-stash-browser — TypeScript backend serving a React SPA with HLS video proxying, multi-instance Stash server routing, JWT auth via HTTP-only cookies, and SQLite via Prisma. Use when writing or modifying Express route handlers, middleware, proxy controllers, or streaming endpoints in the peek project.
| name | release-beta |
| description | Release a new beta version - bumps versions in both package.json files, commits, tags, and pushes |
Beta versions follow this pattern: X.Y.Z-beta.N
3.2.2-beta.3 → 3.2.2-beta.4)3.2.2-beta.3 → 3.2.3-beta.1)main branch and it's up to dateclient/package.json version fieldEdit BOTH files to the SAME new version:
client/package.json - update "version" fieldserver/package.json - update "version" fieldCRITICAL: Both files must have identical version strings.
git add client/package.json server/package.json
git commit -m "chore: bump version to X.Y.Z-beta.N"
git push origin main
The tag MUST match the version with a v prefix:
git tag vX.Y.Z-beta.N
git push origin vX.Y.Z-beta.N
Example: Version 3.2.3-beta.1 → Tag v3.2.3-beta.1
v prefix or typo)