Skip to content
Gittensory
Workflows

Maintainer workflow

The default posture is silence. You opt into context. The repo stays calm.

The mirrored loop

Each step on the right is what you see in the repo; the matching step on the left is what the contributor is doing privately via MCP at the same point.

New installations should start with self-hosting setup, then GitHub App configuration: install on one repo, verify installation health, preview the public panel, then decide whether Gittensory Orb Review Agent should become a required check.

Miner
What the contributor does
Maintainer
What the repo owner sees
  1. Plan
    The contributor pulls a private decision pack via MCP — lane fit, repo targets, ranked next actions. Nothing is posted to your repo.What miners see
    Plan
    Default posture is silence. No always-on public check runs, no score numbers, no labels on non-confirmed-miner PRs.Privacy boundary
  2. Analyze
    Metadata-only branch analysis runs locally. Source code stays on the contributor's machine.Branch analysis reference
    Analyze
    On confirmed-miner PRs, request the maintainer packet on demand — no background scanning of your repo.
    GET /v1/repos/:owner/:repo/pulls/:number/maintainer-packet
    http
    Maintainer packet API
  3. Preflight
    The contributor sees branch blockers, account/queue blockers, and maintainer-fit notes before opening the PR.Common blockers
    Preflight
    You can ask for the same reviewability view in the PR thread.
    @gittensory preflight
@gittensory blockers
@gittensory duplicate-check
    Upstream drift
  4. Packet
    The contributor opens the PR with a public-safe packet — clean description, no private scoring language.PR packet format
    Packet
    At most one sticky sanitized comment and one configured label per confirmed-miner PR. Pull richer context on demand via the API.
    GET /v1/repos/:owner/:repo/pulls/:number/reviewability
GET /v1/repos/:owner/:repo/registration-readiness
    http
    Self-host reviews
See the contributor sideSelf-host reviews

On-demand commands

By default, the public commands below are authorized for maintainers, collaborators, and confirmed miners (not the general public) — output stays scoped to maintainer-visible packets when appropriate. A repo can narrow this per command via commandAuthorization in its settings.

@gittensory help
@gittensory ask
@gittensory preflight
@gittensory blockers
@gittensory duplicate-check
@gittensory miner-context
@gittensory next-action
@gittensory reviewability
@gittensory repo-fit
@gittensory packet

A separate maintainer-only queue-digest family defaults to maintainers and collaborators only:

@gittensory queue-summary
@gittensory confirmed-miners
@gittensory review-now
@gittensory needs-author
@gittensory duplicate-clusters
@gittensory burden-forecast
@gittensory intake-health
@gittensory outcome-patterns
@gittensory noise-report
Public-facing comments are sanitized before they leave the Worker. Private scoring, reward, and risk language never appears in the PR thread.
← PreviousGitHub App configurationNext →Maintainer install & trust