Compare multiple NemoClaw pull requests addressing the same issue. It checks merge eligibility, correctness, quality, and attribution, then produces an evidence-based recommendation for merging or choosing a candidate for further repair.
Review NemoClaw issues and pull requests, propose issue types, project priorities, statuses, and labels, then apply only approved changes. Supports individual items and batch triage, with explanations and a report of each update.
Clean up GitHub issue and pull request titles by removing bracketed NemoClaw tags. It previews proposed changes, applies them after approval, and checks for remaining matches while preserving other tags and plain-text mentions.
Close a NemoClaw maintenance day by consolidating documentation and changelog updates, reviewing merged and unfinished work, and preparing a release handoff. When requested, pass the version to the dedicated skill that verifies and creates the release tag.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Manage isolated working environments in OpenShell using its command-line tool. Register gateways, create and connect to sandboxes, configure credential providers, and reuse workload templates with shared images, environment settings, and computing resources.
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.
Monitor GitHub Actions builds and tests with the gh command-line tool. Track runs until completion, inspect branch or pull request checks, read failed job logs, and rerun failed jobs or entire workflows.
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.
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.
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.
Develop and fix OpenShell’s keyboard-driven terminal interface using guidance on screen structure, background data fetching, themes, and navigation. Follow existing implementation patterns to add features that fit the interface’s established behavior.
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.
Diagnose failed model requests from OpenShell sandboxes to hosted APIs or local servers such as Ollama and vLLM. Check provider attachment, access rules, credentials, network layout, and client settings to identify the narrowest configuration change needed.
Assess OpenShell issues by checking first-hand use cases, reproduction evidence, existing behavior, and duplicates. Prepare a concise technical assessment, request specific missing information, and leave acceptance and roadmap decisions to human maintainers.
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.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)