app-audit

Audit software projects for release readiness with a go/no-go verdict.

12|5|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/Clyra-AI/gait --skill app-audit-clyra-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: app-audit
Source: https://github.com/Clyra-AI/gait/tree/main/.agents/skills/app-audit
Command: npx skills add https://github.com/Clyra-AI/gait --skill app-audit-clyra-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits of a software project to ensure release readiness by collecting evidence and surfacing blockers, risks, and compliance gaps.

Core Features & Use Cases

  • Evidence-first assessment: compile findings from code, docs, and workflows to produce a go/no-go verdict.
  • Structured risk reporting: categorize blockers by severity and domain (security, architecture, DX, GTM).
  • Audit traceability: provide references to commands, files, and outputs for reproducibility.

Quick Start

Run an app-audit on the current repository to generate an evidence-based go/no-go report.

Frequently Asked Questions about app-audit

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

FAQPage Schema
How do I perform an evidence-based release readiness audit for a software project?▼

Release readiness audits identify whether a software project meets launch criteria by evaluating code, documentation, and workflows across product, architecture, DX, security, and GTM domains to produce a go/no-go verdict with severity-ranked blockers.

What is a go/no-go verdict in software release readiness?▼

A go/no-go verdict is the structured assessment determining if a software project is safe to launch, generated by compiling evidence from code, docs, and workflows while categorizing blockers by severity and domain.

How do I generate structured risk reports with severity blockers for my codebase?▼

Generate structured risk reports by auditing your codebase and workflows, categorizing identified blockers by severity and domain including security, architecture, DX, and GTM to surface compliance gaps and risks.

Can I audit open-source software codebases like Gait for product launch readiness?▼

Yes, you can audit OSS product codebases like Gait and similar repositories by evaluating their product, architecture, developer experience, security, and go-to-market readiness to produce a structured go/no-go verdict.

How do I ensure audit traceability and reproducibility during a release readiness assessment?▼

Ensure audit traceability by using an evidence-first workflow that provides references to commands, files, and outputs, allowing full reproducibility of the go/no-go verdict and identified blockers.

What are the limitations of using an evidence-first workflow for security audits?▼

Evidence-first security audits require accessible code, documentation, and workflows to compile findings; projects lacking these inputs may yield incomplete go/no-go verdicts or unresolved compliance gap assessments.