security-review

Audit AMUX across five security domains and output a findings report.

64|13|Updated Mar 12, 2026

Search Tags:#ci/cd #security #review #vulnerabilities #container #risk-assessment

Ready to run

npx skills add https://github.com/prettysmartdev/amux --skill security-review-prettysmartdev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/prettysmartdev/amux/tree/main/.claude/skills/security-review
Command: npx skills add https://github.com/prettysmartdev/amux --skill security-review-prettysmartdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides a structured security review of AMUX across container security, network and API security, secrets and credentials, CI/CD supply chain, and codebase hygiene, helping teams identify and document risk before deployment.

Core Features & Use Cases

Five-domain assessment framework covering container security, network/API security, secrets management, CI/CD supply chain, and code hygiene.
Findings with file path, line number, severity, and concise description.
Output a consolidated findings table and recommended mitigations to support remediation planning.

Quick Start

Initialize the review with the security-review skill and follow the guided prompts to generate a prioritized findings report for the repository.

Frequently Asked Questions about security-review

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

FAQPage Schema

How do I perform a pre-release security review for my CI/CD pipeline and repository?▼

A pre-release security review scans your CI/CD pipeline and repository across five domains: container, network, secrets, supply chain, and code hygiene, outputting findings with severities, file paths, and mitigations.

What is a five-domain security assessment framework for container and supply chain risks?▼

A five-domain security assessment framework evaluates container security, network and API security, secrets management, CI/CD supply chain, and codebase hygiene to document deployment risks in a consolidated report.

How do I identify exposed secrets and credentials in my repository before deployment?▼

To identify exposed secrets and credentials, a structured security review scans the repository's code hygiene and secrets management domains, documenting findings with file paths, line numbers, and mitigation strategies.

Can I use a guided security review for manual repository audits and automated CI pipelines?▼

Yes, this guided security review supports both manual repository-level audits and automated CI pipelines by applying a structured five-domain framework to identify risks before deployment.

What is the best way to document container and network security vulnerabilities during a code audit?▼

The best way to document vulnerabilities is generating a consolidated findings table that lists file paths, line numbers, severities, descriptions, and recommended mitigations across all assessed security domains.