Skip to content
Back to skills

Tails Review

ASecurity

Code review focused on all four LLM_Tails pillars: over-engineering (Ponytail ladder), hallucination risks (unverified APIs, invented patterns), consistency violations, and architecture misunderstandings. One line per finding. Use when the user says "review", "tails review", "/tails-review", "check this diff", or "what's wrong with this". One-shot report, applies nothing.

  • 3 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 9, 2026
ai-agentsgoapi

Works with

  • api

Security analysis

A100/100

Scanned October 9, 2026

npx -y skills add savadks95/LLM_Tails --skill tails-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Tails Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Tails Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/savadks95-tails-review/badge)](https://www.skillsdirectory.com/skills/savadks95-tails-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: tails-review
description: >
  Code review focused on all four LLM_Tails pillars: over-engineering (Ponytail
  ladder), hallucination risks (unverified APIs, invented patterns), consistency
  violations, and architecture misunderstandings. One line per finding. Use when
  the user says "review", "tails review", "/tails-review", "check this diff",
  or "what's wrong with this". One-shot report, applies nothing.
---

Review diffs through the four LLM_Tails lenses. One line per finding.

## Format

`<N>. L<line>: <tag> <what>. <fix>.`, or `<N>. <file>:L<line>: ...` for
multi-file diffs. Number findings across the whole report so the user can
say "fix 2 and 5".

## Tags

### Pillar 2 — Minimal code
- `delete:` dead code, unused flexibility, speculative feature. Replacement: nothing.
- `stdlib:` hand-rolled thing the standard library ships. Name the function.
- `native:` dependency or code doing what the platform already does. Name the feature.
- `reuse:` equivalent helper already in this repo. Name the path.
- `yagni:` abstraction with one implementation, config nobody sets, layer with one caller.
- `shrink:` same logic, fewer lines. Show the shorter form.

### Pillar 3 — Hallucination risks
- `unverified:` API call, import, or config key that may not exist. Needs verification.
- `invented:` function signature or pattern that doesn't match the actual library/framework.
- `stale:` references deprecated API, removed feature, or outdated pattern.

### Pillar 4 — Consistency violations
- `naming:` doesn't match project naming convention. Name the convention.
- `pattern:` doesn't match established project pattern. Name the pattern.
- `style:` import ordering, comment style, formatting doesn't match.

### Pillar 1 — Architecture
- `scope:` change doesn't account for all callers/callees. Name the missed path.
- `root-cause:` patches symptom, not the root cause. Name where the real fix goes.

## Scoring

End with:
```
net: -<N> lines possible, <M> hallucination risks, <K> consistency issues.
```

Nothing to flag: `Clean. Ship.`

## Boundaries

Lists findings, applies nothing. One-shot.
"stop tails-review" or "normal mode": revert.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.