「release」の検索結果

Transform academic papers into university press releases for general.

日本語の概要は準備中です。原文の説明を表示しています。

Determine the next version, update the marketing site, and run the full release pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

Checklist and automation guide for adding a new skill to the OPC Skills project. Ensures all required files, metadata, logos, and listings are created before release. Use when adding a new skill, publishing a skill, or preparing a skill for release.

日本語の概要は準備中です。原文の説明を表示しています。

Run the full R package release gate — regenerate docs, run the test suite, run R CMD check --as-cran, and triage every ERROR / WARNING / NOTE against CRAN policy before a release or submission. Use when the user says "check my R package", "R CMD check", "is this package CRAN-ready", "run devtools::check", "prepare for CRAN submission", or points at a directory containing a DESCRIPTION file. Produces a check report + CRAN-submission checklist in `quality_reports/`.

日本語の概要は準備中です。原文の説明を表示しています。

Pre-screen analysis outputs (tables, figures, logs) built on restricted or confidential data for statistical-disclosure-limitation problems before any release. Scans for small cell counts, complementary-suppression gaps, dominance (p-percent / (n,k)), re-identifiable exact counts, PII leakage, and unrounded sensitive statistics; classifies each finding CRITICAL / WARNING / OK and gates on any CRITICAL. Use before depositing or sharing restricted-data results, or when the user says "disclosure check", "SDL scan", "is this output safe to release", "check for small cells", "disclosure avoidance", "pre-screen for the RDC", or "can I export this from the enclave".

日本語の概要は準備中です。原文の説明を表示しています。

Publish or update a game on Steam with Steamworks and SteamPipe: configure depots and packages, upload builds with steamcmd, set a build live on a branch, and run the release checklists. Use for Steam publishing, app_build.vdf/steamcmd uploads, depots, beta branches, or a store page release.

日本語の概要は準備中です。原文の説明を表示しています。

Convert a git log, commit list, or release notes into a polished, user-facing changelog. Use when writing release notes, generating a CHANGELOG.md entry, or documenting what changed in a version. Produces a structured changelog section with version header, categorised changes, and migration notes. For an already-curated change list use changelog-writer instead.

日本語の概要は準備中です。原文の説明を表示しています。

Write changelogs and release notes readers actually benefit from — changes translated to so-whats, grouped by reader impact (breaking first, gifts second, plumbing last), with the upgrade path stated and the marketing kept honest. Use when asked write the release notes, turn this commit list into a changelog, announce this update to users, or why does nobody read our changelogs. Produces the impact-grouped changelog, the so-what translations, the breaking-changes block with migration steps, and the two-audience split when needed.

日本語の概要は準備中です。原文の説明を表示しています。

Turn a list of changes, commits, or PRs into clean release notes / a changelog entry. Use when asked to write release notes, a changelog, or a version announcement from raw changes. Produces a Keep-a-Changelog-style entry grouped by type (Added/Changed/Fixed/etc.), written for users — surfacing breaking changes and upgrade notes up top. To go straight from a raw git log use changelog-generator instead.

日本語の概要は準備中です。原文の説明を表示しています。

Use when running or planning an Apache Struts release on any maintenance line (6.x, 7.x) - cutting the tag, staging artifacts, opening the vote, promoting, updating the site and announcing - or when asked what the next step in a release is.

日本語の概要は準備中です。原文の説明を表示しています。

Use when setting up or optimizing developer workflows in a monorepo, managing mise tasks, git hooks, CI/CD pipelines, database migrations, or release automation. Invoke for development environment setup, build automation, testing workflows, and release coordination.

日本語の概要は準備中です。原文の説明を表示しています。

Release-gate sequence: validate → review → push → tag. Wraps kernel:git mechanics with the pre-ship safety chain. Triggers: ship, release, push to main, ready to merge, deploy.

日本語の概要は準備中です。原文の説明を表示しています。

Generate categorized release notes from any source (GitHub, Linear, Jira, or manual input) with optional publishing

日本語の概要は準備中です。原文の説明を表示しています。

Use when planning an AISTATS project timeline from venue fit through abstract submission, full-paper upload, supplementary material, review release, author-reviewer discussion, decision, camera-ready, PMLR publication, registration, presentation, and artifact release, with backward-planning offsets for theory-plus-experiments papers.

日本語の概要は準備中です。原文の説明を表示しています。

Maps between gene identifier systems (Ensembl, Entrez, HGNC symbol, UniProt, RefSeq, MANE) using AnnotationDbi, biomaRt, mygene, pyensembl, and Ensembl REST. Encodes Ensembl version stripping with GENCODE _PAR_Y preservation, the Ziemann 2016 Excel autocorrect debacle and Bruford 2020 HGNC renames (SEPT*->SEPTIN*, MARCH*->MARCHF*, MARC*->MTARC*, DEC1->DELEC1), OCT4/POU5F1 alias resolution, biomaRt archive endpoints for release pinning, the `filters` (plural) gotcha, MANE Select for clinical reporting, cross-species orthology via Ensembl Compara / OMA / OrthoDB, and tx2gene construction for tximport. Use when converting gene IDs across systems, handling renamed symbols, building tx2gene, pinning to a specific Ensembl release for reproducibility, or mapping cross-species orthologs.

日本語の概要は準備中です。原文の説明を表示しています。

Automate versioning and changelog generation using semantic versioning principles. Configure release automation, version bumping, and changelog tools. Use when implementing version management or automating release processes.

日本語の概要は準備中です。原文の説明を表示しています。

Choose and apply the correct semantic version bump for this repository. Use for every user-visible release, before merge when a change set should ship as patch, minor, or major, and whenever package/plugin/desktop version metadata must stay synchronized.

日本語の概要は準備中です。原文の説明を表示しています。

Deploy and manage Kubernetes workloads with progressive delivery. Use for deployments, rollouts, blue-green, canary releases, scaling, and release management.

日本語の概要は準備中です。原文の説明を表示しています。

Manage Helm charts, releases, and repositories. Use for Helm installations, upgrades, rollbacks, chart development, and release management.

日本語の概要は準備中です。原文の説明を表示しています。

Release pipeline checklist

日本語の概要は準備中です。原文の説明を表示しています。

Release coordination across departments

日本語の概要は準備中です。原文の説明を表示しています。

Expert delivery management for release planning, deployment strategy, incident response, change management, SLA/error-budget tracking, and DORA metrics across continuous delivery pipelines.

日本語の概要は準備中です。原文の説明を表示しています。

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,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum.

日本語の概要は準備中です。原文の説明を表示しています。

把项目推送到 GitHub，三种模式自动判断：**首次推送**（大文件扫描 → 生成 .gitignore → git init → gh 建仓 → 推送）、**日常更新**（commit + push）、**版本发布**（打 tag + 建 Release，可附下载文件）。核心原则是安全第一：推之前必扫大文件和敏感文件，宁可多问一句也不把不该推的东西推上去。当用户说"推到GitHub""推送到GitHub""git push""上传到GitHub""提交并推送""发版本""打release""打tag""/git-push"时触发。不适用于：规划哪些功能进哪个版本号（用 issue-pool——本 skill 只负责把已经定好的版本号打成 tag）、复杂 git 操作如 rebase/cherry-pick/解冲突/改历史/回滚（直接用 git 命令，本 skill 不覆盖）、代码写完前的自测和验收。

日本語の概要は準備中です。原文の説明を表示しています。