blackfuel-ai/Blackfuel Code Review

AI-powered code review on pull requests, against any OpenAI-compatible inference endpoint.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Activelast commit Jun 11, 2026
License
MIT

Pinned Snippet

workflow.ymlSHA-pinned
uses: blackfuel-ai/code-review@aadf64df855510b6ba98e9911511e580eadbfb96 # v1.0.4

tags can be moved; commit SHAs can't. why a SHA?

Inputs

namedescriptionrequireddefault
openai-api-keyAPI key for the OpenAI-compatible inference endpoint (defaults to Fuel1 by Blackfuel).yes—
github-tokenGitHub token with `contents:write` and `pull-requests:write` scopes. The default `GITHUB_TOKEN` works for the default scope; provide a PAT if you want approval reviews from a specific bot identity.yes—
modelModel identifier (e.g. `oai@MiniMaxAI/MiniMax-M2.7`).nooai@MiniMaxAI/MiniMax-M2.7
openai-base-urlBase URL for the inference endpoint. Defaults to Fuel1 — point this at any OpenAI-compatible API to use a different provider.nohttps://api.fuel1.ai
reviewer-handleGitHub handle (without `@`) that humans can mention in PR comments to leave advisory notes for the reviewer. Notes are fed into the review prompt but never override findings.nocode-reviewer
submit-verdictWhen `true` (default), triage the sticky review comment into an `approved` / `changes_requested` verdict and submit a formal PR review (`gh pr review`). Set to `false` to post only the sticky review comment (advisory mode — no merge gating).notrue
approver-tokenOptional PAT used ONLY to submit the formal PR review when `submit-verdict` is `true`. Falls back to `github-token` when unset. Use a separate PAT when you want the approval to come from a named bot identity, since reviews submitted with the default `GITHUB_TOKEN` cannot approve PRs the GitHub Actions runner authored.no""

Outputs

namedescription
durationReview duration in seconds.
verdict`approved` or `changes_requested` when `submit-verdict` is true; empty otherwise.
rationaleBrief explanation of the verdict.