メニュー
Use this skill when preparing a release, updating the changelog, or managing the deployment pipeline. Use after a set of features have been merged and are ready for production. Don't use for individual feature PRs or bug fixes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use this skill when reviewing or auditing the AI insights system prompt for hallucination risk, prompt quality, output reliability, and cost. MDR language is delegated to the mdr-compliance-check skill + mdr-string-check CI. Don't use for general MDR audits (use mdr-compliance-check) or code review (use code-review).
Use this skill when implementing API routes, Supabase integration, authentication, webhooks, database migrations, or server-side functionality. Don't use for UI components (use frontend-feature), bug fixes (use bug-triage), or code review (use code-review).
Use this skill when auditing project dependencies for security vulnerabilities, outdated packages, or unnecessary bloat. Use on a monthly cadence or when a security advisory is reported. Complements the dependency-review CI gate (which only blocks high-severity new deps on PRs) with a proactive audit. Don't use for feature development or bug fixes.
Use this skill when triaging, investigating, or fixing a reported bug. Covers reproduction, root cause analysis, fix implementation, and regression testing. Use when assigned a bug report or when investigating unexpected behavior. Don't use for new features (use backend-feature or frontend-feature) or reviews (use code-review).
Use this skill when implementing UI components, dashboard features, landing page changes, chart visualizations, or client-side functionality. Don't use for API routes or backend work (use backend-feature), bug fixes (use bug-triage), or code review (use code-review).
Use this skill when auditing code changes for GDPR compliance, privacy policy accuracy, data flow verification, or consent mechanism review. Don't use for MDR SaMD compliance (use mdr-compliance-check) or general code review (use code-review).
| name | release-management |
| description | Use this skill when preparing a release, updating the changelog, or managing the deployment pipeline. Use after a set of features have been merged and are ready for production. Don't use for individual feature PRs or bug fixes. |
Manage AirwayLab releases, changelogs, and post-deploy verification.
npx tsc --noEmit && npm run lint && npm test && npm run build
app/changelog/page.tsx## v0.X.Y — [Date]
### Added
- [Feature description with user-facing impact]
### Fixed
- [Bug description and resolution]
### Changed
- [Modification and why]
Keep entries user-focused. "Added oximetry H1/H2 split comparison" not "Refactored OximetryResult interface to include half-split arrays."
AirwayLab deploys via Vercel on push to main. After merge:
Create a verification checklist issue assigned to the board (human) with these items:
Agent-verifiable checks (do these directly): 6. Build logs -- Verify Vercel build completed without errors. 7. API health -- Check /api/health endpoint responds 200.
If something breaks:
git revert <commit> && git pushAfter a successful release, create an announcement task for the Head of Growth:
This ensures the growth team can announce new features promptly.
Comment on the release task with: