opf/action-eslint

Analysis updated 2026-08-10 · repo last pushed 2021-12-08

JavaScriptAudience · developerComplexity · 2/5DormantSetup · easy

Mindmap

mindmap
  root((repo))
    What it does
      Checks JS code automatically
      Comments on pull request lines
      Flags style and errors
    How it works
      Uses ESLint for checking
      Uses reviewdog for comments
      Runs on every pull request
    Use cases
      Junior developer feedback
      Catch unused variables
      Enforce code style
    Config options
      Warnings or errors
      Block merging or not
      Check only new code

mindmap root((repo)) What it does Checks JS code automatically Comments on pull request lines Flags style and errors How it works Uses ESLint for checking Uses reviewdog for comments Runs on every pull request Use cases Junior developer feedback Catch unused variables Enforce code style Config options Warnings or errors Block merging or not Check only new code

What do people build with it?

USE CASE 1

Automatically flag inconsistent indentation or unused variables on pull request lines before a human reviewer sees them.

USE CASE 2

Configure the action to block merging when serious errors are found, enforcing code quality before changes land.

USE CASE 3

Set it to only check newly added code so pre-existing issues don't clutter review feedback.

USE CASE 4

Use it as an automated first-pass reviewer so senior engineers can focus on logic and architecture.

What is it built with?

JavaScriptESLintreviewdogGitHub Actions

How does it compare?

	opf/action-eslint	00kaku/gallery-slider-block	0verflowme/weirdhta
Language	JavaScript	JavaScript	JavaScript
Last pushed	2021-12-08	2021-05-19	2022-06-16
Maintenance	Dormant	Dormant	Dormant
Setup difficulty	easy	easy	moderate
Complexity	2/5	2/5	2/5
Audience	developer	general	developer

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Requires an existing ESLint configuration in your repository and a GitHub Actions workflow file.

No license information was provided in the explanation, so usage rights are unknown.

In plain English

This project is a GitHub Action that automatically checks your JavaScript code for common mistakes and style problems every time someone opens a pull request. Instead of forcing a human reviewer to spot every minor formatting inconsistency or potential bug, the tool leaves comments directly on the specific lines of code in the pull request, pointing out the issues it found. Under the hood, it combines two existing tools. The first, ESLint, is a widely used checker that scans JavaScript for errors, bad practices, and deviations from your chosen style rules. The second, called reviewdog, takes the problems ESLint finds and translates them into review comments directly on your GitHub pull request. This makes the feedback loop feel like a colleague is reading your code and leaving notes, except it happens automatically and instantly. Any team working with JavaScript or TypeScript in a GitHub repository would benefit from adding this. For example, if a junior developer submits a pull request with inconsistent indentation or a variable that is never used, this action will flag those issues on the exact lines in question before a senior engineer even looks at it. This saves reviewers from nitpicking style details, letting them focus their time on the actual logic and architecture of the changes. The tool is highly configurable through simple settings. You can decide how strict it should be, choosing to report issues as warnings or errors, and whether a found mistake should block the pull request from merging entirely. You can also tell it to only flag problems in the new code being added, rather than complaining about pre-existing issues elsewhere in the project, which keeps the feedback relevant and focused on the current work.

Copy-paste prompts

Prompt 1

Add the action-eslint GitHub Action to my repository so ESLint runs automatically on pull requests and posts review comments on specific lines.

Prompt 2

Configure action-eslint to report issues as warnings but not block the pull request, and only check lines changed in the current diff.

Prompt 3

Set up action-eslint to fail the pull request check and block merging when ESLint finds errors in JavaScript files.

Prompt 4

Help me write the YAML workflow file to use action-eslint with my existing ESLint config so code review comments appear automatically on PRs.

Frequently asked questions

What is action-eslint?

A GitHub Action that automatically reviews JavaScript code in pull requests by flagging style issues and mistakes directly on specific lines, so human reviewers can focus on logic instead of formatting.

What language is action-eslint written in?

Mainly JavaScript. The stack also includes JavaScript, ESLint, reviewdog.

Is action-eslint actively maintained?

Dormant — no commits in 2+ years (last push 2021-12-08).

What license does action-eslint use?

No license information was provided in the explanation, so usage rights are unknown.

How hard is action-eslint to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is action-eslint for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.