magus v0.4.2 is out. See what's new
¶ View markdown source · ✎ Suggest an edit
3 min read

Agent skills

These are the skills magus agent install writes, reproduced verbatim from the bodies embedded in the binary. Each ships in two hand-authored permutations, and install writes both: the short form is the always-loaded primary, and the full form is its <name>-full twin, loaded by name when a reader needs the rationale. See Skills for the difference.

skill full short saved what it is for
magus-architecture-review 6322 5123 18% Ground refactoring and structure proposals in the magus knowledge graph instead of intuition.
magus-buzz-review 20279 15155 25% Review Buzz code - a magusfile, a spell, or a standalone .buzz script - across three lenses run in parallel: idiom/style, skeptic/correctness, and upstream-Buzz conformance.
magus-buzz-write 8174 6776 17% Write and run Buzz, the language magusfiles, spells, and magus buzz scripts are written in.
magus-change-summary 7051 5385 23% Summarize what changed in a magus workspace, write it up, or answer a granular diff question.
magus-commit-composition 4448 3840 13% Restructure an UNPUSHED branch so each commit is one reviewable idea, using the workspace's own boundaries (project ownership, declared outputs, blast radius) rather than guessing from paths.
magus-context-audit 5846 4187 28% Audit the instructions an agent was given - the repo instruction file, installed skills, handoff-journal entries, a routing index, hook-injected text, and any user-level instruction file - for statements that contradict each other or that no longer match what the tools do.
magus-docs-lookup 3670 2956 19% Traverse magus's own documentation to answer a "how does magus do X / what does Y mean / where is Z documented" question, instead of guessing an answer or a URL.
magus-handoff-journal 5590 4625 17% Maintain a user-owned handoff journal through magus_memory or magus memory: named decisions, plans, pointers, and the hypotheses an investigation ruled out, all surviving worktrees and sessions.
magus-multi-agent 21840 16102 26% Split work across agents in a magus workspace as an acceptance-criteria loop: partition by WRITE SET using graph evidence (magus refs --occurrences, explain, affected --plan --stdin), prove the leases cannot collide, bound fan-out depth, and match each lease's model to the work it needs.
magus-query 13065 10541 19% Query the magus knowledge graph to find and relate entities (projects, targets, spells, ops, charms, modules, diagnostics, docs).
magus-run 11157 7393 33% Run builds, tests, lints, and codegen through magus targets.
magus-sdk 13317 12880 3% Help a Go developer consume magus as a library (import "github.com/egladman/magus") instead of shelling out to the CLI, and audit whether the SDK actually serves them.
magus-vcs-hygiene 8132 5992 26% Safe git operations in a magus workspace (any repo with magusfile.buzz at the root).
magus-workspace-rules 5435 4391 19% Adapt magus's installed agent surface to THIS workspace without breaking it.
all 14 134326 105346 21%
agentsskillsreference
Last updated (77dde07d)
Earlier changes on this page (7)

Full history ↗ · Blame source ↗

Glossary

Workspace

The magus root directory that owns a set of projects and shared config; the unit magus operates over. See workspace.

Project

A directory magus recognizes as a unit of work (it has a magusfile); the unit of caching, scheduling, and dependency tracking. See workspace.

Magusfile

The magusfile.buzz that declares a project's targets (as export funs) and binds its spells. See targets.

Target

A named operation (build, test, ...) you invoke with magus run <target>; it may compose a spell's tool-native operations and depend on other targets. See targets.

Op

A single tool-native command a target composes (long form: operation); the middle of the work hierarchy (Spell to Op to Target). See operations.

Spell

A language/runtime adapter (e.g. go, md) that maps generic targets onto a toolchain's real commands. See spells.

Charm

An execution modifier attached with : (lint:rw) that changes how a target runs, not which one; the built-in rw flips a check-only target to mutate in place, and ci always strips it. See charms.

Module

A magus stdlib namespace a magusfile imports for host capabilities: filesystem, exec, vcs, and more. See the module reference.

Buzz

The language magusfiles are written in (the .buzz engine). See engines.

Affected

The set of projects touched by a change; magus affected <target> runs a target only over them. See affected.

CI

An ordinary magusfile-defined target you compose yourself with magus\needs - magus does not hardcode its stages. Magus.RunCI treats it specially only in that it strips the rw charm, it is the anchor magus affected ci keys off, and a selected scope with no project declaring it is a load error rather than a silent no-op. See targets.

Knowledge graph

The queryable graph of a workspace's spells, targets, docs, and code relationships; query it with magus query/explain/path. See knowledge.

Ownership

An insight lens: author concentration - the primary author and their share, the distinct-author count (the bus factor), and abandonment. See insight.

Session

One magus process's recorded facts - the targets it finished, their outcomes, and the lease it acted as - kept in a repo-scoped store every worktree shares. magus session lists them; the store prunes itself by last-fact age.

Lease

One row of the lease ledger: a piece of work an orchestrating agent handed out, with its goal, the checkpoint it was cut against, and the paths it owns or must not touch. The ledger records; the agent guard is what reads those facts back when grading a write. See doctrine.

Conventions

Placeholders

Angle brackets mark a value you replace with your own - never type the brackets:

magus run <target>
magus completion <shell>    # e.g. bash, zsh, fish

<target>, <path>, <shell>, <name> and the like are stand-ins, not literal text.