miqdadbadjuber/anti-slop v3.2.19

v3.2.19: the community files, and a README and guide rebuilt

on GitHub

Nothing about what antislop does changed. This release is about how a person arrives. GitHub's community profile asks a repository for four files before it reads as one a person can join rather than one they can only install, and this repository had shipped ten install paths and a guide with none of them.

The community files

• CONTRIBUTING.md is written from the things every pull request here had to be asked for rather than from a template. It opens with the two that stop a branch moving: rebase onto the current main, with the branch that sat while six releases landed under it, and raise the version, with all eleven files that have to agree with cli/package.json listed outright.
• CODE_OF_CONDUCT.md is the Contributor Covenant 2.1, verbatim, with one line changed: the canonical text leaves the enforcement contact as a placeholder, and this copy names the maintainer's GitHub account, because no email address exists here.
• Issue templates replace a blank box. The bug report asks for your agent and its version, your install route, and your operating system, and says why the last one is being asked: this repository is developed on Windows, CI runs on Linux, and macOS is the least tested of the three.
• A pull request template carries the checklist those files imply, plus a section for a new agent door that deletes itself when it does not apply.

The guardrails grew with them

The files answer to the rules the rest of the repository already follows rather than to a looser standard. The em dash check and the doc link check read all six, a new check resolves every URL a community file routes a person by, and the version check reads cli/package-lock.json twice, at the top level and inside packages[""], because npm ci installs from a stale lock without correcting it.

The README, read end to end

Install is the largest change. Ten numbered subsections that carried a paragraph of caveats beside every command became eleven short routes: a heading, one line, and the command in a block of its own. The folder detail, and every caveat that was detail rather than a warning, stayed where it was already written out in more depth, in the guide. The motion comparison is gone rather than moved: the animated GIF weighed 1.9 MB against the 583 KB of stills it repeated, and a GIF is dithered to 256 colors, which made it the lowest-fidelity copy of images the page already carried in full. The page went from 333 lines to 229.

The guide, rebuilt around routes

It had grown to five routes written out three times, one section for Install, one for Update, one for Remove, so a reader who picked the installer had to hold three places open to install, update, and remove one thing. It is one section per route now, eleven of them, each carrying its own Install, Update, and Remove. The part that could not be written by hand is new: a catalogue of every named pattern each skill teaches, generated from the skills by scripts/skill-index.mjs and read into the page between two markers. It counts 115 patterns in 22 groups, and a guardrail fails when the
guide's copy is stale.

Also in this release:

• The skills directory route told you to add --all for every skill, a flag npx skto re-run the install command to update, when the tool ships an update` command ofits own. Both were settled by asking the CLI rather than the page, and the core carried the same update instruction, so it and the skill generated from it changed with it.
• SECURITY.md said the entry-file writer left an author's blank lines exactly as they were. It follows the line ending the file already uses and tidies the blank lines at the seam where its block joins, and the page says that now.
• The doc link check read markdown links only, so an image the README points at could be deleted with all thirteen checks still green. It resolves raw HTML src and href now, and the manifest check follows a ${CLAUDE_PLUGIN_ROOT}/ path to its tail, which is how the Claude Code MCP launcher was checked by nothing at all.

Updating is unchanged:

npx antislop-ai --update

Every route is in the README's Update table and walked through in the guide. Full detail is in the ROADMAP.