Axon Shaft docs

Runs, automations and the audit log

The Runs list, usage and each run's page, how automations and templates work, the audit log, and the notifications the dashboard shows.

Runs

The account's Runs page and each project's Runs page list the runs, newest first. Each row shows the status or verdict, the project, the commit with a link to the run on GitHub, the trigger, the findings, the tokens (with the cost of a run on an API key, on hover), how long it took and when it started. The list reads again every 10 seconds while a run is still going.

The list ends with a line about older runs. Runs older than 7 days are on GitHub: a project's list links to the repo's Axon Shaft workflow (https://github.com/<owner>/<repo>/actions/workflows/shaft.yml), and the account's list links to each project's. PR comments and check runs stay with the pull request. Workflow logs follow the repo's own retention setting, 90 days by default.

Usage

Usage sits above the list on both Runs pages. Pick a range: Today (since midnight UTC), 7 days (the default), 1 month or 3 months.

  • Every range shows the runs, how many passed, were blocking or failed (a cancelled run counts as failed), the tokens, and the approximate cost of runs on an API key.
  • Today and 7 days also show the findings by severity, the findings per checklist and the total review time. They come from the runs themselves, which are kept for 7 days.
  • 1 month and 3 months come from daily totals, which keep only those numbers, for 3 months.

The last line is the lifetime total, such as "Lifetime: 1,284 runs · 172M tokens · $412.37 since Nov 17, 2026". On the account's page it adds up every project you see, and only the account's admins see the cost. On a project's page anyone who sees its runs sees the cost too, as each run's row already shows it. A run counts in the daily and lifetime totals once it finishes.

A run's page

A run's page shows its status, automation, commit, trigger, model, effort, tokens, duration and start time, with links to the pull request comment and the Actions log.

  • A finished review shows its card: the headline, what the change does, a chip for each checklist, the findings by severity with file:line linked to the reviewed commit, and what it didn't check.
  • A finished /ask or /fix shows its reply as it was posted. A reply has no verdict, so its status reads Done.
  • A failed run shows its error card and message at the top, with the code from Failure, notice and skip codes.
  • The card's headline, findings and what it didn't check, and a reply, show their Markdown formatted as GitHub does: lists, code, tables and links, each link opening in a new tab. Only web and email links are links, any HTML in them shows as text, and an image from another site shows as a link to it, so the page never loads it.

Under them is the run's log from GitHub: the job's steps while it runs, then the whole log, with each group folded except the review. The log stays on GitHub, and the page reads it with your GitHub sign-in when you open it. A log GitHub no longer keeps shows as expired.

A run is deleted 7 days after it started, with its findings, card or reply, tokens and error. Its workflow run, pull request comment and check runs stay on GitHub, and the runs list links to the repo's Axon Shaft workflow there. See Data flow.

Automations

An automation is something Axon Shaft does on the repo by itself when something happens there. The Automations tab groups them by what starts them: on pull requests, when someone comments /ask, when someone comments /fix, and on new issues.

  • Every project starts with Code review, Reply and Task, all on.
  • Only the first review automation that's on runs. Another review that's on reads "Paused: <name> runs instead".
  • Each automation's menu edits, duplicates, renames, resets it to its template, or removes it. Its own page can also change its template.
  • Add automation opens the templates. A template that needs something not built yet says Coming soon, Connect Jira or Connect Linear, and can't be added.

One automation's page

The page has four sections, each with its own Save. A sentence at the top says when it runs and what it does, and changes as you edit.

  • When it runs. For a review: the pull request events, what it does with forks, outside contributors, bots and Axon Shaft's own pull requests, the target branches, and the skip labels. See Code review options.
  • What it looks for. For a review: the depth, then its checklists in order, each with a switch and up to 500 characters of your own rules, your own checks, and your own instructions.
  • What it posts. Reviews only: where nits go, and whether the summary has a walkthrough.
  • Model. The model and effort for this automation alone.

Recent runs lists its last five runs. The danger zone resets it to its template, which puts back the template's checklists in its order, or removes it.

A checklist you add yourself, from Add a checklist or from the Marketplace, is marked Added by you.

Changing an automation's template

Change template, in the automation's menu or beside "Based on", moves it to another template of the same kind. So does Apply to an automation on a template's page in the Marketplace. Its name, options and instructions stay as they are, and its checklists become the new template's.

When the automation has checklists its template didn't list, or checks of your own, the dialog lists them and you choose:

  • Keep them and switch: the new template's checklists come first, then yours, each with its switch and rules as they were, then your own checks.
  • Reset to the new template: you get the new template's checklists and nothing else.

A kept checklist that the new template lists too stays in the list, greyed out and marked Already in the template. The template's own entry is the one that runs. It isn't deleted: if you change the template again to one without it, it runs again as one you added.

Marketplace

The Marketplace, in the sidebar, has three tabs: Templates, Checklists and My items. Templates and Checklists each have a search box, a sort and chips to filter by, and Show (All, Built-in or Community) once community items are listed. Built-in items show Axon Shaft as the publisher, with a verified mark. A community item shows its publisher as @account, with its version, and a community checklist's card shows how many projects use it.

  • Templates lists every template. A card shows what the template is for, when it runs, its tags and the projects you manage that already have it, with Use template, Coming soon or Connect Jira. A template's page has Add to a project, and Apply to an automation, which moves one of your automations to it. The chips filter by category, and the sort is Suggested, Most used (on your projects) or A to Z.
  • Checklists lists the checklist catalog. Add on a built-in checklist's card, or Add to an automation on its page, adds it to the end of one of your review automations. A card shows how the checklist runs (Model, Script, or Script and model), the first two things it catches, the kinds of project it suits, the files it runs on and how many templates list it. The chips filter by kind of project, and the sort is Suggested, In most templates or A to Z.

A checklist's page shows its publisher, version and how it runs, what it checks with a sample finding, the files it applies to, when it skips, the kinds of project it suits, its script and the templates it's used in. It doesn't show a built-in checklist's rules, which only the model gets at run time. A community checklist's page shows all six of its rules, its author linked to their profile, how many projects use it, what changed in its latest version, and every version with its notes. A community template's page shows its author, version, uses and versions too.

The docs have the same catalog, with each checklist's check run name: Templates and the Checklist catalog.

My items lists the community checklists and templates of each of your accounts, drafts and published, newest change first. Each row shows the item's key, status, version and when it last changed, and the item it was forked from, if any. The account's admin can edit, publish and unpublish them.

Using a community checklist or template

Community checklists run only in reviews. To use one, open it and choose Add to an automation, or choose Add a checklist on a review automation's page, where community checklists are listed with their publisher. Either way it's added at the version you saw. Each row in the automation's list shows the checklist's publisher and pinned version.

To start from a community template, open it and choose Add to a project. The new review is based on Code review, with the template's name, options and checklists, its community ones at the versions the template pins. A later version of the template doesn't change it, and resetting it goes back to Code review.

When the author publishes a new version of a checklist you use, its row shows Version n available. Choose it to see what changed in each version's notes, and every rule and path that differs from the version you run. Approve version n saves the automation with the new version. Until you approve, it keeps running the old one. If the author unpublishes it, your automation keeps running its version and the row says Unpublished by the author, but no other automation can add it. Community items has how they're kept safe.

Publishing a checklist or template

Create, at the top of the Marketplace, makes a community checklist or template. You see it if you can publish for an account: your personal account, or an organization where you're an admin. Pick what to make and, if you can publish for more than one account, which account publishes it. The dialog then walks through that kind's steps and checks each one before the next.

A checklist has five steps:

  1. Basics: its name, its slug, a one-sentence summary for its card, and the kinds of project it suits. The slug follows the name until you change it, and the checklist is published as @account/slug. Once the item is saved, the slug can't change.
  2. Where it runs: the files it applies to and the files it leaves out, as globs. A box under them tries the globs on paths you type and says which would run. When none of a pull request's changed files match, the checklist doesn't run.
  3. Rules: the six rules the model gets for it: what it looks at, what counts as a finding, what it never flags, what a finding cites, what's blocking and what should be fixed. Each has a line on what to write and an example.
  4. Preview: the checklist's step in the review prompt, word for word.
  5. Visibility and publish: who can see it once it's published, and what changed in this version.

A template has four: Basics (its name, slug and description), Checklists (built-in checklists, in the order reviews run them), Options (the review options an automation has, starting from Code review's), and Visibility and publish.

Save draft keeps the item on the account without publishing it, and only the account can see a draft. Publish makes it the next version (1, 2 and so on), which never changes after. Everything published is public, with every rule, so anyone can read it before they use it, and a personal account's published items are always public. Private items, which only the account could see and use, carry the Organization plan marker and aren't available yet.

In My items, Edit opens the same steps on the item's draft, or on its newest version when it has no draft. Saving an edit to a published item makes a draft, and the published version stays as it is until you publish again. Publish asks what changed and makes the next version. On an unpublished item with no draft, it lists the item again as it was. Unpublish takes the item out of the Marketplace, and anyone already using a version keeps it.

To publish, your GitHub account has to be at least 30 days old, and an account can publish at most 5 times a minute.

Forking a checklist

Fork, on a community checklist's page, copies its newest version into a draft on one of your accounts, under a slug you choose. The draft shows in My items with the checklist and version it came from, and you can edit and publish it as your own. Built-in checklists can't be forked, since their rules stay hidden.

Audit log

The audit log is in the account's settings, for the account's admin only. It lists who changed what on the account and its projects, removed projects included, newest first, 50 at a time:

EntryWhen
Added, removed, paused or resumed the projectAdd project, Remove, and the Danger zone
Added, changed, removed or reset a jobChanges to an automation, with the fields that changed
Saved or deleted the Claude tokenThe account's or a project's token card
Changed settingsAny settings card, with the settings that changed
Added the workflow file, or opened a pull request for itThe Add the workflow, Workflow needs an update and New action version cards
Made, forked, changed, published or unpublished a community itemCreate, Fork, Edit, Publish and Unpublish in the Marketplace

Each entry names the person, the project and the fields that changed. It never shows a value: a token, a rule or a setting's new value isn't recorded. An entry is deleted once it's 3 months old.

Commands, labels and pull request comments happen on GitHub, so GitHub's own timeline records them, not the audit log. See Overrides and audit.

Notifications

The dashboard doesn't send email. It shows:

  • the bell at the bottom of the sidebar, which for the account's admin, or for someone whose org role shows as Role unknown, lists "AxonShaft has new permissions to review" when the installation hasn't approved everything the app asks for. Otherwise it's empty;
  • Alerts on the account's page and a bar over each project page, with the same permissions to review;
  • a bar that says "A new version is ready." with a Reload button, when the dashboard has been updated since the page loaded.

On the pull request, GitHub's own notifications cover the summary comment, which is posted once and then edited, so GitHub emails people on the pull request once.

Last updated on