gaia-security-review

Analyze changed files for OWASP Top 10 and secrets exposure.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-security-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gaia-security-review
Source: https://github.com/gaiastudio-ai/gaia-public/tree/main/plugins/gaia/skills/gaia-security-review
Command: npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-security-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Pre-merge OWASP-focused security review to catch critical vulnerabilities, secrets exposure, and misconfigurations before code merges.

Core Features & Use Cases

  • OWASP Top 10 analysis: automatically audits changed files for common web security risks.
  • Secrets and credential checks: scans for hardcoded keys and exposed secrets.
  • Audit-driven governance: generates a machine-readable verdict and updates the Review Gate for security compliance.

Quick Start

To start the security review, provide the story key to the skill.

Frequently Asked Questions about gaia-security-review

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

FAQPage Schema
How do I automate an OWASP Top 10 security review before merging code?

Automate an OWASP Top 10 security review by analyzing changed files against canonical story documents to identify web risks, secrets exposure, and misconfigurations. The process generates a machine-readable PASSED or FAILED verdict.

How does pre-merge secrets detection work for hardcoded credentials?

Pre-merge secrets detection scans changed files in a story for hardcoded keys and exposed credentials. It audits implementation artifacts to catch sensitive data exposure before code merges.

What is the best way to check authentication and authorization issues in changed files?

Checking authentication and authorization issues involves analyzing changed files for access control flaws. The review targets implementation artifacts to produce a machine-readable security verdict.

Do I need specific implementation artifacts to run a pre-merge security review?

You need canonical story files under docs/implementation-artifacts/{story_key}-*.md to run a pre-merge security review. The skill analyzes these specific files to generate its security verdict.

How do I update the Security Review gate with a PASSED or FAILED result?

Update the Security Review gate by integrating with review-gate.sh after analyzing changed files. The security review outputs a machine-readable PASSED or FAILED verdict to enforce compliance.

Can I use this security review for audit-driven governance and compliance?

You can use this security review for audit-driven governance because it generates a machine-readable verdict and updates the Review Gate. This ensures security compliance for OWASP risks and secrets exposure.