git404hub

what is unslop-ci fr?

cj-vana/unslop-ci — explained in plain English

Analysis updated 2026-05-18

0TypeScriptAudience · developerComplexity · 3/5LicenseSetup · easy

tl;dr

A diff-aware CI tool that scans only the lines a pull request adds for signs of AI generated code, text, and UI, and can block the build.

vibe map

mindmap
  root((unslop-ci))
    What it does
      Scans added diff lines only
      Detects AI generated tells
      Blocks or warns in CI
    Tech stack
      TypeScript
      GitHub Actions
      Node CLI
    Use cases
      Gate pull requests for AI slop
      Pre commit staged file checks
      Audit a whole tree on demand
    Audience
      Developers
      Engineering teams

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Add a CI gate that fails pull requests carrying strong AI generated code tells.

VIBE 2

Run a pre commit hook that checks only staged changes for slop patterns.

VIBE 3

Audit an entire source tree once for lingering AI generated artifacts.

VIBE 4

Tune which rules block the build versus which only produce a warning.

what's the stack?

TypeScriptNode.jsGitHub Actions

how it stacks up fr

cj-vana/unslop-ci0xradioac7iv/tempfs52191314/web-agent-proxy-sdk
Stars000
LanguageTypeScriptTypeScriptTypeScript
Setup difficultyeasymoderatemoderate
Complexity3/53/54/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · easy time til it works · 5min

Runs via npx with no install required for a quick check, or npm install for CI and pre-commit integration.

in plain english

unslop-ci is a continuous integration tool written in TypeScript that checks pull requests for the telltale signs of AI generated content, sometimes called AI slop, and can fail a build when it finds strong ones. What sets it apart from a general code linter is that it is diff aware: it only looks at the lines a change actually adds, not the whole file or the whole repository, so you can turn it on for an old codebase without first cleaning up everything that came before. Three separate scanners run over added lines depending on the file type. The code scanner covers languages like TypeScript, Python, Go, and SQL, and looks for things like leftover chat assistant phrases, placeholder stubs such as a comment saying rest of your code, swallowed errors like an empty catch block, emoji in source code, and generic function names. The text scanner covers markdown and similar files, catching patterns like the em dash, the not just X it's Y sentence structure, assistant style sign offs, and certain overused word choices. The ui scanner covers component and style files, flagging things like untouched default component library styling, a common purple and indigo AI color scheme, and gradient heading text. The rules are ported from an existing open source project and are grounded in a large scale analysis of what people actually flag as AI giveaways online. You can run it from the command line with npx, wire it into GitHub Actions as a workflow step, or hook it into git as a pre commit check so staged changes are checked before you commit. Findings are grouped by severity, high, medium, or low, and by whether they represent an actual bug versus just a stylistic tell. The default gate blocks high severity findings and anything classified as a bug, while everything else shows up only as a warning. You can adjust this threshold, exclude paths, disable individual rules, or mark a specific line as intentional with an inline comment so the gate does not fight you on deliberate choices. Configuration lives in an unslop.config.json file at the repository root. The project is released under the MIT license.

prompts (copy fr)

prompt 1
Show me how to add unslop-ci as a GitHub Actions step that gates pull requests.
prompt 2
Help me set up unslop-ci as a pre commit hook using husky.
prompt 3
Explain the difference between the code, text, and ui scanners in unslop-ci.
prompt 4
Walk me through writing an unslop.config.json to exclude generated files and disable a rule.

Frequently asked questions

what is unslop-ci fr?

A diff-aware CI tool that scans only the lines a pull request adds for signs of AI generated code, text, and UI, and can block the build.

What language is unslop-ci written in?

Mainly TypeScript. The stack also includes TypeScript, Node.js, GitHub Actions.

How hard is unslop-ci to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is unslop-ci for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.