sa-es-ir/rookery scored 29/100 on Slopicide
Human-led
Mostly human fingerprints, with the odd assist.
What stood out
How strongly each pattern showed up overall, and in how many of the files.
- Boilerplate padding1/8 files · 23%
More lines, wrappers and ceremony than the job needs.
- Assistant tells1/8 files · 13%
Emoji in logs, 'in a real application…', placeholder TODOs.
Human fingerprints
- Pragmatic shortcuts7/8 files · 48%
Terse idioms and deliberate omissions an experienced author takes.
- Domain-specific naming6/8 files · 40%
Names that show deep familiarity with the problem.
- Lived-in code6/8 files · 37%
Idiosyncrasies and quirks of code that evolved over time.
- Comments explain why2/8 files · 24%
Comments about trade-offs, gotchas, bugs and workarounds.
Files we looked at
The files behind the score, sloppiest first.
- cli/src/logo.rs82out of 100
Rust · 3.2 KB
- skills/systematic-debugging/find-polluter.sh53out of 100
Shell · 1.9 KB
- Assistant tells 84%
- Boilerplate padding 33%
Pattern spotted: emoji in comments or log messages
17echo "🔍 Searching for test that creates: $POLLUTION_CHECK"18echo "Test pattern: $TEST_PATTERN"19echo ""2021# Get list of test files (find . emits ./-prefixed paths, so accept the22# pattern written with or without a leading ./)An example of the pattern; it doesn’t affect the score. View on GitHub
- ui/flow.js24out of 100
JavaScript · 15 KB
- cli/logo.py16out of 100
Python · 4.3 KB
- cli/src/config.rs15out of 100
Rust · 15 KB
- cli/src/approve.rs14out of 100
Rust · 33 KB
- cli/src/main.rs13out of 100
Rust · 22 KB
- agent.py1out of 100
Python · 130 KB
Scanned Oct 31, 2026 from main. A playful gut check, not a verdict on the people behind the code. How scoring works. More recent reports.