Workbooks + GitHub

Connecting GitHub would let a workbook's agent do the repo work it already reaches for — branch, commit, open a pull request, file and triage issues — against a real GitHub repository, with the token held by the host. The local half (everything git can do) ships today; the GitHub-API half is the planned extension.

Field	Value
Toolkit id	`github` (planned) · `git` (ships today)
#+EXEC shape	`command`
Backing CLI	`git` (+ `gh` / GitHub API, planned)
Status	`north-star` (git: `stable`)
Manifest	`toolkits/git/manifest.org`

What it does

Shipping today (via the git toolkit):

Branch, commit, rebase without losing work, recover a detached HEAD, undo a commit safely, bisect, cherry-pick — end-to-end recipes in toolkits/git/skills/.

Planned (the GitHub integration proper):

Open and update pull requests.
File, comment on, and close issues.
Read PR/issue state to drive an agent's plan.

Capabilities it grants

Capability	Why it needs it
`vfs`	Read / write the repo working tree
`posix`	Run the `git` binary (`git/manifest.org:4`, `CLI_BIN: git`)
`net`	Push / fetch; reach the GitHub API (planned)
`secrets`	The GitHub token the host holds (planned)

See Dock capabilities.

How to add it

The intended flow:

Set the GitHub token as a host secret (the toolkit never sees it):
```
   wbx secret set GITHUB_TOKEN <token>
```
Add the toolkit:
```
   wbx toolkit add github
```

Today, for local repo work, reference the git toolkit and read its skills on demand (see the skill index in toolkits/git/manifest.org).

GitHub action across the Dock and never sees the credential.

Worked example

Local, shipping today — rebase a feature branch onto updated main using the toolkit's recipe (no training-data guesswork):

# agent reads toolkits/git/skills/rebase-without-losing-work
git fetch origin
git rebase origin/main
# conflicts resolved per the recipe, then:
git push --force-with-lease

Planned — once the GitHub integration ships, the same agent would then open a PR:

wbx github pr open --base main --title "..."   # planned

Related toolkits

Workbooks + Linear — issue tracking sync (toolkits/linear/)
Workbooks + Slack — notify a channel on a PR/issue event (slack)
Build: Authoring skills (how the git recipes are structured)
All integrations: Toolkits & integrations

Maturity

north-star for the GitHub-API integration; the local git toolkit is stable and ships today (toolkits/git/manifest.org). The honest split: an agent can do everything local git does right now via that toolkit's verbatim recipes; the GitHub-side actions (PRs, issues, API) are the documented next step, not a present capability. No present-tense claim is made for the unbuilt half.

Capability Matrix row: /maturity
Source of truth (shipping half): toolkits/git/manifest.org