security-audit

To scan code for security vulnerabilities, this Skill analyzes your codebase and configuration files to detect common security flaws and secrets exposure, generating a ranked report with actionable remediation steps.

Validating code compliance requires security rules defined in your contexts/rules/ directory, which this Skill uses to check your deployed environments and configurations against governance policies and produce a compliance status report.

Automating governance checks for code implementation involves enforcing security as a system rule; this Skill runs periodic validations against defined contexts/rules/ to identify violations and rank them by severity.

Yes, predefined security rules are required to perform a vulnerability audit, as the Skill validates your code and configurations against rules stored in contexts/rules/ to determine compliance status and generate remediation guidance.

You should run a security audit after deploying a new feature to ensure no new security risks were introduced, verifying that all security policies are met before going live and maintaining a robust security posture.

A security vulnerability report includes a ranked list of identified security flaws and governance violations, accompanied by actionable remediation steps to fix the issues and ensure compliance with your defined security rules.