DEV Community

Cover image for Stop opening 20 tabs to understand one GitHub issue 🐙
Kelvin-Air
Kelvin-Air

Posted on

Stop opening 20 tabs to understand one GitHub issue 🐙

#showdev #github #workflow

We have all been there. You find an open-source bug you want to fix, or an issue you need to triage. You click the link. Inside the discussion, someone links to a Pull Request in a dependency repository. That PR links to a closed issue. That issue points to a discussion thread.

Before you even write a single line of code, you are 20 tabs deep in browser chaos.

You lose the structural context, you forget where you started, and your brain is fried just tracking the dependency web.

I got completely sick of this tab tax, so I built FicCrunch.

🗺️ What is FicCrunch?

FicCrunch is a bounded reading path and link graph explorer for GitHub issues. Instead of forcing you to manually click through a maze of cross-repository links, it builds a structured roadmap for your reading.

[Your Target Issue] 
       │
       ├───► [Linked PR in Repo B] ───► [Fixed in Version X]
       │
       └───► [Related Issue in Repo C] ───► [Discussion Thread]
Enter fullscreen mode Exit fullscreen mode

You paste a single GitHub issue URL into the platform, and FicCrunch crawls the connected threads to generate a clean, sequential reading order. It stops the tab explosion by mapping out exactly what you need to read, and in what order.

🛠️ The Core Value (And why it saves your sanity)

  • Bounded Reading Paths: It limits your scope. You only see the issues and PRs that actually impact the problem you are tracking.
  • Cross-Repository Link Mapping: If an issue spans across an organization's main app, a client library, and a backend parser, FicCrunch maps them into a single graph.
  • Context Preservation: You can trace a bug from a top-level alert down to the exact broken package version without losing your place.

🔒 A Note on the Engine

I am building FicCrunch as a proprietary platform, so the core graph-mapping engine remains closed-source and private.

However, as someone who spends all day in the open-source ecosystem, I wanted to build a utility that genuinely helps contributors and maintainers navigate the unglamorous, chaotic side of tracking multi-repo dependencies. You don't need to open your code to add value to the community!

💬 I'd love your feedback!

FicCrunch is live, and I want to make it as useful as possible for triage workflows.

  • How do you currently handle tracking issues across multiple repositories?
  • What features would make a tool like this an immediate part of your daily workflow?

Give it a spin at ficcrunch.com and let me know what you think in the comments!

Home Page

Resolve Page

Top comments (0)