Pr Research

Before you open a PR on someone else's repo, this does the homework you'd otherwise skip. It checks if someone already beat you to it, hunts down CONTRIBUTING.md (and actually reads it), analyzes what merged PRs look like in practice, and figures out commit conventions from git history. The output is a markdown doc with concrete next steps and issue recommendations. It's basically codified paranoia for open source contributions. The workflow is sensible: research first, plan second, implement third. Saves you from that embarrassing moment when a maintainer points out you ignored their DCO requirement or duplicated an existing PR.