nemoclaw-maintainer-security-code-review

Review GitHub pull requests against nine security categories and report PASS, WARNING, or FAIL verdicts.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/Army161/NemoClaw --skill nemoclaw-maintainer-security-code-review-army161
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-maintainer-security-code-review
Source: https://github.com/Army161/NemoClaw/tree/main/.agents/skills/nemoclaw-maintainer-security-code-review
Command: npx skills add https://github.com/Army161/NemoClaw --skill nemoclaw-maintainer-security-code-review-army161

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually auditing pull requests for vulnerabilities, leaked secrets, injection flaws, and unsafe configurations is slow and inconsistent. This Skill provides a structured, repeatable security review of any GitHub PR with a standardized verdict report. ## Core Features & Use Cases - Nine-Category Security Checklist: Covers secrets, input validation, authentication, dependencies, error handling, cryptography, configuration, security testing, and system security. - PR and Issue Support: Accepts a PR URL directly or resolves an issue to its single open linked PR, then checks out the code with the GitHub CLI. - Structured Report: Produces an overall verdict, a findings table with severity and file locations, per-category analysis, and a list of reviewed files. - Use Case: A maintainer receives a PR that adds a new API endpoint and modifies a Dockerfile. The Skill checks out the PR, prioritizes auth and input-handling files, flags a hardcoded token and a missing authorization check, and reports a FAIL verdict with fixes. ## Quick Start Ask the agent to perform a security review of the pull request at a given GitHub URL and report the verdict for each category.

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 run a security review on a GitHub pull request?

Provide the PR URL in the format https://github.com/OWNER/REPO/pull/NUMBER. The Skill verifies the PR with the GitHub CLI, checks out the code, diffs it against the base branch, and reports a verdict for each of nine security categories.

Can I review security using a GitHub issue instead of a PR?

Yes, but the issue must have exactly one open linked closing PR. The Skill lists the issue's open closing PRs via gh issue view; if it finds zero or more than one, it stops and asks for a direct PR URL.

What security categories does a PR security audit cover?

The review covers nine categories: secrets and credentials, input validation, authentication and authorization, dependencies, error handling and logging, cryptography, configuration and security headers, security testing, and system security.

What tools are required for automated PR security review?

The GitHub CLI (gh) must be installed and authenticated, git must be available, and the environment needs network access to clone repositories and fetch PR metadata.

What happens when a pull request changes more than 30 files?

The Skill reviews files in priority order: authentication and credential handling first, then user input processing, configuration files, new dependencies, and finally everything else, ensuring security-critical surfaces are examined first.

What are the limitations of this PR security review approach?

The review stops if the PR has no changed files or no reviewable security surface. It is a static manual-style analysis guided by a checklist, so it does not execute code or run dynamic vulnerability scanners.