EXTENSIONS

One workflow, `@dataverket/mirror-forgejo-to-github`, that mirrors every repository of a Forgejo org to a GitHub org and keeps it that way.

Full Azure DevOps API coverage: Git, pipelines, work items and more. Works with Azure DevOps Services, legacy visualstudio.com URLs and Server/on-prem.

SOPS + age vault for swamp: one encrypted file per secret.

GitHub repositories, releases, pull requests and repository settings for swamp, over the REST API. One model type, `@dataverket/github`.

Forgejo (or Gitea) administration for swamp over the /api/v1 REST API with a scoped access token, in one model type, `@dataverket/forgejo`.

Drive pull requests on a Forgejo or Gitea forge: list and read them,

Record a Forgejo or Gitea branch's commits and head over time.

Git repository operations for swamp workflows. Wraps the git CLI

Headless agent dispatch as a swamp behavior: filter the bd ready queue into a typed manifest, branch a target checkout and run one agent on a task, sweep every candidate under a single behavior lock, or run a single agent with no git work at all (`run`). Other extensions call `run` through runModel so there is one authority on how a headless agent is launched. Replaces the .kilo/agents ready-queue.sh / run-task.sh / bd-sweep.sh shell cluster.

Generic, portable housekeeping sweep for any checkout. A read-only audit of dirty trees, diverged or deleted branches, forgotten stashes, stale worktrees, flat sibling clones, temp debris, leftover processes, disk pressure, and stuck tracker claims, plus explicitly-gated cleanup methods that dry-run by default. Project-agnostic: projectDir defaults to `.`, with .beads/ and .swamp/ awareness layered on when present.

Make sure a GitHub repository exists, list a user's or organization's repositories newest first, and keep local source checkouts or mirrors of them up to date, syncing only what changed since last time and keeping force-pushed history in backup refs. Uses the GitHub CLI's existing login, so no token goes in a vault.

Read and write GitLab data via GraphQL (REST fallback for branches and

Exact-state engineering handoffs. Captures a deterministic, secret-free snapshot of Git worktree state plus the authoritative active Bead, records the narrative (goal, scope, commands, decisions, next safe step, forbidden operations), and writes a queryable handoff resource and a markdown report.

Code-reading methods for @shrug/forgejo — map a repository's file tree, read individual files, and snapshot every matching text file into one reviewable data blob. Turns a metadata-only forge node into a source for code review and IaC analysis.

Query GitHub data using the gh CLI for repository, PR, issue, release, and workflow visibility.

Validates a caller-supplied parsed test result for internal consistency and a recognized multi-language test-runner command, then commit-pins the evidence to an immutable Git commit and branch, returning a single pass/fail verdict.

Composition lifecycle for a Graphite (gt) multi-PR stack — validate a declared linear plan, finalize one-commit units, cascade restacks, pin a composed head, and submit gated, idempotent, ordered draft PRs.

Submit an already-validated Git commit as a draft GitHub pull request using the Graphite CLI, then independently verify with the GitHub CLI that the pull request points at the validated SHA, branch and base and is a draft.

Administration of a Forgejo (or Gitea) server over its /api/v1 REST API, authenticated with a scoped access token. Find or create organizations and repositories and update their settings; run GitHub pull-mirrors (create via /repos/migrate, reconcile interval, visibility and description, queue immediate syncs); audit every mirror's sync health; manage pull requests (open, inspect mergeability and head CI state, merge); and audit or repoint repository webhooks so a hook pointing at an old CI target is reported. Changes are find-or-create or reversible (archive/unarchive), except the guarded pr_merge. There are no delete methods: an empty repository left by a failed migration is reported, not deleted. Secrets are never output: mirror source credentials are write-only, and webhook operations neither read nor write the hook secret.

Drive [Forgejo](https://forgejo.org/) and [Gitea](https://gitea.io/) instances

Forge-neutral immutable change packets for reviewed repository delivery. Records exact Git base/head identity, validation evidence, requested draft submission metadata, a canonical SHA-256 digest, and derived readiness. Performs no network, Git, forge, approval, merge, or release operation.

Local git operations model — clone, branch, read, commit, push, rebase. Designed for agent-driven development workflows where code changes are authored locally and pushed to a remote forge. Supports a configurable workspace layout (default: $HOME/{host}/{group}/{project}) and commit message format enforcement.

Structured git comparison — produces per-file diffs between refs and auto-discovers structural patterns to flag deviations in new code. Two methods: diff (structured breakdown) and check (pattern-based review with ready-to-post markdown comments).

List GitHub pull requests via the gh CLI from swamp workflows.