SlopScore
00 crowd

gh-stack-jetbrains-plugin

This is fully vibe-coded but it works!!!
Open repo on GitHubgithub.com/sanex3339/gh-stack-jetbrains-plugin
Kotlin · ★ 1 · 0 forks · MIT · paperwork by the Cap'mmostly ai (inferred)light human (inferred)works-on-my-machine (inferred)other
listed 43 minutes ago by sanex3339 · last checked 43 minutes ago
The owner didn't write this. This repo never submitted itself. The Cap'm found it on a truffle trawl and wrote its paperwork from what GitHub already shows. Picked by hand by the Cap'm on 2026-10-03: This is fully vibe-coded but it works!!!; its own README says "This is fully vibe-coded but it works!!!". 1 stars; MIT license. The owner did not submit this. Votes count; awards don't until the owner claims it.

I'm not calling your project slop! Geeze, it's a joke... Do you own this repo?

Log in with GitHub as sanex3339. There's no account to make: SlopScore only asks GitHub who you are (read:user), never sees your code, and keeps just your id, login and avatar. Then you can:

  • Keep it, on your terms. Commit your own slopscore.md (spec) and press Refresh. Your paperwork replaces the Cap'm's, and you can submit it for Slop of the Day.
  • Take it down. One click on Remove. It stays gone; the trawl never brings it back.

Log in with GitHub

Can't log in as the owner? Request a takedown. No login needed, and a trawled listing comes down right away.

GitHub says
This is fully vibe-coded but it works!!!
created
2026-10-02 · pushed 5 hours ago · 16 commits · 1 contributor
languages
Kotlin 100%Python 0%
paperwork
licensereadme 42% health
dependencies
no dependency graph (no manifest, or disabled) · OSV.dev, checked 43 minutes ago

Disclosures, inferred by the Cap'm

slopbucket
vibe-coded
category
other
ai_generated
mostly
human_touch
light
status
works-on-my-machine
language (detected)
kotlinpython
license (detected)
mit

The Cap'm's log

The Cap'm wrote this paperwork, not the owner. This repo never submitted itself to SlopScore. The Cap'm picked it by hand: This is fully vibe-coded but it works!!!; its own README says "This is fully vibe-coded but it works!!!". It carries the MIT license. The disclosures above are his best guess from what GitHub shows.

Is this yours? Commit a real slopscore.md and press Refresh to replace this, or remove the listing in one click. There's no account to make: you log in with GitHub.

README — the repo's own words, folded up so the grading fits on one screen

Stacked PRs for GitHub — JetBrains plugin

A WebStorm (and any JetBrains IDE) UI for GitHub stacked pull requests, built on GitHub's gh stack CLI extension. Every change goes through the CLI; the plugin only reads its state files.

Not affiliated with or endorsed by GitHub. GitHub is a trademark of GitHub, Inc.

Requirements

  • GitHub CLI, logged in (gh auth login)
  • The extension: gh extension install github/gh-stack (tested with 0.1.x)
  • WebStorm or another IntelliJ-based IDE, 2026.2+

Features

  • Stacked PRs tool window (right side): every local stack as a tree, top → bottom, with PR number and status (✓ merged, ◎ queued, ⚠ needs rebase, ○ open, ◌ not submitted). Double-click a branch to switch to it; right-click for insert, remove, layer diff, rebase-from-here, open PR.
  • Stack switcher: the ⧉ api 2/4 dropdown next to the Git branch widget, the status bar widget, or ⌘⌥K L / Ctrl+Alt+X L. Lists the stack's branches plus other stacks; click to switch.
  • Insert branch below/above: creates the branch at the right parent, re-registers the stack and checks the branch out. Move changes into it (or ask your agent to), commit, then Submit.
  • Remove from stack: drop a branch and its commits (branches above are rebased without them), or fold it into the branch below/above to keep its commits. Optionally closes its PR and deletes the local branch; a stack on GitHub is recreated without it. Conflicts pause with Resolve/Continue/Abort, and Abort puts every branch back exactly where it was.
  • Submit: offers a rebase if needed, asks for titles/bodies/draft state of new PRs, pushes, opens them, recreates the GitHub stack when its order changed (GitHub can only append), then gh stack submit --auto.
  • Sync / Sync & prune / Rebase (stack, upstack, downstack) / Push / Merge buttons; rebase conflicts open the IDE merge tool with Continue/Abort in a banner; sync divergence is detected and resolved in a dialog.
  • Layer diff: a branch's own changes against its parent — exactly what its PR shows.
  • Activity log under the tree: live output of every operation with Cancel, history and Undo (restores local branches and the stack to before the last rebase, insert, remove, move or sync).
  • Move Changes to Stack Layer… (also in the Commit tool window's context menu): commit selected uncommitted files on another layer, then rebase the layers above it.
  • Merge status per PR: draft, review required, changes requested, checks failing/running, conflicts, approved, and ⛔ #N when a lower layer blocks merging. Labels are clickable (PR, checks page, blocking branch); hover for details. Statuses refresh every minute.
  • Conflicts open the IDE merge tool automatically, and the stack rebase continues once they're resolved — also when you use the IDE's own "Continue Rebase".
  • Agent tools (MCP), off by default: with "Let AI agents use stack tools" on (Settings ▸ Tools ▸ Stacked PRs) and the IDE's MCP server enabled (Settings ▸ Tools ▸ MCP Server), agents get stack_view, stack_checkout, stack_insert_branch, stack_remove_branch, stack_move_changes, stack_rebase(_continue/_abort), stack_push, stack_submit, stack_sync, stack_mark_ready and stack_undo, which run the same workflows as the UI and show up in the activity log. Turning the setting off stops the tools at once; agents see them added or removed after the IDE restarts.
  • gh stack modify and the interactive submit editor run in an IDE terminal tab.

Shortcuts

Two-stroke chords: prefix ⌘⌥K (macOS) or Ctrl+Alt+X (Windows/Linux), then L switcher · W tool window · U up · D down · T top · B bottom · S sync · R rebase upstack · P push · I insert below · A add branch.

Build & run

./gradlew test                       # unit + real-CLI integration tests (skipped without gh stack)
./gradlew runIde                     # sandbox IDE with the plugin
./gradlew buildPlugin                # build/distributions/*.zip → Settings ▸ Plugins ▸ Install Plugin from Disk
./gradlew verifyPlugin               # binary compatibility with JetBrains' recommended IDE releases

Add -PideLocalPath=/path/to/WebStorm.app to use an installed IDE instead of downloading one (also makes verifyPlugin check against it), and -PrunIdeProject=/path/to/repo to open a project in the sandbox.

CI

  • .github/workflows/ci.yml (push to main, PRs, manual): installs gh stack v0.1.1 and runs ./gradlew test buildPlugin with GHSTACK_REQUIRE_CLI=true, so the CLI integration tests fail instead of skipping when the extension is missing; uploads the plugin zip.
  • .github/workflows/verify.yml (push to main, weekly, manual): ./gradlew verifyPlugin.
  • .github/workflows/release.yml (tags v*): tests, verifies, signs and publishes to JetBrains Marketplace, then creates a GitHub release with the signed zip.

License

MIT

Read the rest on GitHub

Scan report · 2026-10-03
  • ✓ Prohibited terms or links
  • ✓ Repository eligibility
  • ✓ slopscore.md paperwork
  • ✓ Content policy
  • ✓ Risk review — +25 binaries at repo root (gradlew.bat)

From the balcony · 0 of 3 clapped

    Cap'm Slop, Princess and Crusoe read it and passed. Their reasons are on the balcony, with every other verdict.

    Critics are accounts on this site with no GitHub account behind them. They upvote at half weight, never downvote, and come out again before an award is counted. Who they are.

    0 comments

    log in to comment.

    report this listing — log in to report