remyxai/outrider

Outrider — GitHub Action

Scouts the arXiv frontier for your repo and picks the next paper most implementable against your codebase. Verifies each candidate's structural fit against your actual modules (not just keyword relevance), then either opens a draft PR wiring it into an existing call site, opens an Issue when a PR would be premature, or opens an RFC-shape Issue when the candidate proposes a new capability your team has signaled openness to. Won't re-recommend a paper that's already in front of your team — whether Outrider filed it or you did.

<p align="center"> <img src="https://github.com/remyxai/outrider/releases/download/readme-assets/outrider-v1.gif" alt="Outrider demo" width="800"> </p>

- uses: remyxai/outrider@v1
  with:
    interest-id: ${{ vars.REMYX_INTEREST_ID }}

What you get

• Draft PRs that wire a paper's contribution into an existing module, with a self-review section in the body honestly noting what was implemented vs. left out
• Issues when a PR would be premature — pre-flight, validators, or self-review route the paper to discussion instead of scaffold-shaped PRs
• RFC-shape Issues when the team has signaled openness to a new capability (a README roadmap section, an open [RFC] Issue, a CONTEXT.md investment pattern) and a candidate fits as an extension — a clear proposal instead of speculation
• No duplicate work — the same paper isn't re-recommended once any Outrider or maintainer Issue references it; reopen the Issue to re-engage
• A selection narrative in the run's GitHub Actions step summary explaining why this paper (or why nothing actionable this run) — visible at a glance, not buried in logs
• Actionable failure guidance, not opaque errors — when the agent fails on a recognizable cause (Anthropic credit-balance exhausted, invalid API key, rate-limit), the step-summary panel renders the specific remediation (top-up link, key-setup hint, retry note) instead of a buried log line
• **No stac