nemoclaw-maintainer-security-code-review

Review GitHub pull requests for security flaws and generate PASS/WARNING/FAIL reports.

22.1k|3.0k|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-maintainer-security-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-maintainer-security-code-review
Source: https://github.com/NVIDIA/NemoClaw/tree/main/.agents/skills/nemoclaw-maintainer-security-code-review
Command: npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-maintainer-security-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps maintainers and security engineers find security regressions and vulnerabilities introduced by code changes by producing a structured, per-category assessment that supports informed merge decisions and triage.

Core Features & Use Cases

  • Structured 9‑category checklist: Evaluates secrets, input validation, auth, dependencies, logging, cryptography, configuration, security testing, and holistic posture with PASS/WARNING/FAIL verdicts and justifications.
  • PR-focused workflow: Checks out the target branch using git and the GitHub CLI, lists and prioritizes changed files, reads diffs and file contents, and outputs detailed findings with remediation suggestions.
  • Prioritization for large changes: For large PRs, it prioritizes authentication/authorization, input handling, configs, and dependency changes to focus reviewer effort where risk is highest.
  • Use Case: Review a NemoClaw pull request before merge to detect sandbox escape vectors, Dockerfile injection, credential leakage, or blueprint tampering.

Quick Start

Use the nemoclaw-maintainer-security-code-review skill to audit the pull request URL and produce a per-category PASS/WARNING/FAIL report with remediation recommendations.

Frequently Asked Questions about nemoclaw-maintainer-security-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform a security review on a GitHub pull request before merging?

A security code review detects hardcoded secrets, injection flaws, authorization bypasses, insecure configurations, and dependency risks in pull requests by evaluating per-file diffs across a nine-category checklist to produce PASS/WARNING/FAIL verdicts with remediation guidance.

What categories does an application security audit cover when triaging pull requests?

An application security audit covers nine categories: secrets, input validation, authentication, dependencies, logging, cryptography, configuration, security testing, and holistic posture, assigning PASS, WARNING, or FAIL verdicts with justifications for each changed file.

Do I need GitHub CLI and git installed to audit repository pull requests?

For large pull requests, the review prioritizes authentication, authorization, input handling, configurations, and dependency changes to focus reviewer effort where security risk is highest, rather than analyzing every file equally.

What is the best way to detect hardcoded secrets and injection flaws in code changes?

No, this approach focuses on application security and vulnerability assessment of source code diffs, so it may not detect infrastructure misconfigurations unless they appear as insecure configurations or Dockerfile injection vectors within the pull request changes.