NVIDIA Corporation

Investigate failing or flaky NemoClaw end-to-end tests, which check complete workflows. Trace each assertion through its inputs and implementation, including cleanup and dependent jobs, and produce an evidence ledger to guide authorized repairs and reruns.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate a failing end-to-end test
• Audit assertions that execution has not reached
• Review cleanup and dependent job requirements

Audit and upgrade NemoClaw dependencies, including Hermes and base images. Trace upstream changes to affected code, implement required migrations, and verify tests, distributed artifacts, and the versions actually selected for use.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assess the impact of a dependency upgrade
• Plan migrations for a Hermes upgrade
• Verify base images and selected artifacts

Draft a NemoClaw release announcement from verified GitHub tags and shipped pull requests. Produce a local Markdown draft with an opening narrative, categorized changes, visible pull request links, and thanks to external contributors.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Drafting an announcement after a release tag is created
• Explaining shipped changes and their impact on users
• Preparing acknowledgments for external contributors

Find open NemoClaw security pull requests marked Urgent or High in the project tracker. Connect them to issues, identify competing or superseding proposals, and recommend which request a maintainer should review first.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing which high-priority security pull request to review first
• Finding competing pull requests for the same issue
• Checking declared replacement relationships between pull requests

Turn a named NemoClaw issue into an implementation plan with clear ownership, scope, completion criteria, and validation evidence. For larger changes, define independently useful steps, their dependencies, and delivery order.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan implementation for a named issue
• Divide a large change into useful steps
• Define acceptance criteria and test evidence

Find open issues affected by a proposed code change. Identify additional problems it may fix or requested behavior it may conflict with, then report supporting code differences, issue symptoms, and confidence levels.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find other open issues a PR may resolve
• Check whether a PR conflicts with requested behavior
• Prepare evidence for related-issue reviews

Review agent skills for risky behavior, excessive permissions, and hidden data sharing. It combines static scanning, which checks known risk patterns without running code, with source review to produce an evidence-based installation verdict.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a skill before installation
• Checking permissions in an installed skill
• Investigating credential access or external data sharing

Run the weekly OpenShell release captain checklist. Monday checks the pre-release train, triages failures and the compatibility review, and drafts the coordination post. Tuesday promotes the qualified pre-release after approval, verifies publication, and starts the next train. Trigger keywords - release captain, weekly release, Tuesday release, cut the release, release checklist, pre-release status, release train, start next train, stable release.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review OpenShell issues, pull requests, and failed main-branch checks, then build a local Markdown report with linked evidence and ranked recommendations. Saved progress helps resume an unfinished triage pass without changing GitHub.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing incoming issues and community pull requests
• Checking failed CI runs on main
• Prioritizing unresolved issues with supporting evidence

Process one recommendation selected by ID from a local issue or CI triage report. Apply, reject, or defer it, record the outcome, and obtain separate confirmation before each change made on GitHub.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Apply one recommendation selected by its item ID
• Reject a recommendation and record the reason
• Defer a decision for the next queue review

Promote the latest qualified OpenShell prerelease to a stable release after maintainer approval. Check that qualification matches the tag and commit, present changes since the previous stable version, and monitor the release workflow through completion.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing a qualified prerelease for stable promotion
• Reviewing changes since the previous stable release
• Creating and qualifying a missing prerelease

Turn a design request into an OpenShell RFC, a proposal for review and discussion. The skill follows the project template, assigns an available number, and organizes motivation, alternatives, and open questions into a draft.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Drafting an architecture proposal
• Organizing an API change proposal
• Documenting a process change

Review an authorized security issue in its private workflow. Check the affected code, assess whether the report is valid, explain severity and attack prerequisites, and propose a remediation plan with focused tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking whether a vulnerability report is valid
• Assessing impact and severity
• Planning fixes and focused tests

Create GitHub pull requests with the gh command-line tool. Check linked issues, contributor permissions, branch conventions, and relevant tests, then prepare a title and description that follow the project's contribution rules.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Submit code changes for review
• Open a draft pull request
• Link a pull request to its issue

Review a GitHub pull request or branch and receive a concise summary of its purpose, design choices, and notable code. Check linked issue acceptance and highlight evidence-based concerns through their observable impact on users.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Understand a pull request before reviewing it
• Summarize changes in a branch without a PR
• Review design decisions with file and line references

Turn a GitHub issue into a scoped implementation plan and, when authorized, code changes, tests, documentation, and a pull request that closes it. Check existing ownership and feedback to keep work aligned with acceptance criteria.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating an implementation plan from a GitHub issue
• Implementing an authorized issue with focused tests
• Updating documentation alongside behavior changes

Turn plain-language requirements and optional API documentation into OpenShell sandbox network policies in YAML. Define allowed destinations, programs, and API operations, with optional middleware settings for inspecting or transforming traffic and controlling what happens when processing fails.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Restrict API access to reading operations
• Allow only specific API methods and paths
• Limit internal service access by program and IP range

Keep repository contribution guidance consistent after workflow changes. Compare agent skills, coding guidance, contributor documentation, and issue and pull request templates, then fix contradictory instructions, outdated references, and mismatched inventories.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check guidance after adding or renaming skills
• Align issue and pull request conventions
• Find outdated workflow references

Launch and supervise gator agents for specific GitHub issues or pull requests in OpenShell. Check isolated execution environments, inspect logs, restart stalled agents, and test model or image overrides without changing default settings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Launch gator to review and monitor a specific pull request
• Inspect sandbox status and runtime logs
• Restart a stalled or outdated gator agent

Set up and manage a local Kubernetes development environment for OpenShell using k3d, Skaffold, and Helm. Build and deploy changes, inspect traces, configure optional authentication components, and test behavior across multiple gateway replicas.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create or stop a local OpenShell development cluster
• Rebuild and deploy changes during development
• Inspect local execution traces

Check whether OpenShell issues and pull requests fit the project, then track review feedback and automated checks. State labels show what needs attention and when a pull request is ready for maintainer approval or a merge decision.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Triage OpenShell issues and pull requests
• Check whether review feedback has been addressed
• Monitor automated checks and pending approvals

Diagnose unreachable or unhealthy OpenShell gateways and sandbox startup failures. Identify the underlying execution platform, then examine logs, authentication, certificates, and configuration with the matching tools to narrow down the cause.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate gateway connection and health check failures
• Find why a sandbox remains pending or fails to start
• Check Docker or Podman runtime and image problems

Investigate a specific OpenShell problem or feature need and create a structured GitHub issue. Record observed behavior, technical findings, alternatives, and missing evidence so a human can decide what to accept and pursue.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate an OpenShell bug and document reproduction steps
• Compare alternatives for a specific feature need
• Prepare a structured issue for human review

Create GitHub issues for OpenShell bugs, feature requests, and tasks using the gh command-line tool. Organize firsthand use cases, impact, and completion criteria into the project's templates, then return the created issue link.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Report an OpenShell bug you directly encountered
• Request a feature for a specific OpenShell use case
• Register an internal task with completion criteria