wtf

Audit codebases for deployment blockers, secret exposure, and security gaps.

1.4k|129|Updated Dec 11, 2020
One-click install
npx skills add https://github.com/noobnooc/agent --skill wtf-noobnooc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wtf
Source: https://github.com/noobnooc/agent/tree/main/skills/wtf
Command: npx skills add https://github.com/noobnooc/agent --skill wtf-noobnooc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of missing critical launch blockers in fast-moving "vibe coded" projects, where rushed commits or deployments can lead to exposed secrets, broken builds, security vulnerabilities, or failed production releases.

Core Features & Use Cases

  • Comprehensive Pre-Flight Audits: Scans repositories for critical blockers before commits, merges, or deployments, tailored for fast-moving AI-assisted "vibe coded" projects.
  • Multi-Domain Risk Checks: Covers repository hygiene, secret exposure, environment variable management, database migration safety, application security gaps, dead legacy code, and deployment configuration errors.
  • Use Case: A developer about to ship a new AI-built web app can run this audit to catch committed API keys, missing production build steps, and unprotected admin routes before they impact users.

Quick Start

Use the wtf skill to audit your current project for launch blockers before you commit or deploy your changes.

Frequently Asked Questions about wtf

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

FAQPage Schema
How do I run a pre-commit audit to catch exposed secrets in a vibe coded project?

A pre-commit audit scans your vibe coded project to identify exposed secrets, environment variable issues, and security vulnerabilities before code is merged. It checks repository hygiene and flags concrete commit blockers to prevent credential leaks.

What is the best way to check for deployment blockers before shipping an AI-assisted codebase?

The best way to check for deployment blockers is a pre-launch audit that reviews database migration safety, deployment configuration errors, and dead legacy code. This evidence-based review prevents failed production releases in AI-assisted codebases.

Does a pre-launch audit cover database migration safety and application security gaps?

Yes, a pre-launch audit covers database migration safety and application security gaps alongside repository hygiene and secret exposure. It provides a severity-scoped review output to catch deployment configuration errors and unprotected routes before shipping.

Can I use an automated code review to find dead legacy code and missing build steps before deploying?

Yes, you can use an automated code review to find dead legacy code and missing production build steps. The audit evaluates fast-moving projects to ensure deployment readiness and prevent production failures from rushed commits.

Why does my AI-assisted codebase need a repository hygiene check before merging changes?

Your AI-assisted codebase needs a repository hygiene check because rushed commits can lead to broken builds and failed production releases. The audit identifies concrete commit blockers and security vulnerabilities to ensure safe code merges.