reviewdog CLI
The CLI matches linter diagnostics to code changes and reports findings locally or through an approved review channel.
- 9,721 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Configured runners execute project checks, and an external reporter can post diagnostics and comments using the supplied token.
Install
Manual install
curl -sfL https://raw.githubusercontent.com/reviewdog/reviewdog/fd59714416d6d9a1c0692d872e38e7f8448df4fc/install.sh | sh -sFirst Installation command, fetching the pinned-commit script and installing into ./bin by default. Do not enter the shell prompt $.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Configured runners execute project checks, and an external reporter can post diagnostics and comments using the supplied token.
This is third-party code. Review the repository files before installing.
What it does
reviewdog reads compiler or linter diagnostics and matches findings to changed lines. An agent can inspect a local diff-focused report, fix issues and rerun checks. The selected analysis tool supplies the actual rules. CI reporters publish checks or comments to supported review systems. Users choose input format, diff filtering and destination; one configuration can drive local and CI runs.
Who it is for. Repository maintainers who want existing linter findings attached to changed code.
Good fit when
- Lint output contains legacy issues while review focuses on the current patch.
- An agent should verify a fix locally before posting.
- CI needs several diagnostic commands in one workflow.
- Verified findings should appear beside changed review lines.
Not a fit when
- You expect defect detection without a linter or diagnostic input.
- The repository owner has not authorized review posting.
- Diagnostics cannot be correctly mapped to files and lines.
Example request
Run diagnostics through local reviewdog for this diff and show findings without posting to GitHub.Limitations
reviewdog needs a linter or other diagnostic source plus a parser matching its actual output. The default filter shows added or modified lines, hiding some existing findings. A zero exit code is possible despite reported issues; configure fail-level when findings must stop a CI job. Publishing requires service credentials and permission, and available comment locations depend on the selected review service API.
How to disable. Remove reviewdog from CI and revoke unused publication credentials. Existing review comments remain in the hosting service.
FAQ
Are comments posted by default?
No. The default local reporter prints results locally.
Where do I configure multiple checks?
Use `.reviewdog.yml` with commands and diagnostic formats.
How do I show all diagnostics?
Use `-filter-mode=nofilter`.
Why can CI pass despite findings?
Check `-fail-level`; findings do not fail the exit code by default.
Can it read SARIF?
Yes. SARIF is a supported input format.
Discussion
No questions or reviews yet.
Related
CLI toolsA code-review CLI and plugin for agents: reads a git diff and writes line-level comments with context
A CLI opens diffs and documents in a terminal so a person can annotate lines and pass feedback to a coding agent
A CLI and three skills that work through review-bot comments on a PR: assess findings, fix code, reply and wait for checks
A skill and CLI for code review: a team of reviewer agents inspects changes independently, debates findings and produces one report
A 1C code review agent: an auditor collects findings, a critic verifies them, and the result is a Markdown report
cross-review sends plans and code to a second model for review: Codex, Claude Code or Antigravity checks your agent's work.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| reviewdog (this card) | no | 9,721 | |
| open-code-review | no | 49,561 | analyzes changes itself using rules and a language model |
| PHP Insights | no | 5,647 | The project-local CLI checks PHP quality, style and complexity so an agent can inspect findings before changing the app. |
| typos | no | 4,209 | The CLI detects known source-code typos and gives agents reports or diffs that can be inspected before writing changes. |
README in short
Supported inputs include errorformat, RDFormat, Checkstyle and diff. Reporters differ in support for comments outside changed lines.