pre-deploy-audit

Audit applications against security, quality, CI/CD, and test requirements before the first GitHub push.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Ascenseurs-Menetrey-SA/amsa-claude-skills --skill pre-deploy-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pre-deploy-audit
Source: https://github.com/Ascenseurs-Menetrey-SA/amsa-claude-skills/tree/main/pre-deploy-audit
Command: npx skills add https://github.com/Ascenseurs-Menetrey-SA/amsa-claude-skills --skill pre-deploy-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents teams from pushing an unready application to GitHub by running a pre-deployment audit that validates security, code quality, CI/CD readiness, and test coverage before the first push.

Core Features & Use Cases

  • Pre-push readiness gate: Verifies expected setup skills (auth, deployment, etc.) and stops deployment when the score is too low or critical findings exist.
  • Multi-agent audit with scoring: Runs parallel audits for authentication security, code/documentation quality, CI/CD/deployment configuration, and tests/coverage.
  • Actionable evidence report: Creates a structured AUDIT-REPORT.md at the project root with severity-ranked findings and prioritized improvement axes.

Quick Start

Ask Claude to run the audit on your project by calling: /pre-deploy-audit /path/to/your/project

Frequently Asked Questions about pre-deploy-audit

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

FAQPage Schema
How do I run a pre-deployment security audit before my first GitHub push?▼

A pre-deployment audit evaluates your application against security, quality, CI/CD, and test requirements before the first GitHub push. You can trigger it by running /pre-deploy-audit /path/to/your/project to validate release readiness.

What is a pre-push readiness gate for code quality and CI/CD configuration?▼

A pre-push readiness gate blocks risky deployments by verifying setup skills for authentication, CI/CD workflows, and test coverage. It refuses to authorize deployment when domain scores are too low or critical findings exist.

How do I generate an audit report for authentication and test coverage findings?▼

To generate an audit report, the audit tool runs parallel checks on authentication security, code quality, CI/CD, and tests. It produces a structured AUDIT-REPORT.md at the project root with severity-ranked findings and improvement axes.

Does the pre-deployment audit support container and CI workflows with auth variants?▼

Yes, the pre-deployment audit applies to project onboarding and release readiness checks for AMSA applications, including authentication variants and container/CI workflows, validating their expected setup before deployment.

What happens if my code quality score or critical findings do not meet the deployment threshold?▼

If the code quality score or critical findings do not meet the deployment threshold, the audit refuses to authorize deployment. The generated AUDIT-REPORT.md provides prioritized improvement axes to fix the blocking issues.