1,756 件 ・ 関連度順
概要と使いどころ
Check that a tRPC change is safe for released desktop, mobile, CLI, and SDK builds, pick the compatible pattern, and decide when a deprecated procedure can be removed. Use when changing, renaming, or removing an existing procedure, input field, or output field in packages/trpc or packages/host-service, when reviewing such a PR, or when a deploy broke released clients.
日本語の概要は準備中です。原文の説明を表示しています。
Finds undocumented and rotting documentation in a CARLA checkout — unreleased features, Python bindings missing from the API reference, documented API that no longer exists, sensors and catalogue actors missing from their reference pages, broken links, and pages unreachable from the nav. Static only, no build or server. Use when the user asks to "audit the docs", "find undocumented features", "what needs documenting", or is preparing a release or a new default branch.
日本語の概要は準備中です。原文の説明を表示しています。
Downloads CARLA so nothing has to be fetched by hand — an official release package for any published version (resolved live from the GitHub releases, with AdditionalMaps), the rolling nightly Dev build, a shallow source checkout of a branch or tag, or the carlasim/carla Docker image. Reports exactly what was obtained and where, plus the environment variables the other skills read. Use when the user asks to "download CARLA", "get CARLA 0.9.16", "install CARLA", "clone the carla repo", "fetch the latest CARLA", or has no CARLA at all yet.
日本語の概要は準備中です。原文の説明を表示しています。
Installs the CARLA Python client (the `carla` package) into a chosen interpreter so the other python-api skills work — from a wheel bundled with your release or checkout, from PyPI (`pip install carla==X.Y.Z`), or by putting an older release's .egg on PYTHONPATH. Detects what is already present, picks the source that matches your simulator's version, pins numpy<2, and verifies `import carla` plus the client/server version match. Use when the user asks to "install the CARLA Python API", "pip install carla", "set up the carla python package", or when a skill reports "cannot import carla".
日本語の概要は準備中です。原文の説明を表示しています。
在 ant-design-mobile 仓库准备 npm 发版，并在用户手工发布后创建 Git tag 和 GitHub Release 时使用。
日本語の概要は準備中です。原文の説明を表示しています。
Takes a structured list of changes from changelog-scan and produces a clean, categorized, user-facing release notes draft. Follows project voice and conventions. Never publishes — only proposes a draft file or section.
日本語の概要は準備中です。原文の説明を表示しています。
Independent checker for release note drafts. Reviews accuracy against the changelog-scan data, tone, completeness, and flags breaking/security items. Use after draft-release-notes. Never let the drafter verify itself.
日本語の概要は準備中です。原文の説明を表示しています。
Turn changelog-scan output into polished, categorized release notes draft. Propose only.
日本語の概要は準備中です。原文の説明を表示しています。
Generate categorized release notes draft from scan data. Human must approve before publish.
日本語の概要は準備中です。原文の説明を表示しています。
Refresh Claude Ads platform, API, policy, regulation, benchmark, issue, pull-request, fork, and repository evidence. Use for ads research refresh, expired refresh_due dates, stale API or platform claims, reverify-or-demote decisions, release-current claim validation, ecosystem review, current platform changes, or updating paid-media knowledge. When tools or sources are unavailable, still demote the stale claim for the current run and block dependent release-current assertions before requesting access.
日本語の概要は準備中です。原文の説明を表示しています。
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legal_hold fields in _log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
日本語の概要は準備中です。原文の説明を表示しています。
Termination review — high-risk flag detection, severance + release, and final pay timing by jurisdiction. Jurisdiction-specific rules and release consideration periods are researched per review, not stored. Use when the user says "reviewing a termination", "can we fire this person", "term review", or describes a termination scenario.
日本語の概要は準備中です。原文の説明を表示しています。
Run a series of pre-release checks on the repo.
日本語の概要は準備中です。原文の説明を表示しています。
Runs a Trailmark structural review gate over a branch, pull request, fix commit, release diff, or git ref range to detect new entrypoints, new tainted paths, removed validation or authorization calls, privilege-boundary drift, blast-radius growth, complexity growth, and newly reachable sensitive sinks. Use when reviewing a PR, branch, remediation commit, or release diff where graph-level security regressions should be checked before merge.
日本語の概要は準備中です。原文の説明を表示しています。
Write an Amazon-style press release that defines customer value before building. Use when aligning stakeholders on a new product, feature, or strategic bet.
日本語の概要は準備中です。原文の説明を表示しています。
Verify a production fix by linking the changed code and release to Sentry issue state and post-release event trends without resolving issues prematurely.
日本語の概要は準備中です。原文の説明を表示しています。
Package, deploy, and verify a playable Three.js or web game. Use for release builds, asset delivery, private/public deployment, production smoke tests, browser proof, release notes, rollback readiness, and cleanup of temporary QA resources.
日本語の概要は準備中です。原文の説明を表示しています。
Generate release notes in multiple formats from git commits
日本語の概要は準備中です。原文の説明を表示しています。
Use when checking whether a Proofpack release candidate has complete local evidence before packaging.
日本語の概要は準備中です。原文の説明を表示しています。
Update Codex releases tracking (guide + landing + version bump)
日本語の概要は準備中です。原文の説明を表示しています。
Transform CHANGELOG entries into social content (LinkedIn, Twitter/X, Newsletter, Slack) in FR + EN. Use after releases or weekly to generate release notes, announcements, social media posts, or recap summaries from guide updates.
日本語の概要は準備中です。原文の説明を表示しています。
Automate version release and code commit using changeset
日本語の概要は準備中です。原文の説明を表示しています。
Create a PR to the main branch for feature/fix changes in this pnpm + Changesets monorepo. Use when the user says "PRを作成", "mainにPR", or wants to submit changes for review. Always run this in the monorepo-aware way — identify the affected package(s) and make sure a changeset exists, because the release pipeline is Changesets-driven.
Pre-release validation, npm publish procedures, and post-publish verification
日本語の概要は準備中です。原文の説明を表示しています。