HubForge
Open

HubForge

Discover what is holding your project back before the next meeting.

HubForge turns issues, pull requests, dependencies, and team capacity into an operational briefing the whole team can understand.

The problem

01

GitHub has activity, not operational context

Issues and pull requests pile up, but mixed teams cannot see what changed, what matters, or what to do next.

02

Blockers hide their impact

Dependencies live in threads and memory—not as a map of what is stuck and how many items wait behind it.

03

Capacity stays separate from the plan

The backlog is visible, but not who is free this week to own the next critical piece of work.

What HubForge delivers

Open HubForge after time away and answer in seconds: what completed, what blocked, what needs review, whether the project is moving, and what to do next.

How it works

  1. 01

    Connect GitHub — sign in and install the App on the repository your team already uses.

  2. 02

    Sync activity — import issues, pull requests, and checks. HubForge adds dependencies and capacity on top.

  3. 03

    Open Briefing — read what changed since your last visit, with facts and inferences clearly labeled.

  4. 04

    Act on signals — unblock dependencies, review pull requests, and assign work using team capacity.

Signal types

01

Character asset blocks three work items

Explicit dependency — integrate, UI, and trailer wait on art.

02

Pull request waiting for review

Input remapping PR open three days — merge blocked until someone reviews.

03

Critical work has no owner

High-priority save-slot migration — nobody has claimed it yet.

Who it is for

Studios of 3–15 people mixing programming, art, design, writing, production, and sound — already on GitHub.

Not for enterprises replacing Jira or teams that want another generic task board.

What HubForge is not

Not a chat replacement, not a second Kanban as the main product, and not a substitute for GitHub Projects or Discord. It interprets GitHub activity, dependencies, and capacity into a shared briefing.

Security and responsible GitHub use

OAuth signs you in. The GitHub App syncs only the repositories you install it on. Multi-tenant boundaries and least privilege are part of the foundation—not a later patch.