What does OSS Hunter do?

OSS Hunter finds, analyzes, and strategizes high-impact open source contributions by identifying the most mergeable and influential issues in trending repositories and producing a ready-to-execute contribution dossier.

What are the four phases of OSS Hunter's protocol?

Phase 1 discovers trending repositories with over 1000 stars and recent activity using web search or the `gh` CLI. Phase 2 extracts issues with labels like `help-wanted` and `good-first-issue`. Phase 3 evaluates feasibility on reproducibility, impact, mergeability, and complexity. Phase 4 generates a structured dossier with project details, root cause analysis, fix strategy, and a confidence score.

What labels does OSS Hunter search for when extracting issues?

OSS Hunter searches for `help-wanted`, `good-first-issue`, `bug`, `v1`, and `roadmap` labels using the `gh issue list` command.

What are the limitations of OSS Hunter?

Accuracy depends on `gh` CLI or web search tool availability, analysis is constrained by context window when reading very large repositories, and PR acceptance can never be guaranteed since it remains at maintainer discretion.

When should I NOT use OSS Hunter?

OSS Hunter is not a fit for contributing to a specific already-chosen repository without discovery, or for generating the actual code fix itself—it scopes and strategizes contributions but does not implement them.

Skill

Find and Analyze Open Source Contributions

Name: OSS Hunter
Availability: OnlineOnly
Author: Antigravity

Finds and strategizes high-impact open-source contributions by hunting mergeable issues in trending repos.

Get skill

Works with github

Antigravity

Own this? Claim it

Spark score

out of 100

Updated 21 days ago

Version 14.1.0

Add to Favorites

Why it matters

Become a top-tier open source contributor by identifying high-impact, mergeable issues in trending repositories and generating actionable strategies for your contributions.

Outcomes

What it gets done

Discover trending open source repositories based on stars, activity, and relevant topics.

Extract relevant issues labeled 'help-wanted', 'good-first-issue', or 'bug'.

Analyze issue feasibility, impact, and mergeability.

Generate a contribution dossier with a proposed fix strategy and confidence score.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-oss-hunter | bash

Overview

OSS Hunter

Helps an agent find, analyze, and strategize open-source contributions by discovering trending repositories, extracting mergeable issues, running a feasibility analysis, and generating a structured contribution dossier with a confidence score. Use it when asked to find open-source issues to work on or to generate a contribution dossier for trending projects; needs the gh CLI or web-search tooling available.

What it does

Helps an agent find, analyze, and strategize open-source contributions by hunting for "mergeable" and influential issues in trending repositories. Runs a four-phase protocol: repository discovery (via web search or gh api, filtering for 1000+ stars and activity within the last 24 hours), issue extraction by label (help-wanted, good-first-issue, bug, v1/roadmap), feasibility analysis (reproducibility, user impact, how quickly the maintainer merges community PRs, and whether the issue fits the agent's current tools), and generation of a "Contribution Dossier" - project name and stars, issue link and description, root-cause analysis from code inspection, a proposed fix strategy, and a 1-10 confidence score.

gh issue list --repo owner/repo --label "help wanted" --limit 10

When to use - and when NOT to

Use it when asked to find open-source issues to work on, search for help-wanted or good-first-issue tasks in a specific domain (e.g. AI or Web3), or generate a contribution dossier for trending projects.

Not reliable without the gh CLI or web-search tooling available, when reading a very large repository exceeds the available context window, or as a guarantee of PR acceptance - that stays at maintainer discretion.

Inputs and outputs

Input: a domain or repository to hunt in, such as "trending AI repositories" or a named repo like langchain-ai/langchain. Output: a structured Contribution Dossier per candidate issue, with root-cause analysis, a proposed fix strategy, and a confidence score.

Integrations

Built by the ClawForge/OpenClaw community; its Phase 3 feasibility heuristics are explicitly designed to be extended via community contributions to the ClawForge project. Relies on the gh CLI and web-search tooling for repository and issue discovery.

Who it's for

Contributors and agents looking to make high-impact, mergeable open-source contributions rather than searching GitHub issues manually.

FAQ

Common questions

Discussion