production-audit

Run a production readiness audit by executing the skill on your local repository to analyze app readiness using local and user-approved evidence. It conducts pre-launch reviews and post-merge checks to identify potential production risks before a public launch or demo.

A local evidence production audit assesses app readiness for launch using only local repository data and user-approved evidence. You need it when preparing for a public launch, demo, or customer rollout to identify potential risks and issues without relying on external audit services.

Yes, you can audit app readiness without third-party data sharing by using a local-evidence audit approach. The skill analyzes user-authorized local repository data to identify production risks while explicitly excluding unpinned external code execution and third-party data sharing.

Yes, a local production audit works for both pre-launch reviews and post-merge checks. It focuses on identifying production risks in shipped apps by utilizing local repository data, allowing maintainers to assess readiness continuously throughout the development lifecycle.

A local-evidence readiness check is limited by its exclusion of unpinned external code execution and third-party data sharing. It relies strictly on local repository data and user-approved evidence, meaning it may not surface risks originating from external dependencies or runtime environments outside the local scope.

You should use a local production audit to assess app readiness without external audit services, ensuring data privacy. It leverages local repository data and user-approved evidence to conduct pre-launch reviews and post-merge checks while identifying production risks and excluding unpinned external code execution.