Larp Detector

Skeptical review of outside contributions to public repos. Use when reviewing, ranking, or replying to public GitHub pull requests or issues from outside contributors, or when the user says "larp-detector".

4,336 stars 628 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add davidondrej/skills --skill larp-detector
Manual install
git clone --depth 1 https://github.com/davidondrej/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/larp-detector ~/.claude/skills/larp-detector

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Larp Detector

When reviewing this code, be careful. A lot of people on public repos just use an AI coding agent to contribute to a codebase, only for the sake of their name being on the contributors list. They also have no taste and no product feel. They're not trying to fix any real issue, any real problem, or any real bug. They literally just want to contribute.

Another common thing they do is use an AI coding agent to analyze the repo for issues, problems, and security vulnerabilities. Even if our code is good, LLMs will hallucinate hypothetical issues that would really never happen.

So be careful when reviewing this. Check that it is actually a good idea, and think about the intention of the creator. What is the intention? Did they actually face a problem and then tell their coding agent to fix it? Everybody uses AI coding agents, so that alone is not a red flag.

Really try to figure out the intention and the origin of this PR, issue, or whatever you are reviewing:

- Did it come from an actual bug that a user encountered?
- Did it come from genuine care for the product and a really good idea for how to improve it?
- Or is it just a fake improvement, or support for something we don't need?
- Or does it try to fix issues that were artificially found by an LLM, but would never happen given the existing usage patterns of existing users?
Read the full skill on GitHub

Details

Skill name
larp-detector
Path
skills/larp-detector/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Larp Detector skill do?

Skeptical review of outside contributions to public repos. Use when reviewing, ranking, or replying to public GitHub pull requests or issues from outside contributors, or when the user says "larp-detector".

How do I install the Larp Detector skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add davidondrej/skills --skill larp-detector. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Larp Detector popular?

It lives in davidondrej/skills, which has 4,336 GitHub stars and 628 forks.

Related skills

Browser Harness

4.3k

davidondrej/skills

Direct browser control via CDP. Use when the user wants to automate, scrape, test, or interact with web pages. Connects to the user's already-running Chrome.

Testing & QAIn 2 lists628

4x4

4.3k

davidondrej/skills

Pull 16 fast decisions out of the user with 4 sets of 4 open questions, then present an implementation plan. Only for risky changes, large product decisions, or large refactors. Run when the user types /4x4. Agents may suggest it in one line but never start it on their own.

AI, LLMs & Agents628

Adr Verbatim

4.3k

davidondrej/skills

Record concise ADRs that preserve the user's decisions without conversational noise. Use for "adr-verbatim", "new ADR", "document that as an ADR", "record this decision", or supplied ADR wording.

Other628

Muse Review

4.3k

davidondrej/skills

Launch an independent Meta Muse Wonder Max code review through Pi and OpenRouter, and return it verbatim. Use for /muse-review, or when the user or another agent asks for a Muse review.

Git & Code Review628

Kimi Review

4.3k

davidondrej/skills

Launch an independent Kimi K3.1 Pro Max code review and return it verbatim, falling back across harnesses and routes until one works. Use for /kimi-review, or when the user or another agent asks for a Kimi review.

Git & Code Review628

Rename Process

4.3k

davidondrej/skills

Coordinate project or repository renames and moves involving Git, BB, services, or multiple machines. Preserve work and history while updating operational paths. Excludes ordinary file, code-symbol, and thread-title renames.

Git & Code Review628

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.