Github Research

GitHub research

Investigate the GitHub surface of software: finding projects, reading a repo's profile, searching code, and scanning issues/releases.

When to use

• "Find a library for X" / "is repo Y maintained?" / "what changed in vN?".
• Debugging: an error is tied to a known issue or a recent release.
• Understanding how a project is built and used.

Tools used

• search_github — repos/issues/code/repository profile search (scope).
• github_repository — one repository's profile (owner/name).
• github_code_search — source-code-level search across repos.
• github_issues — issues/PRs/discussions search.
• github_releases — release list of a repository.

Workflow

1. Classify the question (find project? read repo? find code? find issue?).
2. Pick the matching tool; search_github with scope, or a direct github_repository/github_releases/github_issues call.
3. github_repository to ground claims about stars, license, activity, default branch, and last release.
4. Cross-check code hits with their owning repo before citing.

Input schema

{ "query": "str", "scope": "str", "limit": "int" }
{ "repo": "str" }

Output schema

{ "results": "list[{title,url,repo,description}]" }

Security

Repo metadata is self-reported; verify license/security claims on the actual repository before relying on them.

Related skills

code-search, web-search, error-investigation, source-analysis