Detect AI-generated code patterns ("slop") in PHP/Laravel and TypeScript/React source — comment narration, generic naming, premature interfaces, defensive overdose, mock-everything tests, and the absence of human "scars". Use when reviewing AI-assisted PRs, auditing code for taste/quality (not metrics — that's technical-debt), or hardening a code-review checklist. Triggers on "review for AI slop", "find AI patterns", "check code feels human", "audit code-quality taste".
Ask your Agent
Use this Skill: https://skilld.dev/gh/asyrafhussin/agent-skills/code-slop
This session only. Nothing lands on disk.
≈168 tokens on demand. Your agent reads this file only when SKILL.md points to it.
Impact: LEVEL (impactDescription)
1-2 sentences explaining why this pattern is an AI fingerprint and why it hurts.
// ❌ AI-slop exampleWhy it's slop:
// ✅ Human-equivalentWhy it reads human:
# grep / eslint / phpstan invocationReference: Link · Internal: related-rule
Source: SKILL.md on GitHub
The skill provides heuristics for auditing code quality in PHP and TypeScript projects and is generally safe. It contains a low-severity risk of indirect prompt injection because it processes untrusted source code and PR diffs using shell-based analysis tools without defining boundary markers or sanitization procedures.
No alerts
Risk: LOW · No issues
Signed by skilld at 346603c. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.
Last checked against GitHub last month.
{
"author": "agent-skills",
"version": "1.0.0"
}