magus v0.4.3 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 forms, 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.

magus-architecture-reviewGround refactoring and structure proposals in the magus knowledge graph instead of intuition.5.5 KB short, 6.7 KB full - 18% shorter magus-buzz-langWrite, fix and debug Buzz, the statically typed language of magusfile.buzz, spells and `magus buzz` scripts.10.2 KB short, 12.4 KB full - 17% shorter magus-buzz-reviewReview 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.15.0 KB short, 20.2 KB full - 25% shorter magus-change-summarySummarize what changed in a magus workspace, write it up, or answer a granular diff question.5.5 KB short, 7.1 KB full - 22% shorter magus-commit-compositionRestructure 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.3.7 KB short, 4.3 KB full - 13% shorter magus-context-auditAudit the instructions an agent was given - the repo instruction file, installed skills, memory 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.4.1 KB short, 5.7 KB full - 28% shorter magus-diagramWrite, check and view an architecture figure with magus/figure, the embedded Buzz module: boxes built from the knowledge graph's own Dir records, groups over a declared layer or a dirs set, edges derived from imports and declared calls, and a layout nobody places by hand.7.1 KB short, 7.8 KB full - 9% shorter magus-docs-lookupTraverse 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.3.3 KB short, 4.2 KB full - 19% shorter magus-multi-agentLoad BEFORE your first subagent spawn in a magus workspace: an Agent or Task tool call, a background worker, parallel workers, fanning out, or delegating part of a task.30.9 KB short, 40.0 KB full - 22% shorter magus-queryQuery the magus knowledge graph to find and relate entities (projects, targets, spells, ops, charms, modules, diagnostics, docs).12.0 KB short, 14.7 KB full - 18% shorter magus-runRun builds, tests, lints, and codegen through magus targets.9.1 KB short, 13.3 KB full - 31% shorter magus-sdkHelp 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.12.5 KB short, 12.9 KB full - 3% shorter magus-test-designChoose unit, integration, or end-to-end test boundaries from the magus graph and runtime behavior.6.5 KB short, 10.3 KB full - 36% shorter magus-vcs-hygieneSafe version-control operations in a magus workspace (any repo with magusfile.buzz at the root).7.0 KB short, 9.7 KB full - 27% shorter magus-workspace-rulesAdapt magus's installed agent surface to THIS workspace without breaking it.8.6 KB short, 10.8 KB full - 19% shorter

All 15 together are 141.1 KB installed as the short form, against 180.1 KB for the full twins: 21% less always-loaded text.

agentsskillsreference
Last updated (895d94e4)
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.

Span

OpenTelemetry's name for one unit of work under a trace: a target execution, whose sub-operations are child spans. An output reference points at a span's captured output. See telemetry.

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 for author concentration: the primary author and their share, the distinct-author count (the bus factor), and abandonment. See insight.

Run

One target executing under one magus invocation, such as magus run test web or magus affected ci. A run keeps its captured output behind an output reference. Every magus run is a run whether or not any job asked for it; see Job for how the two relate.

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.