「release」の検索結果

Webサービスの公開前チェックリスト診断と、不足を埋める実装計画を作る。公開準備の総合確認や指定項目の診断に使う。

Use when GitHub may have shipped a GraphQL schema update affecting timeline event unions (PullRequestTimelineItems / IssueTimelineItems), when the gh-timeline dispatcher fallback is hitting more than expected, before a gh-timeline release, or when the user requests phrases like "verify timeline coverage", "audit gh-timeline schema", "check for new timeline events", "GitHub schema changed". Walks through schema diff → patch → test update → live verification → optional fixture refresh, marking each spot where a human decision is required.

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

Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.

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

Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.

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

Generate user-facing App Store release notes from git history since the last tag.

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

Explains how OpenClaw, OpenShell, and NemoClaw form the ecosystem, NemoClaw's position in the stack, what NemoClaw adds beyond the community sandbox, and when to prefer NemoClaw versus integrating OpenShell and OpenClaw directly. Use when users ask about the relationship between OpenClaw, OpenShell, and NemoClaw, or when to use NemoClaw versus OpenShell. Trigger keywords - nemoclaw ecosystem, openclaw openshell, nemoclaw vs openshell, sandboxed openclaw, how nemoclaw works, nemoclaw sandbox lifecycle blueprint, nemoclaw overview, openclaw always-on assistants, nvidia openshell, nvidia nemotron, nemoclaw release notes, nemoclaw changelog.

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

Runs the end-of-day maintainer handoff for NemoClaw. Checks version target progress, bumps stragglers to the next patch version, generates a QA handoff summary, and cuts the release tag. Use at the end of the workday. Trigger keywords - evening, end of day, EOD, wrap up, ship it, cut tag, handoff, done for the day.

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

Scan recent git commits for changes that affect user-facing behavior, then draft or update the corresponding documentation pages. Use when docs have fallen behind code changes, after a batch of features lands, or when preparing a release. Trigger keywords - update docs, draft docs, docs from commits, sync docs, catch up docs, doc debt, docs behind, docs drift.

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

Add descriptions for new models from the HuggingFace router to chat-ui configuration. Use when new models are released on the router and need descriptions added to prod.yaml and dev.yaml. Triggers on requests like "add new model descriptions", "update models from router", "sync models", or when explicitly invoking /add-model-descriptions.

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

GitHub 国内访问加速 skill，使用 githubproxy.cc 代理加速 GitHub 仓库克隆、文件下载、Raw 文件访问等操作。使用场景：(1) 需要 git clone GitHub 仓库时加速，(2) 下载 GitHub Release 文件、Raw 文件、Archive 压缩包时加速，(3) 任何需要访问 GitHub 资源但速度慢的场景

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

Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.

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

Use when working with the gh CLI or GitHub (GitHub.com or GitHub Enterprise Server): repositories, issues, pull requests, releases, GitHub Actions, or authentication. Provides safe host-aware read/write workflows. Not for Gitea/Forgejo — use `using-fj-for-forgejo` there.

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

Use when working with the fjo CLI or Forgejo/Gitea instances: repositories, issues, pull requests, releases, branches, comments, Actions, or authentication. Provides safe host-aware read/write workflows. Not for GitHub — use `using-gh-for-github` there.

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

Tracks competitors weekly across 6 signals: pricing page diffs, homepage positioning changes, blog/RSS posts, job postings (hiring as strategy signal), GitHub star velocity and releases, and daily critical-change alerts for pricing or funding keywords. Delivers a structured digest to Slack, Telegram, WhatsApp, or Discord every Monday. Fires same-day alerts for critical changes. Use when asked to "add competitor", "track competitor", "competitor digest", "what changed at [company]", "competitor report", "monitor [company]", "who is [company] hiring", "did [company] change pricing".

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

Audit wiki health — "wiki health check", "audit the wiki", "find contradictions", weekly pass, before a major content release. Catches contradictions, stale pages, orphans, duplicate concepts and broken links.

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

Review and verify unverified wiki pages — "review unverified pages", "verify wiki content", verification pass, after a major ingest cycle, before content release. The gate that turns AI-generated knowledge into trusted knowledge.

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

Migration and code evolution instructions generator for GitHub Copilot. Analyzes differences between two project versions (branches, commits, or releases) to create precise instructions allowing Copilot to maintain consistency during technology migrations, major refactoring, or framework version upgrades.

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

GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.

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

Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.

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

Comprehensive skill for working with Azure DevOps REST API across all services including Boards (work items, queries, backlogs), Repos (Git, pull requests, commits), Pipelines (builds, releases, deployments), Test Plans, Artifacts, organizations, projects, security, extensions, and more. Use when implementing Azure DevOps integrations, automating DevOps workflows, or building applications that interact with Azure DevOps services.

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

Triage and resolve Arch Linux issues with pacman, systemd, and rolling-release best practices.

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

Audit and remediate dependency/package vulnerabilities across .NET backend, frontend (npm/pnpm/yarn), and Rust projects with severity-based quality gates. Use when the user asks for SCA checks, dependency hardening, or release security gates.

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

Close out a completed workstream by updating README artifacts when needed, producing a commit message, and applying changelog-ready content when the work is ready for commit. Use after review when a stable checkpoint is ready.

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

Mandatory final risk-focused review for any repository change. Checks security, architecture boundaries, test coverage, and release readiness before closeout.

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