gitcmurf/revrem

Run a RevRem code-review remediation loop on a pull request and post a single updatable comment with the results. WARNING: provider-backed CI makes paid model API calls; set max-usd/max-tokens before enabling on GitHub.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Activelast commit Jun 24, 2026
License
Apache 2.0

Pinned Snippet

workflow.ymlSHA-pinned
uses: gitcmurf/revrem@fb9d30c84743c93955e76a50fcf52f97db6a51eb # v0.5.0

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

namedescriptionrequireddefault
baseGit ref to review against (e.g. origin/main). The caller must checkout with fetch-depth 0.origin/main
profileRevRem profile to run.default
max-iterationsOverride the profile's max iterations.""
max-wall-secondsWall-clock budget in seconds.""
max-usdUSD cost ceiling. Strongly recommended for GitHub CI because provider-backed runs can incur real API charges.""
max-tokensToken budget ceiling.""
checksNewline-separated check commands (one per line), overriding the profile.""
routingOverride profile routing: "true" enables routing, "false" disables routing, empty uses the profile.""
commentPost an idempotent PR comment summarizing the run.true
upload-artifactsUpload the redacted HTML report as a workflow artifact.true
raw-artifactsAlso upload the full run directory verbatim. WARNING: this is NOT redacted — it contains raw prompts, model output, check output, and local paths. Only enable on trusted repos. (The HTML/JSON report from upload-artifacts is redacted; this raw bundle is not.)false
fail-on-findingsFail the job when RevRem exits 2 (findings remain).false
install-modeHow to install revrem — "pypi" (published) or "local" (this repo, for dogfooding).pypi
revrem-versionrevrem version to install from PyPI (install-mode: pypi only).0.5.0
github-tokenGitHub token for posting the PR comment. Leave unset to use the automatic GitHub token (resolved in the comment step); override to use a PAT or app token. The default is intentionally empty — not an expression — so the comment step fallback resolves correctly regardless of how GitHub handles expressions in input defaults.""

no outputs