Skip to content
cccskills
FreePublished on GitHub

noslop

Review a branch diff for tests that do not protect meaningful behavior, prose that adds no useful information, and unnecessary code structures. When editing is authorized, simplify the changes and verify them with focused tests.

OriginalShow the original description

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

See how to install

Good for

  • Removing tests that do not protect meaningful behavior
  • Trimming redundant comments and documentation
  • Simplifying unused helpers and compatibility code
  • Reviewing a branch diff before submission

Files included (4)

  • SKILL.md4.3 KB
  • agents/openai.yaml230 B
  • references/examples.md2.3 KB
  • scripts/scan_diff.py4.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

No-Slop Review

Load The Policies

Read these before reviewing:

  • root AGENTS.md
  • root TESTING.md
  • .agents/skills/writing-style/ai-writing-donts.md
  • the nearest module AGENTS.md and testing guide for each changed test

Read references/examples.md when the diff changes tests or prose.

Establish The Review Surface

Review the merge-base diff. Do not substitute commit history or the latest commit.

UPSTREAM=$(git rev-parse --verify origin/main 2>/dev/null || git rev-parse --verify main)
BASE=$(git merge-base HEAD "$UPSTREAM")
git status --short
git diff --stat "$BASE"
git diff --check "$BASE"
git diff "$BASE"
uv run python .agents/skills/noslop/scripts/scan_diff.py "$BASE"

List every changed test, comment, docstring, Markdown file, commit message, and draft PR title/body. Read the surrounding production code and existing tests. The scanner includes untracked files and returns candidates; inspect each one in context.

Gate Tests By Behavioral Value

For every changed test, finish this sentence:

This test fails when ___ user-visible or system behavior is wrong.

Delete or rewrite the test when the blank names an implementation detail, wording choice, supplied fixture value, or language guarantee.

Reject these patterns aggressively:

  • config in, same config out: a constructed or lowered field equals the fixture
  • constructor assignment, enum value, type, attribute, registration, or import exists
  • exact log, help, error, command, or status prose that no machine consumes
  • private state, helper call count, or assert_called_once_with
  • production logic copied into the expected value
  • is not None, does not raise, empty smoke tests, or permanent skips
  • a large matrix whose rows exercise the same branch
  • golden output produced by the implementation under test

Keep a test only when it protects a real boundary, regression, invariant, round-trip, state transition, persisted effect, wire contract, or numerical result against an independent reference.

Prefer one strong test over several weak tests. Use scratch probes for wiring and construction checks. Do not check them in.

Delete Prose Slop

Review every added or edited sentence in comments, docstrings, docs, reports, commit text, and PR text.

Delete sentences that add no fact, result, decision, constraint, or caveat. Apply the full checklist in ai-writing-donts.md. Search explicitly for:

  • X, not Y, not X, but Y, not just X, more than X
  • rather than used as rhetorical contrast
  • the main change, what this means, the real story, what matters
  • importantly, notably, it is worth noting, stepping back
  • effort narration, section narration, recap paragraphs, and generic conclusions
  • unsupported adjectives and claims that outrun measurements
  • comments that describe an earlier version of the patch

Rewrite retained prose as the concrete claim. Split a real comparison into two measured statements. Keep necessary negation such as the test has not run.

Check prose against code and artifacts. A concise false claim is still slop.

Review The Diff As A Design

After the test and prose passes, inspect each new file, helper, type, flag, dependency, compatibility path, and public API:

  1. Name its current consumer.
  2. Remove it when its consumer disappeared.
  3. Reuse an existing repository concept when it fits.
  4. Complete migrations; do not leave old and new paths active.
  5. Keep one-shot migration and debugging machinery outside reusable libraries.
  6. Remove stale comments, aliases, re-exports, shims, and defensive branches.

Fix And Verify

When edits are authorized, make the cleanup. Do not stop at a findings table while safe fixes remain.

Run the narrow affected tests, then:

./infra/pre-commit.py --changed-files --fix

Run ./infra/pre-commit.py --review only at the point required by the commit workflow. Do not claim a clean pass while known findings remain.

Report

Lead with what was removed or simplified. Report retained exceptions with their behavioral contract or evidence. If no edits were authorized, report findings as path:line, the maintenance cost, and the smallest fix.

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

ab-test-zephyr

FreeSummary

Compare Zephyr changes using the same prepared dataset and matching execution settings. Analyze Finelog metrics for each processing stage to distinguish CPU efficiency, elapsed time, and peak memory changes, then report improvements, regressions, or tradeoffs.

  • Compare Zephyr performance before and after a PR
  • Assess speed gains against additional CPU usage
  • Check peak memory and out-of-memory regressions
marin-community/marin4KUpdated Oct 22, 2026

add-dataset

FreeSummary

Register Hugging Face datasets for Marin by inspecting their structure without downloading the full dataset. Identify text fields, configurations, and data splits, then add a dataset module and validate the mapping with a sample.

  • Registering a Hugging Face dataset for Marin
  • Inspecting text fields without a full dataset download
  • Checking configurations and data splits
marin-community/marin4KUpdated Oct 22, 2026

add-grant

FreeSummary

Turn a specified GCP access request into a reviewable Pulumi change and pull request. Select the narrowest suitable role and encrypt personal email identities, covering resource permissions and Cloud Run viewer access through IAP, an access gateway.

  • Prepare a request for GCS bucket read access
  • Add a viewer to a Cloud Run service protected by IAP
  • Prepare service account impersonation permissions
marin-community/marin4KUpdated Oct 22, 2026

Add or update Pallas/Mosaic kernels, specialized computation routines for JAX. The skill covers reference implementations, output and gradient checks, public wrappers, fallback behavior, performance benchmarks, and hardware-specific tuning when requested.

  • Adding a Pallas kernel for a JAX computation
  • Checking outputs and gradients against a reference
  • Maintaining backend selection and fallback behavior
marin-community/marin4KUpdated Oct 22, 2026

Preserve old experiment scripts with a dated Git tag, a named snapshot of the code, and add comments linking related GitHub issues to the archived files and cleanup pull request.

  • Preserving a snapshot of old experiment scripts
  • Linking experiment issues to archived files
  • Updating archive notices after a tag changes
marin-community/marin4KUpdated Oct 22, 2026

babysit-zephyr

FreeSummary

Launch and continuously monitor a specified Zephyr pipeline on Iris when asked. It checks coordinator and worker health, tracks stage progress, identifies stalled or repeated failures, and requires explicit approval before stopping or restarting jobs.

  • Launch a specified Zephyr pipeline and check startup
  • Monitor stage progress and worker health over time
  • Investigate stalled stages or repeated worker failures
marin-community/marin4KUpdated Oct 22, 2026

See all skills by marin-community

Report a problem with this skill