pr-plain-language-cleanup

Trims filler words and needless code from every changed file in a pull request.

6|1|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/jl-cmd/claude-dev-env --skill pr-plain-language-cleanup-jl-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-plain-language-cleanup
Source: https://github.com/jl-cmd/claude-dev-env/tree/main/skill-archive/pr-plain-language-cleanup
Command: npx skills add https://github.com/jl-cmd/claude-dev-env --skill pr-plain-language-cleanup-jl-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull requests often accumulate verbose prose, redundant comments, vague names, and filler wording that make diffs harder to review. This Skill reviews every line of every changed PR file and trims words, names, docs, comments, and code while preserving real behavior. ## Core Features & Use Cases - Line-by-line PR review: Dispatches one agent per changed file to read every line of code, tests, comments, docstrings, and Markdown. - Behavior-preserving trims: Removes filler, repeats, jargon, and dead notes while keeping APIs, data, test intent, error detail, and public names intact. - Measured results: Reports word-count deltas, readability changes, and diff churn separately so reviewers can verify the cleanup stayed non-material. - Use Case: After opening a documentation-heavy pull request, run this Skill to shorten prose and comments across all changed files, then commit and push the trimmed result to the PR branch. ## Quick Start Ask the agent to run the pr-plain-language-cleanup skill on your pull request link to trim filler wording from every changed file.

Frequently Asked Questions about pr-plain-language-cleanup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean up wording in a pull request automatically?▼

Provide the PR link and the skill reads the full diff, sends one agent per changed file, and trims filler words, repeats, and jargon from prose, comments, and code. It then commits and pushes the trimmed changes to the PR branch.

What does a plain-language PR cleanup change in my code?▼

It performs text-only, non-material trims: shortening comments, docs, strings, and names where meaning is preserved. It does not change behavior, APIs, data, test intent, or error detail, and it avoids reflow-only diff churn.

Can PR cleanup rename functions or variables?▼

Only when a safe full rename is clear and does not lose meaning. Public names are kept by default, and cross-file renames are handled by the main agent after searching for old names and links.

When should I not use a text-trim pass on a pull request?▼

Avoid it when the PR needs bug fixes, behavior changes, API redesign, feature work, or splitting into smaller changes. The skill explicitly stops and reports material issues instead of turning a text trim into a code fix.

How is the cleanup verified before committing?▼

The skill records before-and-after word counts, counts changed lines to detect churn, re-reads every changed file and the full diff, and runs only the smallest relevant checks for the files changed before committing.