security-audit

Identify and mitigate security, privacy, license, and operational risks in release workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/RyoyaYahagi/skills --skill security-audit-ryoyayahagi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/RyoyaYahagi/skills/tree/main/security-audit
Command: npx skills add https://github.com/RyoyaYahagi/skills --skill security-audit-ryoyayahagi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured security and compliance review workflow for commercial releases, helping teams identify license, privacy, security, and quality risks early.

Core Features & Use Cases

  • Read project-specific rules (rules.md) to tailor checks.
  • Read references/security.md and follow the scope, scan commands, and output format.
  • If git operations are requested, invoke $git-ops and follow its policy.

Quick Start

Provide a repository with an initial audit scope and run the security audit to generate a compliance report.

Frequently Asked Questions about security-audit

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

FAQPage Schema
How do I run a pre-release security and compliance audit for my software project?

A security audit identifies and categorizes risks like license violations, exposed secrets, and improper data handling before commercial release. It applies to Node.js, Python, Rust, or other stacks by reading project-specific rules and security references to generate actionable remediation guidance.

Can I customize the security audit checks based on my project's specific compliance rules?

Yes, the security audit can evaluate risks across Node.js, Python, Rust, and other stacks. It reads project-specific rules and security references to apply its compliance checks regardless of the underlying technology stack.

Does the pre-release compliance audit support analyzing git history for security risks?

Yes, the compliance audit supports analyzing git history for security risks if git operations are explicitly requested. When invoked, it follows established git operation policies to scan for and mitigate potential pre-release vulnerabilities.

What types of operational and privacy risks are covered in a pre-release security audit?

A pre-release security audit covers operational and privacy risks by categorizing them into license compliance, permissions, exposed secrets, and improper data handling. It generates actionable remediation guidance to mitigate these identified vulnerabilities before commercial release.