「nvidia」の検索結果

Reorganize NemoClaw documentation pages, navigation, or content ownership while preserving published routes. Use for structural documentation refactors.

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

Plan or divide a named NemoClaw issue into independently useful changes with acceptance evidence. Use for planning requests before implementation.

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

Update NemoClaw documentation for merged behavior changes. Use for post-merge catch-up or a requested documentation drift audit.

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

Classify one failed NemoClaw GitHub Actions job using bounded, redacted logs and optional retained artifacts.

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

Find high-priority open NemoClaw security PRs to review, including competing or superseded candidates.

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

Find the repository skill for a NemoClaw task or browse the skill catalog. Use when skill selection needs help.

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

Run a NemoClaw daytime maintainer pass over release-targeted work. Use for the maintainer queue or a requested recurring pass.

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

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.

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

Guide for developing the OpenShell TUI — a ratatui-based terminal UI for the OpenShell platform. Covers architecture, navigation, data fetching, theming, UX conventions, and development workflow. Trigger keywords - term, TUI, terminal UI, ratatui, openshell-tui, tui development, tui feature, tui bug.

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

Manually dispatch and iterate on the Release Canary workflow that smoke-tests published OpenShell artifacts (install.sh on macOS/Ubuntu/Fedora, Helm chart on kind) after each Release Dev publish. Use when changing `.github/workflows/release-canary.yml`, validating a release before tagging, debugging a canary failure, or reproducing a canary job locally. Trigger keywords - release canary, release-canary, canary failed, canary dispatch, test release canary, post-release smoke, install.sh canary, helm chart canary, kind canary, dispatch canary.

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

Generate and manage Software Bill of Materials (SBOMs) for the OpenShell project. Covers SBOM generation with Syft, license resolution via public registries, and CSV export for compliance review. Trigger keywords - SBOM, sbom, bill of materials, license audit, license resolution, generate sbom, sbom csv, dependency license, supply chain, license scan.

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

Generate sandbox security policies from plain-language requirements and optional REST API documentation. Produces L4 or fine-grained L7 network policies and ordered network middleware configuration. Use for API access rules, middleware host selection, failure behavior, or built-in and operator-run middleware attachment. Trigger keywords - generate policy, create policy, update policy, change policy, sandbox policy, network policy, API policy, security policy, allow API, restrict API, network middleware, supervisor middleware.

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

Plan and implement work described in a GitHub issue, including verification, documentation, and a PR that closes the issue.

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

Start up, tear down, and configure the local Kubernetes development environment for OpenShell. Uses k3d (Docker-backed k3s) + Skaffold + Helm. Covers cluster lifecycle, optional add-ons (Keycloak OIDC, Envoy Gateway), HA testing, and port mappings. Trigger keywords - local k8s, local cluster, k3d, skaffold, helm dev, start cluster, stop cluster, tear down cluster, delete cluster, create cluster, helm:k3s, helm:skaffold, local dev environment, dev cluster, k8s dev, envoy gateway local, keycloak local, high availability, HA.

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

Validate and monitor OpenShell GitHub issues and PRs using the gator:* state machine. Use when asked to triage issues/PRs for project validity, gate PRs, run gator, validate submissions, or monitor PRs toward merge readiness.

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

Reconcile contributor skills, AGENTS.md, CONTRIBUTING.md, issue and PR templates, and workflow references after repository workflow changes.

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

Use when an OpenShell sandbox returns policy_denied, mentions policy.local, or needs a narrow network policy proposal.

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

Create GitHub pull requests using the gh CLI. Use when the user wants to create a new PR, submit code for review, or open a pull request. Trigger keywords - create PR, pull request, new PR, submit for review, code review.

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

Maintain and validate OpenShell's build-only Windows MSVC lane for x64 and ARM64. Use when working on Windows compilation, `windows:*` mise tasks, unsupported Windows compute-driver contracts, or Windows build reports. This skill does not implement Docker, Kubernetes, Podman, VM, MXC driver, policy translation, MSI, service, or supervisor runtime support on Windows.

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

Create GitHub issues using the gh CLI. Use when the user wants to create a new issue, report a bug, request a feature, or create a task in GitHub. Trigger keywords - create issue, new issue, file bug, report bug, feature request, github issue.

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

Watch and monitor GitHub Actions workflow runs using the gh CLI. Use when the user wants to check workflow status, watch a running workflow, view CI/CD jobs, or monitor build progress. Trigger keywords - watch pipeline, pipeline status, CI status, check build, monitor CI, view pipeline, pipeline progress, workflow status, actions status.

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

Implement an authorized fix for a reviewed security issue and open a PR that closes its issue.

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

Debug why an OpenShell gateway deployment is unhealthy, unreachable, or unable to create sandboxes. Use for gateway health failures, Docker/Podman runtime issues, Helm failures, Kubernetes scheduling, TLS or auth, gateway interceptors, supervisor middleware startup or runtime failures, external compute-driver sockets, VM drivers, or sandbox startup. Trigger keywords - debug gateway, gateway failing, deployment failing, helm install failing, cluster health, gateway health, gateway not starting, health check failed, sandbox pending, docker driver, podman driver, kubernetes driver, external driver, compute driver socket, gateway interceptor, supervisor middleware, middleware failed, vm driver.

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

Create OpenShell RFC proposals in rfc/ from a design request. Use when the user asks to write, draft, start, create, or update an RFC, Request for Comments, architecture proposal, API proposal, process proposal, or cross-cutting design proposal that should follow the OpenShell RFC process and template.

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