Code + review
DJINN + GitHub
DJINN writes code in a sandbox clone, has it reviewed by a different model family, and opens a pull request. It does not merge its own work.
How it connects
Sandbox only, never the live tree
Writes happen in a separate clone. The running checkout and the process manager are off-limits, enforced at the tool layer rather than by instruction.
Cross-model review is the gate
Code written by one model family is reviewed by another, and a bare pass is not enough — the findings have to be clean. Our last two organs took seven and two rounds to get there.
A watcher reviews every PR again
A scheduled job re-reviews open PRs with new commits, so two independent model families see every change.
Repo activity digest
A weekday summary of commits, PRs and review state into Slack.
Connector spec
- Auth
- oauth2 · github_v1
- Host
- https://api.github.com
Scopes requested
GET repos/${source.full_name}/issues
Emits issue · incremental on updated_at · link_header pagination
Declared boundary: per record via repos/${source.full_name}/collaborators/${user.handle}
GET repos/${source.full_name}/pulls/comments
Emits pr_review_comment · incremental on updated_at · link_header pagination
Declared boundary: per record via repos/${source.full_name}/collaborators/${user.handle}
This spec parses and validates, and it has not been run against a live GitHub account. Sigil fetches and paginates today; it does not yet apply the mapping or enforce the boundary shown here. Both are declared and checked for shape, not executed.
Worth knowing before you wire it
The unauthenticated API allows 60 requests an hour, which a single scan exhausts. A token with no scopes at all raises that to 5,000 — public reads need no permissions.
Documents
GitHub setup and reference.
Setup steps, scopes, and the policy boundaries that govern this connector. Sent by email — leave an address and we send them manually, same as the handbook.
- RunbookThe build → review → merge loop
- PolicySandbox boundaries
- ReferenceReview verdicts and merge criteria
Want GitHub wired into your own company brain?