@yamada-ui/pr-review-anti-patterns
AAdd or remove entries in .agents/references/pr-review-anti-patterns/. Use when the user wants to document a review miss from one or more merged PRs, or remove a stale anti-pattern entry.
Install
agr install @yamada-ui/pr-review-anti-patterns --target claudeWrites 1 file into .claude/skills/, pinned to git-99afd659.
- .claude/skills/pr-review-anti-patterns/SKILL.md
Document
name: pr-review-anti-patterns description: "Add or remove entries in .agents/references/pr-review-anti-patterns/. Use when the user wants to document a review miss from one or more merged PRs, or remove a stale anti-pattern entry." metadata: internal: true
Overview
Add or remove entries in the PR Review Anti-Patterns, which collect cases from past PRs where each AI approved changes that the maintainer disagreed with, or where each AI approved based on incorrect knowledge or interpretation.
Gotchas
- When adding, modifying, or deleting files, always do so in a new worktree branched from
origin/main. - Keep the PR title as a single sentence that is clear to others. Do not reuse the commit message as the PR title.
- Write the title and summary of each PR Review Anti-Patterns entry using search-friendly keywords so that the relevant entry is easy to find.
Steps
0: Branching
Branch on each step based on whether $ARGUMENTS is provided.
- If arguments are provided: proceed to step 1.a.
- If no arguments are provided: proceed to step 1.b.
1.a: Add
Follow the procedure to execute.
1.b: Delete
Follow the procedure to execute.
Trustgrade A
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-99afd659dfe12026-07-31