Skip to content
cccskills
FreePublished on GitHub

stop-slop

Prose final-pass editor for GitHub issue bodies, pull request bodies, release notes, README/docs changes, public comments, and user-facing explanations. Use when Codex drafts or revises substantial prose that will be published or committed, especially when the user asks to polish, de-slop, make it less AI-written, improve a PR/issue body, or prepare docs text; do not use for ordinary code implementation, debugging transcripts, logs, quoted text, command output, API names, or Chinese conversational replies unless explicitly requested.

The English summary is being prepared. Showing the original description.

Works withGitHub
See how to install

Files included (6)

  • SKILL.md2.0 KB
  • agents/openai.yaml248 B
  • LICENSE1.0 KB
  • references/examples.md1.6 KB
  • references/phrases.md2.8 KB
  • references/structures.md5.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Stop Slop

Use this skill as a final prose pass, after technical facts are correct.

Workflow

  1. Preserve facts, scope, and intent.
  2. Leave code blocks, commands, logs, stack traces, quoted source text, identifiers, API names, filenames, branch names, commit messages, and test names unchanged unless the user explicitly asks to rewrite them.
  3. For English prose, remove formulaic AI phrasing, throat-clearing, empty emphasis, stock transitions, fake symmetry, inflated claims, and punchline endings.
  4. Prefer concrete nouns, direct verbs, and specific consequences over vague summaries.
  5. Keep useful technical caution. Do not remove uncertainty, caveats, or passive voice when they make the engineering claim more accurate.
  6. Keep the output in the user's requested language and tone. For Chinese output, use the reference files only as a smell list, not as English style rules.
  7. If a reference detail is needed, read only the relevant file:
    • references/phrases.md for filler phrases and stock wording.
    • references/structures.md for formulaic paragraph and sentence shapes.
    • references/examples.md for before/after patterns.

Output Rules

  • Return the revised text, not a scoring report, unless asked.
  • Mention material factual changes separately if any were unavoidable.
  • Keep Markdown structure valid and preserve links.
  • Do not make the prose more combative or marketing-like.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

adhx

Free

Read public X/Twitter post URLs as structured evidence through the ADHX API. Use for relevant user-provided or research-discovered x.com, twitter.com, or adhx.com links. ADHX does not search X, and long-form Article content may be incomplete.

The English summary is being prepared. Showing the original description.

bioinformatist/codex-base9Updated Oct 16, 2026

Design, review, or report a measured performance comparison. Use for benchmark methodology, speedup or regression claims, and performance-based choices; not generic performance discussion, ordinary dependency bumps, local renames, or prose edits.

The English summary is being prepared. Showing the original description.

bioinformatist/codex-base9Updated Oct 16, 2026

Trace what an actual code change could break beyond its diff when interfaces, serialized data, database schemas, configuration, caches, lifecycle ordering, or cross-language consumers are involved. Use for explicit impact analysis; not local renames, prose edits, ordinary dependency bumps, or generic architecture discussion.

The English summary is being prepared. Showing the original description.

bioinformatist/codex-base9Updated Oct 16, 2026

Shared vocabulary for designing deep modules, interfaces, seams, adapters, leverage, and locality. Use when designing or reshaping module boundaries, making code more testable, or evaluating interface depth.

The English summary is being prepared. Showing the original description.

bioinformatist/codex-base9Updated Oct 16, 2026

Plan or implement retirement of a system, API, feature, persisted configuration, or database shape. Use for compatibility cutovers, explicit deprecation review, or an explicit unreleased replacement decision, including determining whether consumers or data exist; not ordinary dependency bumps, local renames, prose edits, or generic architecture discussion.

The English summary is being prepared. Showing the original description.

bioinformatist/codex-base9Updated Oct 16, 2026

Disciplined diagnosis loop for hard bugs, regressions, flaky failures, and performance problems with unclear cause. Use for root-cause debugging after a concrete symptom exists; do not use for routine implementation or speculative cleanup.

The English summary is being prepared. Showing the original description.

bioinformatist/codex-base9Updated Oct 16, 2026

See all skills by bioinformatist

Report a problem with this skill