Gittensory

Appearance

For Miners ​

Gittensory helps miners decide what to do next with evidence instead of guesswork.

What It Answers ​

  • Is this repo a direct-PR lane, issue-discovery lane, split lane, inactive lane, or unknown lane?
  • Am I in a normal contributor lane or a maintainer lane for this repo?
  • Does my current branch look reviewable?
  • What blocks scoreability right now?
  • Should I clean up open PRs before opening more work?
  • Is there duplicate or WIP collision risk?
  • What public-safe PR packet should I give a maintainer?

Branch Analysis ​

Run from a Git repo:

sh
gittensory-mcp analyze-branch --login YOUR_GITHUB_LOGIN --json

The response includes:

  • lane context
  • role context
  • preflight findings
  • private score blockers
  • current vs projected scoreability scenarios
  • reward/risk reasoning
  • base freshness warnings when the local diff may be inflated
  • maintainer-fit notes
  • public-safe PR packet
  • ranked next actions

When the current score is blocked by temporary account/queue state, pass the assumptions explicitly:

sh
gittensory-mcp analyze-branch --login YOUR_GITHUB_LOGIN \
  --pending-merged-prs 3 \
  --expected-open-prs 0 \
  --projected-credibility 0.8 \
  --scenario-note "approved PRs expected to merge" \
  --json

Gittensory labels that as a user-supplied scenario. It shows the current effective score, the underlying potential score, and what changes if the open-PR and credibility gates clear.

Preflight ​

sh
gittensory-mcp preflight --login YOUR_GITHUB_LOGIN --json

Use this before opening a PR. It is especially useful when you need to know whether a branch is missing tests, missing a linked issue, colliding with active work, or likely to increase maintainer burden.

How This Helps ​

Gittensory does not promise payouts. It explains scoreability and risk:

  • open PR pressure
  • credibility assumptions
  • lane eligibility
  • issue-discovery vs direct PR fit
  • duplicate clusters
  • stale work
  • review friction

That makes recommendations actionable: land or withdraw blocked work, avoid direct PRs in issue-discovery-only repos, improve validation evidence, or pick a repo where your history and the lane actually fit.