nemoclaw-maintainer-security-code-review

Review GitHub PR security changes against a nine-category checklist.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainers and security engineers often spend extensive time reviewing code changes in GitHub PRs and issues for vulnerabilities and insecure configurations. This Skill automates a structured security review workflow that checks out the change, analyzes the modified files, and surfaces a PASS/WARNING/FAIL verdict across a nine-category security checklist.

Core Features & Use Cases

  • Parse PR or issue URLs to determine target repository, pull/issue number, and base branch.
  • Check out the code and identify all changed files.
  • Evaluate changes against a nine-category security checklist and produce per-category verdicts (PASS/WARNING/FAIL).
  • Generate a consolidated security review report suitable for maintainer sign-off and security audits.
  • Use Case: When preparing a PR for security review or triaging an issue reporting a potential vulnerability.

Quick Start

Provide a GitHub PR or issue URL to start the security review.

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 automate security code review for GitHub PRs?▼

Automating security code review for GitHub PRs involves parsing the PR URL, checking out the change, analyzing modified files, and producing a structured per-category verdict suitable for maintainer sign-off and security audits.

How does automated vulnerability detection work for GitHub issues?▼

Automated vulnerability detection for GitHub issues analyzes the issue URL to checkout the target repository, evaluates the code changes against a security checklist, and generates a consolidated report with PASS, WARNING, or FAIL outcomes across nine categories.

Do I need git and gh installed to run an automated AppSec review?▼

Yes, git and gh are required prerequisites to checkout repository code and parse GitHub PR or issue URLs for the automated security review workflow.

What is the best way to structure a security audit for code changes?▼

Structuring a security audit for code changes requires evaluating modified files against a nine-category security checklist, producing per-category PASS, WARNING, or FAIL verdicts consolidated into a structured report for security engineers.

What categories are covered by automated PR security checklists?▼

Automated PR security checklists evaluate changed files across nine security categories, producing a PASS, WARNING, or FAIL verdict for each category to generate a consolidated security review report suitable for audits.