
Dart Long Lines
- 100 installs
- 139 repo stars
- Updated July 11, 2026
- kevmoo/dash_skills
Enforce 80-column line length rules in Dart code and refactor long lines according to linter standards.
About
Guidelines for handling long lines in Dart to comply with the 80-column rule (lines_longer_than_80_chars lint). Provides refactoring strategies for method chains, string literals, and function arguments.
- Part of dash_skills collection (8 total Dart best-practices skills) installable via skills CLI
- Works on Dart v3.0+ with coverage of Records, Pattern Matching, modern features
Dart Long Lines by the numbers
- 100 all-time installs (skills.sh)
- +10 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #444 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/kevmoo/dash_skills --skill dart-long-linesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 100 |
|---|---|
| repo stars | ★ 139 |
| Last updated | July 11, 2026 |
| Repository | kevmoo/dash_skills ↗ |
What it does
Enforce 80-column line length rules in Dart code and refactor long lines according to linter standards.
Files
Dart Long Lines
1. When to use this skill
Use this skill when:
- Writing Dart code that might exceed the 80-column limit.
- Refactoring code to comply with the
lines_longer_than_80_charslint.
Reference: https://dart.dev/tools/linter-rules/lines_longer_than_80_chars
Discovery
To find lines that exceed the limit:
Automated Analysis
The most reliable way to find long lines is to use the Dart analyzer:
- Command:
dart analyze - Lint:
lines_longer_than_80_chars
Manual Search
To search for long lines using regex:
- Regex:
^.{81,}$(Matches any line with 81 or more characters).
2. Guidelines
Format First
Always run dart format before manually breaking long lines. The formatter often automatically fixes long lines, especially in generated code, and applies standard Dart styling rules.
Code Comments
Break long code comments (//) cleanly at word boundaries to ensure lines do not exceed 80 characters. Maintain tight formatting and avoid unnecessary vertical space.
Documentation Comments (///)
- Apply the same line-breaking rules as for code comments.
- Avoid breaking markdown link blocks like
[name]or
[text](http://example.com) across lines. Place them on their own line if they exceed the limit.
- Start doc comments with a single summary sentence, followed by a blank line
before the rest of the comment. It is okay to break this first sentence across multiple lines to fit the 80-column limit.
- Avoid unresolved references or dangling sentences.
Long Strings
- Use adjacent string literals (e.g.,
'part 1 ' 'part 2') to break long
strings. Break at word boundaries.
- If a single-line string contains newline characters (
\n) or if there are
consecutive print statements, consider migrating to a multi-line string literal (''').
Format and Analyze After Changes
- Run
dart formatanddart analyzeafter making changes. - Be aware that splitting strings may trigger new lints (e.g.,
prefer_single_quotes if a double-quoted string is split into parts that no longer contain single quotes).
3. Examples
Documentation Comment Link
Avoid:
/// This is a long doc comment that contains a link to [a very long
/// URL](http://example.com/very/long/url/that/exceeds/eighty/chars).Prefer:
/// This is a long doc comment that contains a link to [a very long URL][ref].
///
/// [ref]: http://example.com/very/long/url/that/exceeds/eighty/charsAdjacent String Literals
Prefer:
final longString = 'This is a very long string that needs to be broken '
'across multiple lines to stay under the limit.';Multi-line String Migration
Avoid:
print('This is line 1\nThis is line 2 that is also quite long\nThis is line 3 which makes the whole thing exceed eighty characters');Prefer:
print('''This is line 1
This is line 2 that is also quite long
This is line 3 which makes the whole thing exceed eighty characters''');