「upgrade」の検索結果

Handle cqs schema version upgrades — check version, attempt migration, rebuild if needed.

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

Check for and apply Spec Kit CLI updates via `specify self`. USE FOR: checking whether a newer specify-cli release is available, previewing an upgrade with --dry-run, upgrading the CLI in place (optionally to a pinned tag). DO NOT USE FOR: checking project tools/integrations (use speckit-check) or managing extensions/presets/integrations/workflows.

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

Use this skill to monitor and verify a deployed URL after releases — checks HTTP endpoints, SSE streams, static assets, console errors, and performance regressions after deploys, merges, or dependency upgrades. Smoke / canary / post-deploy verification.

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

Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.

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

Plan, create, and configure production-ready Google Kubernetes Engine (GKE) clusters using the golden path Autopilot configuration. Covers Day-0 checklist, Autopilot vs Standard, networking (private clusters, VPC-native, Gateway API), security (Workload Identity, Secret Manager, RBAC hardening), observability, scaling, cost optimization, and AI/ML inference. WHEN: create GKE cluster, provision GKE environment, design GKE networking, secure GKE, optimize GKE cost, GKE autoscaling, GKE inference, GKE upgrade, GKE observability, GKE multi-tenancy, GKE batch, GKE HPC, GKE compute class.

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

Use when preparing hardest high-leverage work for a stronger or scarce model, building a ranked execution queue, asking for fable prep, frontier prep, round-collapse, wave queue, or model-upgrade readiness across code, design, copy, marketing, or architecture work.

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

Design, audit, harden, review, or upgrade MCP servers and MCP Apps with revision-aware protocol profiles, explicit HTTP/deployment boundaries, capability-centered validation, bilingual reporting, and reproducible evidence. Use for MCP server architecture, JSON-RPC or Streamable HTTP bugs, security hardening, protocol-version migration, MCP Apps widget boundaries, review reconciliation, test planning, and public engineering evidence.

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

Apply this opinionated workflow when modernizing legacy systems: strangler fig pattern, branch by abstraction, characterization tests, incremental monolith decomposition, framework upgrades, feature-flagged migration with rollback.

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

Audit and maintain the learnings in `docs/solutions/` against the current codebase — fix drifted paths and links, merge overlapping docs, replace guidance the code no longer supports, delete obsolete docs, reconcile the `CONCEPTS.md` glossary, then report and commit. Also bootstraps `CONCEPTS.md` on request and, when asked, culls docs whose reasoning the code already explains. Use for "refresh the learnings", "audit docs/solutions", "are our solution docs still accurate", "clean up / prune the learnings", "create a CONCEPTS.md", or after a refactor, rename, migration, or dependency upgrade that likely invalidated documented solutions. Not for capturing a new learning — use `learn-with-docs`.

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

Prepare, validate, package, or review a dygo framework release and its upgrade path. Use for versioning, tags, binaries, Studio and Core bundling, installers, archives, checksums, and release smoke checks.

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

Coordinate large-scale codebase migrations and multi-file refactors across hundreds of files. Manage framework upgrades, API renames, and config rewrites using batched PRs, issue tracking, and CI verification.

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

Evaluate an incoming workflow upgrade — a skill, MCP server, subagent, library, external service, prompt, or pattern — through one disciplined pipeline before adopting it. Security is a blocking gate. Records every verdict so the same thing is never evaluated twice. Use when considering a new tool from a post, repo, or recommendation. Triggers — "vet this", "should we adopt", "is this safe to install", "evaluate this skill/MCP", "what do you think of this tool".

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

Initialize or safely upgrade a processor project's root AGENTS.md from a maintained baseline. Use when starting a processor project, adding project-level Agent collaboration rules, or comparing an existing AGENTS.md with the package baseline. This skill only handles AGENTS.md; it does not scaffold documentation, inspect or configure environments, install tools, or modify processor source.

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

Fallback for general coding work that does not match any specific sextant sub-skill. Use for lightweight tasks: config changes, style fixes, utility functions, one-off scripts, or tasks too small to warrant a dedicated workflow. All dedicated sub-skills take priority over this one — check these first: sextant:fix-bug (broken behavior), sextant:debug (unknown bug location), sextant:add-feature (new functionality), sextant:modify-feature (changing existing behavior), sextant:review-code (evaluating code), sextant:write-tests (test coverage), sextant:refine-requirements (ambiguous scope), sextant:plan (multi-step sequencing), sextant:ship (release prep), sextant:migrate (cross-module upgrade), sextant:security (vulnerability audit). Only use this skill when none of the above match.

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

The Rembric TUI installer contract — the single, canonical install/setup/upgrade/uninstall path (`apps/plugin/install.sh`, fronted by the repo-root `install.sh` shim). Apply when touching `install.sh`, the root shim, any per-client `install.sh`/`uninstall.sh`, `marketplace.json`, or distribution docs (README, `docs/agents.md`, plugin/client READMEs). Covers the orchestrator model, what must not break, and where the source of truth lives. For running the validation suite, use `rembric-tui-installer-e2e`.

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

Managing third-party dependencies — version pinning, security auditing, license compliance, update workflows, lockfile management, supply chain security. Activate on "npm audit", "dependabot", "renovate", "pin versions", "dependency update", "supply chain", "license compliance", "lockfile", "security advisory", "typosquatting", "SBOM". NOT for internal monorepo package management (use monorepo-management) or publishing your own packages to npm/PyPI.

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

Use before non-trivial coding work to pick a task-appropriate working mode — debug, fix, review, test-first, refactor, optimize, migrate, upgrade, integrate, spike, or unstuck — then follow its checklist. Modes are procedures, not personas. Not needed for trivial one-line edits or non-coding tasks.

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

Use when a project depends on Homebrew formulae or casks, when creating or editing a Brewfile, or when adding brew install/upgrade automation to a project.

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

Use when hardening a Linux host you operate — SSH posture, a default-deny firewall baseline, and unattended security upgrades, each verified on the box rather than assumed from a config file.

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

OCM/OpenClaw envs: create, clone, upgrade, runtimes, services, logs, cleanup.

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

Upgrade or synchronize Agent Skills, or determine a Skill's source and ownership across runtimes and roots. Use only for those lifecycle decisions. Do not use for installation, creation or editing, validation, inventory, usage statistics, general audits, cleanup, packaging, publishing, or ordinary file and package work.

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

Phase 4 Turn 2 of disease-market-sizing-orchestration (A6' upgrade). Audits compose output via Cite-or-Block strict — every anchor must reverse-resolve to an actual file in sources/, every fact claim must have an anchor. Returns verdict (ok/blocked) + violations list. Use AFTER cite-bound-content-generator (Turn 1), BEFORE report-bundle-builder (phase 5).

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

Use the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish, cloud, cloudrun, feedback, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, auth, tts, and remove-background. Also use when diagnosing build or render failures. validate, inspect, and layout are deprecated aliases; use check. Covers local, HeyGen-hosted cloud, AWS Lambda, and Google Cloud Run rendering.

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

Create and evolve production-ready skills with reusable scripts, references, and validation. Use for new skill creation, skill upgrades, and enforcing consistent metadata and structure.

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