Skip to content
user

github

GitHub source → canonical repository work.

2 skills 1 human gate 5–15 min/session
Install this pack Read the reference

The contract

Use it when
You want to start repository work from a GitHub Issue, Milestone, or selection, or compare an existing tracker-origin artifact.
You type
Start repository work from GitHub Milestone 12.
You provide
A trusted configured repository plus an Issue, Milestone, selection, or registered artifact path.
You receive
A bounded content-based route or field-level refresh delta, with an exact preview before any supported coordination write.

Where you decide

The agent pauses at these points. You choose whether to continue, redirect, or stop.

Review the repository routeDecision 1 of 2Confirm one GitHub coordination actionDecision 2 of 2

What changes when you install this

After installing this pack, the skills and agents it provides are available in every session on the relevant scope.

The journey

Say this What happens
Intake GitHub issue 123 as repository work. Start read-only. Bounded acquisition, strict normalization, and content-based routing
Refresh docs/specs/example/spec.md from its registered GitHub source. Field-level comparison under the artifact’s lifecycle and authority

1. Acquire and route

  • You provide: the Issue, Milestone, or explicit selection.
  • Agent does: runs fixed-host approved gh reads, validates provenance, and delegates normalized content to work-intake.
  • You decide: resolve any coherence, evidence, or confidentiality gap.
  • Output: artifact path and kind, lifecycle membership, processor, authority mode, dispatchability, and one next action.
  • State: read-only

2. Materialize repository work

  • Agent does: work-intake writes the selected canonical artifact, then registers it before processor dispatch.
  • You decide: continue with the named processor or stop with a Draft.
  • Output: durable repo-local work. GitHub remains unchanged.
  • State: confirmed-write

3. Refresh or coordinate later

  • You provide: the existing registered tracker-origin artifact to compare.
  • Agent does: presents field decisions. A remote coordination action is a separate request with a fresh confirmation and pending receipt.
  • You decide: approve local fields, then confirm one exact remote action.
  • Output: reviewed local authority state and, when confirmed, one bounded GitHub coordination result.
  • State: confirmed-write

Human gates

For each gate, everything you need to make a confident decision.

  • Review the repository route

    Trigger
    After intake returns an artifact, lifecycle membership, processor, authority mode, and named gaps
    Time
    1–5 minutes
    What to check, good, bad, consequence

    What to check

    • Does the content support this artifact rather than relying on Issue or Milestone type?
    • Is the destination repository and confidentiality boundary correct?

    What good looks like

    One coherent route, or an explicit non-dispatchable gap when the selection is not coherent.

    What bad looks like

    A Milestone forced into a brief or an Issue forced into a spec because of its object name.

    Consequence of skipping

    A wrong route creates the wrong durable artifact before delivery begins.

  • Confirm one GitHub coordination action

    Trigger
    After the exact action, target, and payload digest are shown
    Time
    1–2 minutes
    What to check, good, bad, consequence

    What to check

    • Is the target the registered Issue?
    • Is this only a declared coordination action, not a requirement rewrite?

    What good looks like

    One trace link, pull-request link, display-status label, comment, or closure bound to a fresh confirmation.

    What bad looks like

    A generic update, Issue-body rewrite, or reused confirmation.

    Consequence of skipping

    The wrong remote Issue may be changed and automatic retry is unavailable.

Typical session

Agent turns
3–6
Human gates
1
Wall-clock time
5–15 min

Install

agentbundle install --pack github --scope user

Skills in this pack

  • github-brief-intake1 gate

    Acquires bounded Issue or Milestone data through fixed-host approved gh reads and delegates strict normalized content to work-intake.

  • github-refresh1 gate

    Compares a registered tracker-origin artifact and performs only profile-declared coordination actions after exact confirmation.

Technical reference & next steps