Rewrite PR review comments to be direct and human-sounding.
npx skills add https://github.com/MohamedAbdallah-14/unslop --skill unslop-review
Please help me install this Agent Skill. Skill: unslop-review Source: https://github.com/MohamedAbdallah-14/unslop/tree/main/plugins/unslop/skills/unslop-review Command: npx skills add https://github.com/MohamedAbdallah-14/unslop --skill unslop-review
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.
Rewrite a PR review comment to be direct, actionable, and human-sounding.
High-intent search queries and answers about installing and using this skill.
Rewriting PR review comments involves removing corporate hedging phrases like "It might be worth considering" while preserving the location, issue, and concrete fix. This ensures code review feedback reads like a direct, actionable human teammate suggestion.
Writing direct pull request feedback requires clearly stating the issue and recommended fix without hedging. Rewrite feedback to remove throat-clearing phrases and preserve explicit references, ensuring the comment remains actionable across common languages and diff contexts.
Yes, this PR comment humanizer works across common languages and diff contexts. It rewrites code review comments to sound human by removing hedging phrases and preserving explicit references, ensuring feedback remains direct regardless of the programming language.
The best way to automate peer feedback is to rewrite PR comments directly, removing corporate-AI hedging and preserving the location, issue, and concrete fix. This approach ensures feedback sounds like a human teammate while maintaining actionable formatting expectations.
Automated code reviews sound robotic due to corporate-AI throat-clearing phrases like "I was wondering if perhaps." Rewriting these comments to directly state the issue and concrete fix eliminates hedging and makes the feedback sound like a human teammate.
Yes, you can preserve explicit code references when rewriting PR review comments. The rewriting process keeps explicit references intact while removing throat-clearing phrases, ensuring the location, issue, and concrete fix remain clear and actionable.
KjellKodAutomate draft pull request creation, CI monitoring, and review comment resolution.
kanade0404Process GitHub pull request review threads into replies and summary comments.
randalmurphalGenerate structured code review feedback with evidence and severity guidelines.
boraoztuncRemove AI-writing patterns like filler phrases and passive voice from prose.
