Avoid manually wrapping comments

Repository metrics

Stars

5,022 stars (5,022 stars)

PR merge metrics

Avg merge 1d 16h (Avg merge 1d 16h)399 merged PRs in 30d (399 merged PRs in 30d)

Description

// This is a long comment but
// I don't like long lines

// This is a long comment but I don't like long lines

// This is a long comment. <-- period
// I don't like long lines

Contributor guide

Research direction

Study existing rules in eslint plugin unicorn (e.g., rules in the `rules` folder) to understand the pattern for creating a new rule. The rule should detect manually wrapped comments (i.e., adjacent single line comments that could be combined) and either report or auto fix them. Look at the AST structure of comments in ESLint (provided tokens) and consider edge cases like comments with periods or punctuation at line breaks. No linked PRs or additional comments provide further guidance, so the implementation is open ended.

Tech stack

javascript

Domain

toolingdeveloper experience

Issue type

Feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Clear

Prerequisites

basic knowledge of ESLint plugin developmentfamiliarity with AST of comments

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

60