Agent skill

Unslop Review

by MohamedAbdallah-14 in MohamedAbdallah-14/unslop

Rewrites code review comments so they read like a human teammate wrote them.

MITAuto-check passedWriting & Content

Install Unslop Review

skills CLI
$ npx skills add MohamedAbdallah-14/unslop --skill unslop-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install MohamedAbdallah-14/unslop unslop-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/MohamedAbdallah-14/unslop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/unslop-review .claude/skills/unslop-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
unslop-review
GitHub stars
155
Used in
3 other repos
Token cost
~980 tokens
SKILL.md length
490 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Rewrites code review comments so they read like a human teammate wrote them.

  • User says humanize review
  • SKILL.md covers Purpose, Trigger, Format and Rules, plus 2 more sections
  • Calls git
  • De-slop PR comment

What it does

Unslop Review is an agent skill from MohamedAbdallah-14/unslop. Rewrites code review comments so they read like a human teammate wrote them. Cuts corporate-AI throat-clearing ("I noticed...", "I was wondering if perhaps...", "It might be worth considering..."). Each comment is direct: location, the issue, a concrete fix. Use when user says "humanize review", "de-slop PR comment", "make this feedback sound human", "review this PR", "code review", "/review", "/unslop-review". Auto-triggers when reviewing PRs.

Its SKILL.md is about 980 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Writing & Content, covering Humanizing AI text and Code review. The repository describes itself as: Make AI output sound human. Strips AI-isms (sycophancy, stock vocab, hedging stacks, em-dash pileups), preserves code/URLs/headings. Plugin for Claude Code, Cursor, Windsurf… The licence is MIT.

When your agent uses it

  • User says humanize review
  • De-slop PR comment
  • Make this feedback sound human

Example prompts

  • “I noticed...”
  • “I was wondering if perhaps...”
  • “It might be worth considering...”
  • “/unslop-review”

What it can do on your machine

Read from SKILL.md and the folder at commit 29d4360. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Unslop Review loads about 980 tokens when it runs. Until then it costs about 116 tokens; SKILL.md has 490 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~116
When it runs · the whole SKILL.md, loaded when a task matches
~980

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from MohamedAbdallah-14/unslop at commit 29d4360, republished under its MIT licence (© MohamedAbdallah-14). 490 words, ~980 tokens.

Download SKILL.mdSave it as .claude/skills/unslop-review/SKILL.md (or your agent's skills folder).
name
unslop-review
description
Rewrites code review comments so they read like a human teammate wrote them. Cuts corporate-AI throat-clearing ("I noticed...", "I was wondering if perhaps...", "It might be worth considering..."). Each comment is direct: location, the issue, a concrete fix. Use when user says "humanize review", "de-slop PR comment", "make this feedback sound human", "review this PR", "code review", "/review", "/unslop-review". Auto-triggers when reviewing PRs.

Unslop Review

Purpose

Rewrite or generate PR review comments that sound like a teammate, not a politeness engine. Direct on the issue, concrete on the fix, kind on the human.

Trigger

/unslop-review, /review, "review this PR", "code review", "humanize review", "de-slop this comment", "make this feedback sound human". Auto-trigger when reviewing pull requests.

Format

Default shape: L<line>: <severity prefix> <observation>. <fix>.

Severity prefixes (optional but use them when severity matters):

  • bug: — code is broken or will break
  • risk: — works today, fragile tomorrow (perf, race, missing test)
  • nit: — style, naming, dead code, "while you're here"
  • q: — genuine question, not a hidden complaint

Multi-file: <file>:L<line>: <severity> <observation>. <fix>.

Range: L88-140: ... when the issue spans lines.

Rules

Drop
  • Throat-clearing: "I noticed that...", "It seems like...", "It looks like to me..."
  • Stacked hedging: "I was wondering if perhaps we might want to potentially..."
  • Polite-padding: "I would kindly suggest...", "just a small suggestion..."
  • Per-comment praise: "Nice work on this function but...", "Great pattern, however..."
  • Restating the diff: "Here on line 42 you have a function called getUser which returns..."
  • Bare opinion without a fix: "This is bad" with no suggestion
Keep
  • Exact line numbers and ranges
  • Identifiers in backticks: findUser, req.body.id
  • Concrete fix or concrete question
  • "Why" only when the fix isn't obvious
Tone

Human, not corporate. "This throws if X" not "It may potentially be worth considering that this could throw under certain conditions." Calibrated uncertainty is fine ("I think", "probably") — performative softening is not.

Auto-clarity (use full prose, not one-liners)
  • Security findings (CVE-class, auth, secrets)
  • Architecture disagreements that need a real discussion
  • Onboarding context for a new contributor
  • When the answer is genuinely "this is fine"

In those cases use a short paragraph, then resume terse for the rest.

Examples

Show full SKILL.md (203 more words)Show less
Bad → good
  • Bad: I would kindly suggest that we might want to potentially consider adding a null check here as it could maybe lead to issues in some scenarios.

  • Good: L42: bug: \findUser` returns undefined when no match. Guard before `user.email` or early-return 404.`

  • Bad: Great work on this implementation! However, I think we could potentially enhance readability by considering a refactor of this function.

  • Good: L88-140: nit: this function does validation, I/O, and mapping. Splitting them would make the happy path easier to follow. Happy to pair on a cut if helpful.

  • Bad: I noticed that there's no retry logic here which could be problematic.

  • Good: L23: risk: no retry on 429. Wrap the call in \withBackoff(3)` so we don't drop legitimate requests.`

  • Bad: This implementation leverages a robust caching strategy.

  • Good: (delete — empty praise. If the caching is genuinely interesting, explain why specifically.)

Approval

If the change is solid and you have nothing concrete: LGTM on its own line. No boilerplate.

Boundaries

  • Comments only. No commits, no git push, no auto-approve, no linter runs.
  • Output is paste-ready: one comment per line, or a clearly separated list.
  • Severity must be honest. Don't downgrade a bug to a nit to soften the message.

© MohamedAbdallah-14, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/unslop-review of MohamedAbdallah-14/unslop.

Open the folder on GitHubat commit 29d4360

Used in 3 other repositories

We found 8 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in MohamedAbdallah-14/unslop, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Unslop Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Unslop Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Unslop Review this skillMohamedAbdallah-14/unslop1553 repos~980Automated safety check: PassMIT
SepiaNanako0129/sepia3.1k—~3.6kAutomated safety check: PassMIT
Noslopmarin-community/marin3.9k—~1.1kAutomated safety check: PassApache-2.0
Korean Commit Message Polisherepoko77-ai/im-not-ai5.9k—~504Automated safety check: PassMIT
Chinese Technical Writingleter/zh-tech-writing352—~656Automated safety check: PassMIT
DeslopMrZoyo/deslop-GPT138—~4kAutomated safety check: PassMIT

Similar skills

  • Sepia

    Nanako0129/sepia

    Make AI-generated writing read as human-written, in fiction and in professional prose.

    3.1k GitHub stars~3.6k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Noslop

    marin-community/marin

    Deslop, simplify, or review low-value tests and prose only when explicitly requested for a branch or diff.

    3.9k GitHub stars~1.1k tokensUpdated today
    Writing & ContentAuto-check passed
  • Korean Commit Message Polisher

    epoko77-ai/im-not-ai

    Rewrites Korean commit messages that read like office jargon or translation into natural wording, leaving the type, scope and meaning untouched.

    5.9k GitHub stars~504 tokensUpdated 15 days ago
    Writing & ContentAuto-check passed
  • Chinese Technical Writing

    leter/zh-tech-writing

    Sets writing rules for Chinese technical docs: short plain sentences, consistent typography and a checklist for removing AI-sounding filler.

    352 GitHub stars~656 tokensUpdated 16 days ago
    Writing & ContentAuto-check passed
  • Deslop

    MrZoyo/deslop-GPT

    Audit or apply evidence-backed, test-first subtractive cleanup for accumulated agent-created test bloat, verification theater, and defensive or fallback bloat while preserving independent external…

    138 GitHub stars~4k tokensUpdated 4 days ago
    Writing & ContentAuto-check passed
  • Ship

    millionco/react-doctor

    Take the current branch from done-coding to merge-ready in one pass — review the diff against AGENTS.md, deslop, commit and push, open a PR using rule-validate's PR copy, then babysit until mergeable.

    15k GitHub stars~716 tokensUpdated today
    DevelopmentAuto-check passed

More from MohamedAbdallah-14/unslop

  • Unslop Commit

    MohamedAbdallah-14/unslop

    Rewrites commit messages so they sound like a careful human engineer wrote them.

    155 GitHub starsUsed in 1 repo~927 tokens
    Auto-check passed
  • Unslop File

    MohamedAbdallah-14/unslop

    Humanize natural-language memory files (CLAUDE.md, todos, preferences, docs) by removing AI-isms and adding burstiness while preserving every code block, URL, path, command, and heading exactly.

    155 GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check: warnings
  • Unslop Help

    MohamedAbdallah-14/unslop

    Quick-reference card for unslop modes, sub-skills, and slash commands.

    155 GitHub starsUsed in 1 repo~623 tokens
    Auto-check passed
  • Unslop Reasoning

    MohamedAbdallah-14/unslop

    Strip AI-slop patterns from reasoning traces (chain-of-thought, extended thinking, agent decomposition) — not final prose.

    155 GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • Unslop

    MohamedAbdallah-14/unslop

    Humanize LLM output so it reads like a careful human wrote it.

    155 GitHub starsUsed in 1 repo~4.1k tokens
    Auto-check: warnings

Questions about Unslop Review

What does Unslop Review do?

Rewrites code review comments so they read like a human teammate wrote them. Unslop Review is an agent skill from MohamedAbdallah-14/unslop. Rewrites code review comments so they read like a human teammate wrote them.

When should I use Unslop Review?

Unslop Review fits situations like: user says humanize review; de-slop PR comment; make this feedback sound human.

How do I install Unslop Review in Claude Code?

Run `npx skills add MohamedAbdallah-14/unslop --skill unslop-review -a claude-code`. Or copy the skill folder (skills/unslop-review in MohamedAbdallah-14/unslop) into .claude/skills/unslop-review in your project. Claude Code loads it when a task matches its description.

How do I install Unslop Review in Codex?

Run `npx skills add MohamedAbdallah-14/unslop --skill unslop-review -a codex`. Or copy the skill folder (skills/unslop-review in MohamedAbdallah-14/unslop) into .agents/skills/unslop-review in your project. Codex loads it when a task matches its description.

Can I use Unslop Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MohamedAbdallah-14/unslop --skill unslop-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/unslop-review, .gemini/skills/unslop-review, .github/skills/unslop-review and .opencode/skills/unslop-review in your project.

What does Unslop Review need to run?

Going by SKILL.md and its folder, Unslop Review needs the command-line tools its instructions call (git).

Does Unslop Review access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Unslop Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Unslop Review use?

Unslop Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Unslop Review use?

About 980 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Unslop Review?

Skills that share tags, products or a category with Unslop Review: Sepia (Nanako0129/sepia, 3.1k stars), Noslop (marin-community/marin, 3.9k stars), Korean Commit Message Polisher (epoko77-ai/im-not-ai, 5.9k stars) and Chinese Technical Writing (leter/zh-tech-writing, 352 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Unslop Review?

MohamedAbdallah-14 (a GitHub user) maintains it in MohamedAbdallah-14/unslop, which has 155 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 5, 2026.

Source: MohamedAbdallah-14/unslop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.