security-revisor

Validate delivery changes for LGPD, injection, and hardcoded secrets.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/joleques/northstar-ai --skill security-revisor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-revisor
Source: https://github.com/joleques/northstar-ai/tree/main/.codex/skills/security-revisor
Command: npx skills add https://github.com/joleques/northstar-ai --skill security-revisor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevent insecure or non-compliant code deliveries by detecting LGPD/data privacy issues, input validation gaps, injection risks, and hardcoded secrets before release. The skill enforces a gate that blocks delivery when critical or high-severity findings are present and produces a clear remediation path for the development team.

Core Features & Use Cases

  • Checklist-driven review for LGPD, PII exposure, input validation, injection risks, and secret management.
  • Structured gating that returns PASS/FAIL status and blocks delivery on critical or high findings.
  • Evidence-backed findings with file references, code snippets or commands, severity classification, and required corrective actions.
  • Use Case: Run as a final pre-release check for an implementation or bugfix to ensure no sensitive data leakage, unsafe query construction, or hardcoded credentials are introduced.

Quick Start

Run the security-revisor on the change by providing the demand type (bug or implementation), list of modified files, executed tests and results, and any new environment variables.

Frequently Asked Questions about security-revisor

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

FAQPage Schema
How do I check for hardcoded secrets and LGPD compliance issues before a code delivery?

To check for hardcoded secrets and LGPD compliance issues before delivery, run a pre-release security review on modified files, test results, and environment variables. This validates input, detects sensitive data exposure, and generates a structured PASS/FAIL status with mandatory remediation actions.

What is a pre-delivery security review for injection and input validation risks?

A pre-delivery security review is a checklist-driven gate that validates input handling and detects injection vulnerabilities in code changes. It produces evidence-backed findings with severity classifications and blocks delivery when critical or high-severity security risks are present.

How do I block a code release if high-severity security vulnerabilities are found?

You block a code release when high-severity vulnerabilities are found by applying structured gating during your pre-delivery review. The process returns a FAIL status, halting delivery until the development team executes the required corrective actions for the identified risks.

What context do I need to provide to review data protection and security risks in my changes?

To review data protection and security risks, you need to provide the change type, a list of modified files, executed tests and results, and any new environment variables. This minimal context allows the review to pinpoint LGPD gaps and hardcoded credentials accurately.

Does automated security review work for both bug fixes and new feature implementations?

Yes, automated security review works for both bug fixes and new feature implementations. You apply it as a final pre-release check by providing the demand type alongside modified files and test results to ensure no unsafe query construction or sensitive data leakage is introduced.