ai-problems-detection

Enforce a five-check pre-implementation protocol to prevent AI-generated code defects.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/paulinett1508-dev/SuperCartolaManagerv5-production --skill ai-problems-detection
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ai-problems-detection
Source: https://github.com/paulinett1508-dev/SuperCartolaManagerv5-production/tree/main/.claude/skills/ai-problems-detection
Command: npx skills add https://github.com/paulinett1508-dev/SuperCartolaManagerv5-production --skill ai-problems-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents common AI programming failure modes—overengineering, reinventing existing solutions, using undocumented APIs, duplicating code, and building monolithic files—by forcing a mandatory self-check before writing or changing code.

Core Features & Use Cases

  • Pre-implementation anti-pattern checklist: Verifies simplicity, reuse, documentation knowledge, duplication risk, and modularity (e.g., file size and mixed responsibilities).
  • API and library veracity guardrails: Requires confirming method/function existence and options against the project’s dependency versions and official docs.
  • Copy/paste and monolith detection prompts: Helps identify repeated logic across the codebase and flags “everything in one place” growth before it becomes technical debt.
  • Security-focused review cues: Adds a safety step to detect credential exposure, unsafe query patterns, and sensitive-data logging tendencies.

Quick Start

Ask an AI to apply the ai-problems-detection protocol to your planned change, then have it stop and propose corrections if any of the five mandatory checks fail.

Frequently Asked Questions about ai-problems-detection

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

FAQPage Schema
How do I prevent AI from generating duplicated code and monolithic files during development?▼

You can prevent AI coding errors by enforcing a mandatory pre-implementation self-diagnostic protocol that evaluates overengineering, duplication, re-inventing existing solutions, missing documentation, and monolithic structure before code execution or commit.

What is the best way to verify API usage against installed dependency versions before committing code?▼

API verification guardrails require confirming method and function existence against the project's installed dependency versions and official documentation before proceeding with any code execution or commit.

How do I run a pre-implementation code review to catch overengineering and missing documentation?▼

Run a defined five-check workflow that evaluates simplicity, reuse, documentation knowledge, duplication risk, and modularity to catch overengineering and missing documentation during feature planning or code modification.

Can I use this anti-pattern detection protocol for reviewing existing code changes before a commit?▼

Yes, the protocol applies to reviewing code changes before execution or commit, adding security-focused cues to detect credential exposure, unsafe query patterns, and sensitive-data logging tendencies alongside structural anti-patterns.

Does the self-diagnostic workflow check for security issues like credential exposure and unsafe query patterns?▼

Yes, the self-diagnostic workflow includes security-focused review cues that detect credential exposure, unsafe query patterns, and sensitive-data logging tendencies alongside structural anti-patterns before code execution.