Core concepts
Branch analysis
Gittensory analyzes branches using metadata only. Your source code never leaves your machine.
Inputs
- Repository identity (owner/repo).
- Branch, base, and head refs.
- Changed-file metadata — paths, sizes, line counts.
- Labels and linked issues.
- Commit messages.
- Validation summaries (lint/test outcomes, not logs).
- Optional local scorer output.
- User-supplied scenario assumptions.
Outputs
- Lane context (maintainer / contributor / hybrid).
- Role context for your account.
- Scoreability scenarios (see Scoreability).
- Branch blockers and account/queue blockers.
- Maintainer-fit notes.
- Public-safe PR packet preview.
- Ranked next actions.
Example invocation
POST /v1/local/branch-analysis
Authorization: Bearer ••••••••
Content-Type: application/json
{
"repo": { "owner": "entrius", "repo": "gittensor" },
"refs": { "base": "main", "head": "feat/scorer-cleanup" },
"files": [ { "path": "src/scorer.ts", "added": 42, "removed": 8 } ],
"labels": ["scorer", "ready-for-review"],
"linked_issues": [421],
"commits": ["refactor scorer gating", "fix linked-issue projection"]
}httpFile metadata is allowed (path, line counts). File contents are not requested, accepted, or stored. The MCP enforces this on the client.