1,747 件 ・ 関連度順
概要と使いどころ
Corta una nueva versión — mueve la sección Unreleased del CHANGELOG a una versión SemVer con fecha, crea el commit y el tag, y opcionalmente el release de GitHub. Úsalo cuando la persona pida publicar/cortar una versión o preparar un release (p. ej. "corta la versión 1.2.0", "prepara el release", "publica una nueva versión"). No hace push sin confirmación.
日本語の概要は準備中です。原文の説明を表示しています。
Subagent that scans CopilotKit + AG-UI releases shipped in (and just after) the report window, diffs the git tags to extract what each release actually fixed, and returns a fix-map the weekly-report writer cross-checks against open issues. Catches issues that are quietly already-fixed in a shipped release, and is the authoritative source for the "current release vX.Y.Z" version claims. Invoked by weekly-report (spawned in parallel with the Discord/GitHub pulls); runs as a general-purpose subagent so the orchestrator's context stays small.
日本語の概要は準備中です。原文の説明を表示しています。
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx skills—not domain app tutorials.
日本語の概要は準備中です。原文の説明を表示しています。
Give a harness project its own GitHub-releases update checker: the Composer dependency, the name of the release archive, the per-project credential, the release workflow, and the five checks that catch an updater which is silently doing nothing. Use when a project should install its own releases, when a release is published and never offered, or when a hand-copied update checker should move to vendor/.
日本語の概要は準備中です。原文の説明を表示しています。
Check upgrade safety for a Tamanu upgrade that spans many versions: verify that every intermediate hotfix is included in the target version, and surface the new configuration/settings, data migrations, and FHIR rematerialisation impact the upgrade brings. Use when the user wants to check an upgrade from one Tamanu version to another (e.g. "check hotfixes from v2.31 to v2.47"), confirm no intermediate hotfix was dropped, or understand what config, migrations, and FHIR rework a multi-version jump requires. Handles Tamanu's train-release model (release/X.YY branches vs vX.YY.Z patch tags) and the cherry-pick model where the same logical fix has different SHAs on different branches. Purely git-based — no live database or Canopy access needed. Not for cutting a release (see release-cutoff-checks) or deciding which tests to run (see scope-tamanu-release-tests).
日本語の概要は準備中です。原文の説明を表示しています。
xp-harness の version を上げて GitHub Release を作る開発者向け skill。現バージョン確認 → 次バージョン判定 (semver) → 変更内容のユーザー向け / 開発者向け分類 → tag + push → gh release create までの流れを定義。「リリースする」「タグを打つ」「v0.x.x をリリース」と明示されたときに発火。
Use when cutting a RELEASE CANDIDATE of riddl — tagging X.Y.Z-rc.N, publishing it as a GitHub prerelease, and later promoting it to a final release. Also use when the user says "cut an RC", "release candidate", "rc.1", or asks to promote an RC to final. For a normal release use /ship instead.
日本語の概要は準備中です。原文の説明を表示しています。
Use for ANY pull-request flow, version management, release cutting, or CI/release-pipeline troubleshooting in this repo. Covers trunk-based development on `main`, the `release` branch as deployment trigger, gate behavior, and what each release artifact is. Routes to focused agent files for each task (`agent_pr.md`, `agent_release.md`, etc.).
日本語の概要は準備中です。原文の説明を表示しています。
Backport fixes from main onto release/YYYY.WW in the ai repo with cherry-pick and rebase merge so release-please changelogs stay correct. Use when hotfixing a release branch, cherry-picking to release/*, or preparing a release backport PR.
日本語の概要は準備中です。原文の説明を表示しています。
リリースワークフロー全体のガイド。CHANGELOG 形式、セマンティックバージョニング、Git フローのベストプラクティス。「release」「リリース」「version」「バージョン」「CHANGELOG」「tag」「GitHub Release」などのキーワードで自動適用。
GitHub Releaseを作成する。前回タグからの変更を集めてリリースノートを書き、タグ作成・push・gh release createを実行。「リリースして」「vX.Y.Zを切って」と言われたら使う。
HeroUI Pro React の新リリースを公式サイトから調査し、 指定されたリリースノートドキュメントを追記更新するスキル。 「できるようになったこと・作れるようになったもの」を主軸に、 自然な日本語でユーザーストーリーとして記述する。 Trigger: HeroUI Pro リリースノート更新, heroui-pro release notes, heroui-pro更新, /dev:heroui-pro-release-notes
Automates releases and package publishing with changesets or semantic-release. Handles versioning, changelog generation, git tags, and release notes. Use for "release automation", "semantic versioning", "package publishing", or "changelog generation".
日本語の概要は準備中です。原文の説明を表示しています。
GitHubのIssue分類やPRの確認、CI失敗の調査、変更履歴を含むリリース準備、セキュリティ警告の確認を、gh CLIで進める運用スキル。
Webアプリの本番公開に向け、CI/CDによるテストと配布の自動化、Docker化、稼働確認、切り戻し手順、公開前の確認項目を整理するスキル。
Write the Discord announcement for a stable Paperclip release from the release changelog. Use when a release issue needs a copy-pasteable dotta-voice Discord post or refreshed discord_announcement document.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to finalize a release. It stamps the [Unreleased] changelog section with a version and date, runs bumpversion to update all version files, and creates the release commit and tag. Only run this when you're ready to ship.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'site launch,' 'go live,' 'pre-launch QA,' 'launch checklist,' 'GTM plan,' 'we're about to ship,' 'changelog,' 'release notes,' or 'what did we ship this week.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas. For the offer being launched (bonuses, guarantees, scarcity, naming), see offers.
日本語の概要は準備中です。原文の説明を表示しています。
Assess a Python SDK release candidate or release plan against the previous release and recommend ship or block.
日本語の概要は準備中です。原文の説明を表示しています。
Produce consistent, auditable release notes from Conventional Commits. Separates commit parsing, semantic-bump logic, and changelog rendering for automated releases with editorial control. Use when cutting a release, generating CHANGELOG.md from git history, computing the next semantic version from commits, automating release notes in CI, or planning a hotfix/rollback. Examples: 'generate the changelog for v1.4.0', 'what version bump do these commits require', 'we need an emergency hotfix process'.
日本語の概要は準備中です。原文の説明を表示しています。
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-release safety audit for the Bifrost repo. Scans database migrations changed in a release for high-scale deadlock / lock-contention risks and for work that blocks application boot time, then produces a pass/warn/fail report with a concrete remediation plan. Invoked with /release-checklist [git-ref-range]. Built to grow - new checks are appended to the Checks Registry.
日本語の概要は準備中です。原文の説明を表示しています。
Package and release a finished game mod. Covers the pre-release lint (no game files, decompiled code or leaked keys), README and install steps, credits and AI disclosure, versioning, where to upload (Nexus Mods, Steam Workshop, Thunderstore, mod.io, GitHub releases), and the post with a video. Use when the user wants to ship, share, upload, release or post a mod.
日本語の概要は準備中です。原文の説明を表示しています。