github-solution-research

# GitHub Solution Research Use GitHub as problem-solving evidence and an implementation source. The goal is to find open-source projects and GitHub evidence that already solve the user's specific engineering problem, report the relevant project information, then translate the existing solution into a local fix, implementation path, or verification plan. This skill is for concrete problems first. For general tool or architecture selection, use it only after the local goal has been framed as a specific capability, blocker, workflow, or integration need. ## When to Use - Runtime, build, test, deploy, package, SDK, API, dependency, framework, or integration errors. - A feature implementation is blocked by an unclear edge case, missing usage pattern, or uncertain API behavior. - A local issue resembles something that maintainers or other open-source users may have resolved in issues, PRs, examples, code, or release notes. - The user asks whether GitHub/open-source projects can solve the same problem. - Mature implementation examples or reusable projects would reduce uncertainty for one concrete capability. - The answer should compare suitable GitHub repositories and explain how to use one with local adaptation. Do not use for tiny edits, copy changes, local-only refactors where the codebase already dictates the answer, or requests that explicitly forbid web/GitHub research. Do not inspect private repositories unless the user explicitly scopes and authorizes that access. ## D...