Add Stop That Shit

[lennney]

Plugin submission

Add Stop That Shit to the Development & Workflow section.

• Plugin: https://github.com/lennney/stop-that-shit
• Description: Local-first scope guard for Codex with explicit task modes, before-action checks, and bounded dependency, hash, and subagent decisions.
• HOL Scanner: 95/100, 0 critical, 0 high
• Scanner CI: https://github.com/lennney/stop-that-shit/actions/runs/32038604283

The source repository runs the required HOL Plugin Scanner workflow on main and the full project CI matrix passes.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[github-actions]

✅ Contribution gate passed. @lennney, no action is required.

The previous contribution-gate failure is resolved. View the latest sweep.

[lennney]

The linked source repository is public and the required scanner workflow is present on main. This close/reopen only retriggers the contribution validator after its initial workflow-directory read returned a 404.

[lennney]

Thanks for the automated gate. The linked source repository is public and the required scanner workflow is present on main:

• Workflow file: https://github.com/lennney/stop-that-shit/blob/main/.github/workflows/hol-plugin-scanner.yml
• Source CI run: https://github.com/lennney/stop-that-shit/actions/runs/32038604283
• claude plugin validate ., full test/eval/release checks, and the HOL scan all pass; the scan reports 95/100 with 0 critical and 0 high findings.

The contribution sweep classified this PR as source repository or workflow directory was not found twice, while the public GitHub contents endpoint currently returns HTTP 200 for the same workflow directory. Could you please rerun the gate or check whether the validator's repository token is returning a cross-repository 404 for public personal repositories?

中文说明：源仓库是公开的，main 上已有符合要求的 scanner workflow，项目侧验证和扫描均通过。门禁连续两次把公开 workflow 目录判为不存在，可能是 validator 使用仓库令牌读取外部个人仓库时的权限/404 问题，麻烦维护者重新运行或检查该读取逻辑。

[kantorcodes]

Please update before merge: the current alphabetical validator reports a new inversion because appears before . Move Stop That Shit before Superloopy in Development & Workflow, rebase onto current main, and rerun the validator/checks.

[kantorcodes]

Correction to my previous review note: the current alphabetical validator reports a new inversion because Superloopy appears before Stop That Shit. Move Stop That Shit before Superloopy in Development & Workflow, rebase onto current main, and rerun the validator and checks.

[kantorcodes]

The source scanner is present and reports 95/100 with 0 critical/high findings, but the branch is based on stale Codex main e7077743 and the current contribution history still reports the alphabetical inversion noted earlier (Stop That Shit must sort before Superloopy). Please move the entry, rebase onto current main e01550e0, rerun the alphabetical/contribution checks, and request re-review.

[kantorcodes]

The source scanner remains green (95/100, 0 critical/high findings), but the alphabetical issue is still outstanding: Stop That Shit must sort before Superloopy in Development & Workflow. This branch also targets stale Codex catalog main e7077743 while current main is 70983d15. Please move the entry, rebase onto current main, rerun alphabetical/contribution checks, and request re-review.

[kantorcodes]

Codex catalog main advanced to 2da64baa after the TokenChronicle artifact sync, while this branch still targets e7077743. The source scanner remains green (95/100, 0 critical/high), but Stop That Shit still needs to move before Superloopy. Please fix the ordering, rebase onto current main, rerun checks, and request re-review.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-10T17:42:09.370088Z	63b1bd2	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.