anchor

Git/forge skills for consistent and effective source control.

End-user docs: https://chris-peterson.github.io/anchor

An anchor holds a vessel fast against drift. Here it holds work fast: it takes work-in-progress (tracked by tack), runs it through review (moor), and sets it down in source control — committed, described, and opened for review on the forge.

Repo layout

.claude-plugin/plugin.json   plugin manifest
skills/commit/               /anchor:commit — stage, test, review, write the commit message (--preview reviews the working tree without committing)
skills/prepare-review/       /anchor:prepare-review — rebase, draft the CR description, open/update the CR
skills/resolve-feedback/     /anchor:resolve-feedback — fetch CR feedback; fix / reply / resolve each thread to resolution
skills/pipeline/             /anchor:pipeline — work with a commit's forge pipeline; report state or watch until it settles
skills/issue/                /anchor:issue — gather the why/consumer/acceptance; draft and file (or update) a forge issue
rules/                       ambient rules a SessionStart hook injects into every session
hooks/emit-rules.sh          the injecting hook (registered in hooks/hooks.json)
scripts/review-diff.sh       launch the configured difftool through its review sidecar; print the verdict on stdout
scripts/pipeline-status.sh   resolve / watch a commit's pipeline on the forge; print a normalized verdict on stdout
scripts/look-ahead.sh        unpushed-commit count (bash-analyzer-safe helper)
guides/                      load-bearing reference the skills/rules read at runtime (configuring, forge cookbook, description-vs-docs, changeset-scope)
templates/                   the output shapes the skills produce (commit-message, cr-description, issue-description), read at runtime
docs/                        end-user docs site (docsify, GitHub Pages); skills/, rules/, guides/, templates/ are rendered in

Optional integrations

The skills work standalone and light up further when these siblings are installed (each degrades gracefully when absent):

• [moor](https://github.com/chris-peterson/moor) — the visual diff viewer the

commit skill launches (including --preview). Absent → it falls back to git difftool --dir-diff with your configured difftool, asking whether to revise or proceed in place of moor's rejected-hunk feedback.

• [tack](https://github.com/chris-peterson/tack) — the WIP route tracker. Absent

→ CR-to-tack linking is skipped silently.

Try the plugin locally

claude --plugin-dir .

Launches Claude Code with the working tree mounted as a plugin, so /anchor:commit and /anchor:prepare-review resolve.

Docs

just docs

Runs scripts/copy-skill-docs.sh (syncs each SKILL.md and guide into docs/) and serves the docsify site locally. Deployed to GitHub Pages on push to main via .github/workflows/deploy-docs.yml.

License

MIT