yeetslop
Remove AI-generated code slop introduced in the current branch. User-invoked only.
- License 许可
- MIT
- 最近更新
- 2026-08-05
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- yeetslop
- description
- Remove AI-generated code slop introduced in the current branch. User-invoked only.
- disable-model-invocation
- true
03 SKILL.md 正文
Yeet Slop
Strip AI-generated slop out of the current branch's diff — invoked explicitly rather than chosen by the model.
1. Scope the diff
Diff the current branch against its base branch (the repo's default branch, or whatever the user names) to see everything introduced in this branch: git diff <base>...HEAD.
Complete when: the full set of changes introduced in this branch is known.
2. Scan for slop
Within that diff, look for:
- Extra comments a human wouldn't add, or that are inconsistent with the rest of the file's commenting style.
- Extra defensive checks or try/catch blocks that are abnormal for that area of the codebase — especially around calls from trusted or already-validated codepaths.
- Casts to
any(or the language equivalent) used to get around a type error instead of fixing it. - Any other style that doesn't match the surrounding file.
- Unnecessary emoji.
Complete when: every candidate instance of slop in the diff has been identified.
3. Verify before removing
For each candidate, check it against the rest of the file and nearby code — remove it only if it's actually inconsistent with established style or genuinely unnecessary, not just unfamiliar. Don't strip something that's load-bearing or already how the file normally looks.
Complete when: each candidate has been confirmed as genuine slop, not a false positive.
4. Apply and report
Make the edits directly. Report with only a 1–3 sentence summary of what was changed — no itemized list, no restating the diff.
Complete when: the edits are applied and a brief summary has been given.
04 同仓库更多 Skills
review-pass
Review a diff, branch, or PR for correctness, security, and quality issues. Use when asked to review code changes, review a PR, or do a code review — especially useful in agents without a built-in review command.
release-notes
Draft release notes or changelog entries from a commit or tag range. Use when asked to write release notes, draft a changelog, or summarize what changed between two versions or tags.
pr-writer
Draft a pull request title and description from the current branch's diff and commit history. Use when asked to write a PR description, draft a PR, or prepare a branch for review.
objfw
Opinionated guide for writing, debugging, reviewing, and testing Objective-C when the target uses ObjFW. Use for ObjFW classes and APIs, ObjFW-style types, ARC, exceptions, strings, collections, streams, sockets, run loops, portability, objfw-compile, or ObjFWTest in an ObjFW project.
noteday
Log today's work — a summary of the day plus any tickets worked on — as an entry in the personal Notion "Daily Log" database. Use when the user runs /noteday or asks to note down their day.
learn
Extract non-obvious learnings from the current session into AGENTS.md files, placed as close to the relevant code as possible. Use when asked to capture learnings, save session discoveries, or update AGENTS.md with what was learned.