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.
Validate the staging NemoClaw Brev Launchable by checking its web deployment flow, environment access, deployed image, and preinstalled user journey. Report inference results and missing dependencies separately as advisory evidence outside automated end-to-end testing.
Analyze saved NemoClaw CI timings to rank consistently slow command-line tests and compare base-image publication with reuse. Read-only analyzers report execution times, runner queues, and sample coverage as bounded JSON output.
Classify a failed NemoClaw GitHub Actions job using logs with sensitive information hidden and output size limited. Optionally inspect saved artifacts to identify failure patterns and gather evidence for further investigation.
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.
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.
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.
Find the right NemoClaw skill for a task using a catalog organized for users, maintainers, and contributors. Understand which skill handles documentation, setup, implementation, reviews, or releases, and choose an appropriate starting point.
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.
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.
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.
Review a NemoClaw pull request for security risks by examining changed code, configuration, and dependencies. Assess nine categories and report findings with severity, file locations, and recommended fixes, alongside an overall assessment of whether it is safe to merge.
Publish or update a NemoClaw pull request and track automated checks and reviews through completion. It preserves the requested scope, coordinates repairs for valid findings, and reports the latest commit’s results and remaining blockers.
Run NemoClaw live end-to-end tests, which check complete workflows, or inspect existing release evidence. Routes requests to local or trusted GitHub workflows and reports the tested commit, results, workflow link, and relevant job links.
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.
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.
Continuously monitor automatic end-to-end tests on NemoClaw main, group failures by root cause, and coordinate fixes and peer reviews through GitHub. Track ownership and merge readiness while checking whether later runs confirm each repair.
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.
Analyze the full retained history of one NemoClaw pull request to identify contributor, review, and automation delays. Generate a summary and an interactive timeline file, then compare observed timing with a default ten-minute target or a requested alternative.
Answer NemoClaw maintainer questions using policy references covering issue and pull request assessment, labels, project fields, releases, and competing contributions. It explains the relevant rules in plain language through a read-only workflow.
Recheck older NemoClaw bug reports against the reported and newest releases, then prepare evidence-backed recommendations for maintainers. It documents reproduction results and proposed updates for approval without automatically closing issues.
Run one NemoClaw maintainer pass focused on work for a target release. Select a ready pull request, small repair, security concern, or test gap, complete one outcome, and record progress and decisions requiring user input.
Implement an accepted NemoClaw issue or repair a classified pull request finding. Keep changes within the agreed scope, run focused checks for affected behavior, and review the final changes before handing evidence to an authorized publication workflow.
Prepare and create a signed NemoClaw release tag for a requested version, then monitor release workflows, documentation, and published images. It records maintainer decisions and drafts an announcement after verifying the remote tag.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)