r/developers • u/Severe_Still_887 • 3h ago
Programming, github, developers, opinions, inputs What repository investigation tasks still take you too much manual effort?
I’m building a repository intelligence tool and want to understand where it could be genuinely useful before developing it further.
Currently, it analyses public Python repositories on GitHub, creates snapshots at specific commits, compares code structure and relationships, highlights changes such as removed APIs, and generates an evidence-linked report.
It doesn’t automatically fix bugs or certify that a release is safe.
I’m interested in situations where understanding a repository becomes difficult or time-consuming—whether you’re maintaining it, reviewing changes, taking over someone else’s code, or investigating a failure.
A few questions for developers and engineering leads:
- What’s a recent task where you spent too long figuring out how a codebase worked or what changed?
- How did you investigate it, and where did your existing tools fall short?
- What specific output would have helped you make a decision or finish faster?
- Is this a recurring problem or something you face only during migrations, incidents, or handovers?
I’m considering use cases such as release comparisons, onboarding, change-impact analysis, and regression investigation, but I don’t want to assume those are the right priorities.
Concrete examples would be especially helpful. And if Git, your IDE, or existing tools already handle this well enough, I’d like to hear that too.