security-audit

Auditing a game's codebase for security vulnerabilities involves scanning save handling, networking, input validation, data exposure, and dependency supply chain. This Skill produces a prioritized Markdown report with severity classifications and remediation guidance.

Prioritizing game security risks involves classifying save tampering and network exploit findings by severity (CRITICAL/HIGH/MEDIUM/LOW). This approach orders remediation tasks by impact and effort, creating a structured plan to fix critical vulnerabilities first.

Yes, the game security audit covers third-party dependency supply chain risks. It scans your repository's dependencies and plugins to identify potential vulnerabilities, integrating these findings into the overall security assessment report.

Yes, this code audit checks multiplayer network authority and input validation. It evaluates whether your game properly sanitizes user inputs and maintains server-side authority to prevent common cheat vectors in multiplayer environments.

To re-audit game code after fixes, run the security audit in full mode against your updated repository. It supports quick re-audits and can write the final prioritized report directly to disk for production tracking.

Running a game security audit requires providing engine or language context, a source directory manifest, and the ability to run greps and analysis tasks. These inputs enable comprehensive vulnerability scanning across your codebase.