audit-vibecode-patterns

Detects AI-generated slop patterns in JavaScript/TypeScript codebases.

1|Updated May 2, 2026
One-click install
npx skills add https://github.com/Shankulkarni/vibe-audit --skill audit-vibecode-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-vibecode-patterns
Source: https://github.com/Shankulkarni/vibe-audit/tree/main/skills/audit-vibecode-patterns
Command: npx skills add https://github.com/Shankulkarni/vibe-audit --skill audit-vibecode-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI-generated code often includes subtle scaffolding, leftover patterns, and hardcoded placeholders that look functional but are risky in production. This skill detects these slop patterns before they reach users, reducing silent defects and maintenance toil.

Core Features & Use Cases

  • Pattern detection: flags AI scaffolding, mock data, placeholder text, unused or dead code, and misused environment values.
  • Code-quality guardrails: surfaces risky patterns that degrade reliability, security, or readability during code reviews or pre-release audits.
  • Use Case: during a PR review, run the detector to surface files containing placeholder bodies or hardcoded URLs and confirm remediation before merge.

Quick Start

Run the vibecode pattern detector on your codebase to surface AI-generated slop before merging.

Frequently Asked Questions about audit-vibecode-patterns

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

FAQPage Schema
How do I detect AI-generated slop patterns in my codebase?

You can detect AI-generated slop patterns by running static analysis and pattern matching to surface hardcoded placeholders, mock data, and environment leakage markers, outputting actionable findings with file paths and line references.

What are AI slop patterns and why do they cause production defects?

AI slop patterns are subtle scaffolding, leftover mock data, and hardcoded placeholders that look functional but introduce silent defects and maintenance toil in production environments.

How do I scan JavaScript and TypeScript projects for hardcoded placeholders during a PR review?

Run the vibecode pattern detector on your JavaScript and TypeScript projects during PR reviews to flag files containing placeholder bodies, hardcoded URLs, and misused environment values before merge.

Can I use static analysis to find environment leakage markers in AI-assisted code?

Yes, static analysis can be applied to AI-assisted code to identify environment leakage markers, dead code, and risky scaffolding patterns that degrade reliability and security during pre-release audits.

Does this pattern detector work with languages other than JavaScript and TypeScript?

The detector applies primarily to JavaScript and TypeScript projects, but it can also be used to review other AI-assisted code to surface hidden defects and scaffolding before release.

What is the best way to audit code for mock data before a release?

The best way to audit for mock data is to run pattern matching as a pre-release audit to surface risky scaffolding, confirm remediation, and prevent unused or dead code from reaching users.