Publish a pack for a stack¶
Share what agents should know about one language, framework or platform, for anyone to turn on.
1. Pick a name you can publish¶
Publish the pack under your GitHub handle, with a prefix that starts with it. Names that look like an official pack's or use a vendor's name are refused (naming):
brainrc new pack jdoe-elixir --id jdoe/elixir --prefix jdoe-elixir-
2. Write one domain skill per stack¶
A domain skill has four sections: how to validate offline, conventions, a review checklist, and
what never to do without approval. Its description says when to load it. The
tutorial writes one in full.
3. Tell Gatework which files load it¶
[[extensions.gatework.domains]]
files = "`*.ex`, `*.exs`, `mix.exs`"
skills = ["jdoe-elixir-phoenix"]
reviewer = "brainrc-code-reviewer" # optional: the agent that reviews these files
4. Say which brainrc versions it works with¶
new pack pins requires_core to the minor series you ran it with, and its CI workflow and
pre-commit hook to that release's tag. When you test against a newer brainrc, move all three
together (compatibility).
5. Release it¶
Tag a release, and tell people to pin the tag:
[jdoe-elixir]
git = "https://github.com/jdoe/elixir-pack.git"
ref = "v1.0.0"
A domain skill everyone should get can go into Gatework itself instead: open a pull request on
brainrc/gatework with the skill in skills/<stack>/ and a
row in its Domains table.