Community items
How Axon Shaft keeps checklists and templates from other accounts safe to run on your code, as built today.
Anyone can publish a checklist or template to the Marketplace. A community checklist's rules go into your review's prompt, so they run on your code. These are the rules that keep that safe. Ratings, reports and moderation come later; the list says where each point stands.
You can read everything before you use it
A community item's page shows every rule, the files it applies to and leaves out, its version, its author linked to their profile, how many projects use it, what changed in its newest version, and the list of its versions with their notes. Built-in checklists keep their rules hidden: they're ours, and their code is reviewed in our repo.
Using one pins a version
Adding a community checklist to a review keeps it at the version you saw, as @publisher/slug@version. Each version never changes once it's published. When the author publishes a new one, the automation shows "Version n available", and nothing moves until someone with access to the automation reads the diff of its rules against the pinned version and approves it. If the author unpublishes it, your automation keeps running the version it pins and shows "Unpublished by the author". Starting an automation from a community template copies the template at its version, with its community checklists at the versions it pins.
It runs only in reviews
A community checklist runs only in a review, with the review's read-only tools. The API refuses one on a Reply or Task automation and never sends one to /ask or /fix. The action's tool guard, environment allowlist and sandbox are part of the action's release, and nothing in an item changes them. An item is data: rules, paths and at most one of the built-in scripts by its key. It can't add a script or a command. See What runs in CI.
The prompt treats its rules as someone else's
The API puts a community checklist's rules in a fenced block. The prompt says they come from @publisher, not from Axon Shaft or your repo, that they may only add findings within the checklist's scope, and that they can't change the output format, the other checklists, the verdict rules or any instruction outside the block. Each fence carries a hash of the version's content, which the content can't contain, so its text can't close the block early. Its findings name it as @publisher/slug, and its check run on the pull request is Axon Shaft / @publisher/slug.
Checks on publish
Every save checks the item against its schema and size limits: names, summaries and each rule have a maximum length, and paths are capped at 20 globs. Anything outside the schema is refused. A text check that holds back items with links, shell commands or "ignore the instructions above" for a moderator comes later.
Reports and moderation
Not built yet. Once it is, every item gets a Report button, and moderators can unpublish or remove an item. A removed checklist already drops out of every run.
Limits on publishing
An account publishes at most 5 times a minute, and the person publishing needs a GitHub account at least 30 days old.
Last updated on