security-review

Identify exploitable risks in code changes and generate structured security reports.

29|5|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/johnqtcg/awesome-skills --skill security-review-johnqtcg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/johnqtcg/awesome-skills/tree/main/skills/security-review
Command: npx skills add https://github.com/johnqtcg/awesome-skills --skill security-review-johnqtcg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Exploitability-first security reviews for code changes identify and surface security risks with evidence, ensuring actionable remediation and consistent governance across teams.

Core Features & Use Cases

  • Evidence-based findings grounded in code/config/runtime evidence.
  • Suppression discipline with explicit open questions and rationale.
  • Scope-based review depth with Lite/Standard/Deep options.
  • Go-specific secure-coding gates alongside general security checks.
  • Comprehensive output contracts, machine-readable JSON, and risk-acceptance workflow.
  • Reference-driven validation using design rationale and scenario checklists.

Quick Start

Run a full security-review on the latest code change and generate the standardized report.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I automate a security review for Go code changes?

This security review identifies exploitable risks in code changes by applying a comprehensive gate-driven review across auth, input, secrets, API, data, concurrency, container, and dependency domains. It presents evidence-backed findings in a structured report with suppression notes and remediation plans.

Does this security review tool support risk acceptance and suppression workflows?

Yes, this security review supports risk acceptance and suppression workflows by generating explicit suppression notes with rationale and open questions. It outputs structured risk acceptance entries and an uncovered risk list for governance tracking.

What is the best way to assess exploitability in code changes?

The best way to assess exploitability in code changes is using an exploitability-first approach that grounds findings in code, config, and runtime evidence. This method applies comprehensive gates across multiple risk domains to ensure actionable remediation.

Can I adjust the depth of a vulnerability risk assessment for different code changes?

Yes, you can adjust vulnerability risk assessment depth using Lite, Standard, or Deep scope options. This scope-based review depth scales the security review process to match the complexity and risk profile of the specific code changes.

What security gates are applied to Go-specific code changes?

Go-specific security gates are applied alongside general security checks across auth, input, secrets, API, data, concurrency, container, third-party, and dependency risk domains. These gates validate code changes using design rationale and scenario checklists.