一键在 Manus 中运行任何 Skill

slop-removal

星标0

分支0

更新时间2026年3月19日 19:34

Remove AI-generated comment slop from a branch diff. Use when the user asks to clean up AI comments, remove slop, or strip unnecessary comments from a branch.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

finbarrtimbers

finbarrtimbers/DotFiles

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Remove AI Slop from Branch Diff

What counts as slop

Remove ONLY clearly AI-generated filler:

Comments that restate what the code obviously does (e.g., # Increment counter, # Return the result)
Phrases like "This is important because...", "Note that...", "We need to..."
Overly verbose docstrings that describe trivial behavior
Section headers that add no information (e.g., # Main logic, # Helper function)

What to keep

Do NOT remove:

Comments that explain non-obvious logic, edge cases, or algorithmic choices
References to external specs, papers, or issues
TODOs and FIXMEs
Type annotations or parameter descriptions in docstrings

Workflow

Run git diff origin/main..HEAD to see all changes on the branch
Identify slop comments introduced in this branch (not pre-existing)
Show me the list of proposed removals BEFORE making any edits
After confirmation, make the edits — only comment/docstring deletions, no code changes
Run the linter (make style && make quality) and confirm tests still pass
Commit with message "Remove AI-generated comment slop"

同仓库更多 Skills

同仓库

compare-wandb-runs

finbarrtimbers/DotFiles

Compare metrics between two wandb runs (new vs old format). Use when comparing DPO training runs to verify metric consistency.

2026-03-190

fix-permissions

finbarrtimbers/DotFiles

Suggest the minimal permission rule for the most recent denied tool call. Use when Claude was prompted for permission and you want to allow it permanently.

2026-03-190

fix-pr-comments

finbarrtimbers/DotFiles

Read review comments on a GitHub PR and fix the issues raised. Use when the user asks to address, fix, or resolve PR comments or review feedback.

2026-03-190

review-interview-code

finbarrtimbers/DotFiles

Review PyTorch interview prep solutions on the current branch. Use when the user asks to review interview code, review PyTorch solutions, or invokes /review-interview-code.

2026-03-190

update-pr-body

finbarrtimbers/DotFiles

Update the body of a GitHub pull request. Use when the user asks to update, edit, or modify a PR description/body.

2026-03-190

monitor-experiment

finbarrtimbers/DotFiles

Monitor Beaker experiments until completion. Use when the user asks to monitor, check, or track a Beaker experiment.

2026-01-150

name	slop-removal
description	Remove AI-generated comment slop from a branch diff. Use when the user asks to clean up AI comments, remove slop, or strip unnecessary comments from a branch.

Remove AI Slop from Branch Diff

What counts as slop

Remove ONLY clearly AI-generated filler:

Comments that restate what the code obviously does (e.g., # Increment counter, # Return the result)
Phrases like "This is important because...", "Note that...", "We need to..."
Overly verbose docstrings that describe trivial behavior
Section headers that add no information (e.g., # Main logic, # Helper function)

What to keep

Do NOT remove:

Comments that explain non-obvious logic, edge cases, or algorithmic choices
References to external specs, papers, or issues
TODOs and FIXMEs
Type annotations or parameter descriptions in docstrings

Workflow

Run git diff origin/main..HEAD to see all changes on the branch
Identify slop comments introduced in this branch (not pre-existing)
Show me the list of proposed removals BEFORE making any edits
After confirmation, make the edits — only comment/docstring deletions, no code changes
Run the linter (make style && make quality) and confirm tests still pass
Commit with message "Remove AI-generated comment slop"