go-live-audit

Audit a repository and produce a GO, NO-GO, or GO-WITH-FIXES release verdict.

4|3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/ulpi-io/skills --skill go-live-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-live-audit
Source: https://github.com/ulpi-io/skills/tree/main/go-live-audit
Command: npx skills add https://github.com/ulpi-io/skills --skill go-live-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill replaces superficial pre-launch checklists with a thorough, project-tailored audit that identifies verified launch risks and produces a clear GO, NO-GO, or GO-WITH-FIXES verdict.

Core Features & Use Cases

  • Project-Tailored Auditing: Discovers the repository's stack, architecture, authority documents, product purpose, and hard rules before creating the audit.
  • Multi-Agent Verification: Runs build gates, dimension-specific read-only finders, deduplication, adversarial verification, and completeness review with bounded concurrency.
  • Launch Readiness Reporting: Groups confirmed, uncertain, and rejected findings with severity, file locations, evidence, verifier reasoning, gate results, and coverage statistics.
  • Use Case: Before releasing a production application, use this Skill to test the repository's gates, inspect applicable security and reliability dimensions, challenge reported defects, and determine whether the launch should proceed.

Quick Start

Ask the go-live-audit skill to audit the current repository before its public release and return a launch-readiness verdict.

Frequently Asked Questions about go-live-audit

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

FAQPage Schema
How do I audit my repository for release readiness before a public launch?

A pre-launch audit inspects your whole repository by running parallel typecheck, test, lint, and build gates alongside multi-agent security dimension finders to produce a GO, NO-GO, or GO-WITH-FIXES verdict.

What is a multi-agent code audit for go-live launch decisions?

A multi-agent code audit uses parallel read-only dimension finders and adversarial verification to identify confirmed pre-launch risks across your repository, deduplicating findings before issuing a launch verdict.

Can I run a pre-launch security review on my entire repository instead of just a branch?

Yes, whole-repository pre-launch security reviews apply to software repositories preparing for public releases, customer launches, or internal general availability milestones.

How do I get a launch verdict with GO, NO-GO, or GO-WITH-FIXES status?

You obtain a launch verdict by running an audit that groups confirmed, uncertain, and rejected findings with severity and evidence, returning a GO, NO-GO, or GO-WITH-FIXES status based on verified risks.

Does the go-live audit work with any tech stack or programming language?

The audit adapts to any tech stack by discovering the repository's architecture and hard rules before generating project-specific typecheck, test, lint, and build gates.

What are the limitations of automated release readiness audits?

Automated release readiness audits use read-only access and cannot modify code, so uncertain findings require manual review and the audit's completeness depends on existing authority documents and test coverage.