GitHub issue graph tool: turn one issue into a link graph and reading order

FicCrunch is a GitHub issue graph tool for contributors: paste one issue and get a bounded link graph and reading order, including links in other repositories. Use Alive when you want a read on recent repository activity before you start.

ficcrunch.com/resolve

Issue Resolver

Triage a thread or prep before you PR — same paste, bounded path.

Not sure the project is alive? Check the repo first.

Guest · 1 free resolve · then sign in

01·THE PROBLEM

Why linked GitHub issues are hard to follow

One issue cites another org’s toolkit, a pull request, and three closed threads. You are twenty tabs deep with no order. FicCrunch bounds that crawl — including cross-repo links — and hands you a path.

02·HOW IT WORKS

How FicCrunch works

01·PASTE

Paste an issue or PR URL

That URL is the root. FicCrunch follows links from there. It does not walk the whole repository.

02·PATH

Get a bounded graph and numbered reading order

You get one bounded set of linked issues and pull requests, including links that leave the root repo, plus a numbered order to read them.

03·AI

Optional AI summaries

The graph and reading order come first. Turn summaries on for a resolve when you want them, and skip them when you don’t.

Example

Input: https://github.com/demo/handbook/issues/12

Graph: five issues, one in demo/toolkit (another repository).

  1. First-time contributors get lost in linked issues
  2. Document the local setup path
  3. Shared auth helper used by the handbook app
  4. Clarify which issue to open next
  5. Old decision: keep the reading path bounded

03·TWO TOOLS

Two tools: Resolve and Alive

01·RESOLVE

Resolve: map linked issues and pull requests

Start from one URL and see the linked issues and pull requests around it, with a path through them.

Resolve a GitHub issue

02·ALIVE

Alive: check repository activity

Alive reads public GitHub signals and tells you whether the repository looks active, quiet, archived, or unclear.

Check a repository’s recent activity with Alive

04·WHO IT'S FOR

Who FicCrunch is for

01·CONTRIBUTORS

Contributors preparing to work on an issue

Paste the issue you are about to touch. Read the linked context in order before you open a pull request.

02·MAINTAINERS

Maintainers reviewing linked context

Before you reply or merge, see the bounded path — including other repositories — instead of opening every related tab.

05·LIMITS

What FicCrunch does not do

  • It does not fix the issue or open a pull request for you.
  • It does not crawl an entire repository.
  • It does not triage a backlog or replace a project board.
  • It does not replace GitHub sub-issues. Sub-issues are planned work. FicCrunch orients the wider web of mentions and links.
  • Alive is a hint from public activity. It is not a verdict that a project is maintained or abandoned.

06·PLANS

Plans

Free and Pro differ by monthly resolves and AI summary budget. Founding Customer is a one-time seat with Pro limits.

FOUNDING CUSTOMER

Lifetime Pro limits — €29 once

13 paid seats left at €29 once (20% off with a partner code at checkout). Same Pro caps forever: 500 resolves/month and the Pro AI budget — not unlimited. GitHub account required.

07·QUESTIONS

Questions

What is a GitHub issue graph tool?
It turns one pasted issue into a bounded map of linked issues and pull requests, plus a numbered reading order. FicCrunch is one of the GitHub issue graph tools that follows those links even when they leave the starting repository.
Does it work with private repositories?
Not in this version. Resolve and Alive read public GitHub issues and pull requests. Sign-in does not unlock private repos.
Does it follow links across repositories and organisations?
Yes, when the issue or PR text names them, inside a hard bound. It does not crawl an entire organisation or repository.
How is it different from GitHub sub-issues?
Sub-issues are planned work you attach on purpose. FicCrunch orients the wider web of mentions and links that already exist in comments and bodies.
Why do I sign in with GitHub, and what permissions are used?
Sign-in is for your identity, monthly resolve quota, and optional AI summaries. It uses GitHub’s standard user profile OAuth, not a repo install. The product fetches public issue data with its own GitHub App. Sign-in does not grant FicCrunch access to private repositories.
What can Alive not tell me?
It cannot promise a project is maintained, abandoned, or that a pull request will be merged. It reports public signals such as recent pushes, open issues, and whether the repo is archived.

08·FEEDBACK

Feedback

FicCrunch is early. A short note after a real resolve helps more than a feature list — what helped, and what didn’t.