Menu
Create a versioned release of CrossTide. Use when: bumping the version number, publishing a new release, updating CHANGELOG, tagging a git commit, or preparing a GitHub release. Covers the full release checklist from version bump to git tag.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Add a new route card to the CrossTide app. Use when: adding a new view or page, creating a new CardModule, registering a new route, or wiring a card into the router, registry and test guards. Produces a complete card with registry entry, router route, view container, unit tests and E2E coverage.
Add a new technical indicator to the CrossTide domain layer. Use when: implementing a new calculator (RSI/MACD-style), adding a signal method to the consensus engine, or extending screener/backtest inputs. Covers purity constraints, the calculator + series export pair, consensus registration, property tests and generated docs.
Add a new Hono route to the CrossTide Cloudflare Worker. Use when: adding a new API endpoint, integrating a new market data provider, exposing a new server-side calculation, or adding a new WebSocket fan-out. Produces a complete, production-ready integration with KV cache, Valibot validation, rate limit, OpenAPI entry, and tests.
Debug broken API calls and fetch failures in CrossTide. Use when: a card shows an error state, data is not loading or stale, worker route returns 502, provider chain failing, or fetch never resolves. Covers worker tail logs, KV state inspection, fixture comparison, and common failure patterns.
Deploy CrossTide to Cloudflare Workers and Pages, provision KV/D1/R2 resources, verify production health, or troubleshoot deployment failures. Use when deploying, provisioning, rolling back, or checking production.
Create, apply, verify, or troubleshoot CrossTide Cloudflare D1 migrations. Use when changing database schema, applying migrations locally or remotely, checking migration status, or planning rollback migrations.
| name | release |
| description | Create a versioned release of CrossTide. Use when: bumping the version number, publishing a new release, updating CHANGELOG, tagging a git commit, or preparing a GitHub release. Covers the full release checklist from version bump to git tag. |
| argument-hint | New version number, e.g. 11.36.0 |
Use this skill only when you are doing an actual versioned release or preparing the repository for one.
For general cleanup, use .github/instructions/pre-release.instructions.md without tagging.
Update ALL of these (search the current version string, e.g. 11.35.0):
| # | File | Field / location | Notes |
|---|---|---|---|
| 1 | package.json | "version" field | Single source of truth |
| 2 | src/sw.ts | SW_VERSION constant or __APP_VERSION__ | Build-time injected when possible |
| 3 | CHANGELOG.md | New ## [X.Y.Z] section at top | Move [Unreleased] → versioned section |
| 4 | README.md | Version badge + Vitest badge | Top of file |
| 5 | .github/copilot-instructions.md | Header version (line 1) | If present |
| 6 | .github/AGENTS.md | Header > Version: vX.Y.Z line | Top of file |
| 7 | docs/ARCHITECTURE.md | Title (vX.Y.Z) | Line 1 |
| 8 | docs/ROADMAP.md | Shipped baseline: vX.Y.Z | Refresh-date header + version-history table row |
| 9 | docs-site/ content | Any version references in Astro Starlight | Only if displayed in published docs |
## [X.Y.Z] — YYYY-MM-DD
> **N tests / M suites / 0 failures** (commit `<hash>`)
### Added
- **Feature name**: brief description
### Fixed
- **Fix name**: what was broken → what was fixed
### Changed / Performance / Security
- (sections only if non-empty)
One line per item. Move from [Unreleased] block. Skip empty sections.
| Change | Bump | Example |
|---|---|---|
| New card / new worker route / new API | Minor | 11.35.0 → 11.36.0 |
| Bug fix / polish / docs | Patch | 11.35.0 → 11.35.1 |
| Breaking schema or layer redesign | Major | 11.x → 12.0.0 |
Full checklist lives in
.github/instructions/pre-release.instructions.md— load it and run every item in order.
Quick summary (PowerShell):
npm run typecheck
npm run lint
npm run lint:css
npm run lint:html
npm run lint:md
npm run format:check
npm run test:coverage
npm run build
npm run check:bundle
npm run check:contrast
node scripts/arch-check.mjs --strict
All must exit 0. Or: npm run ci.
git add -A
git commit -m "chore(release): vX.Y.Z"
git tag vX.Y.Z
git push origin main --tags
gh release create vX.Y.Z --generate-notes
release.yml auto-builds and attaches dist.zip + SBOM + provenance attestation on v*.*.* tags.
Every command below must exit 0:
npm run ci
npm audit --omit=dev --audit-level=high
npm audit signatures
Zero tolerance: 0 type errors · 0 lint errors/warnings · 0 markdownlint errors · 0 test failures · JS gzip < 250 KB · OpenAPI version matches package.json.