dart-multiline-strings — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited dart-multiline-strings (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill when:
print() or stdout.writeln() statements into asingle, cohesive output block.
newlines (\n), or use nested indentations.
templated messages) to be readable, maintainable, and performant.
Do NOT refactor to multiline strings when:
(<80 chars) without embedded newlines.
bundles (e.g. intl, ARB files), where line breaks or formatting must conform to external translation tooling.
strict CSV rows, or queries where indentation whitespace inside triple quotes would alter payload semantics or introduce unintended leading spaces.
console streams where individual writes occur with delays or flushing between lines.
To find candidate code blocks for multi-line string refactoring:
print() or stdout.writeln() calls inside afunction, especially inside loops, console views, or CLI controllers.
\n escape sequences.+ operator or adjacentstring literal splits that are meant to represent multi-line outputs.
Instead of calling print() repeatedly for a multi-line output, group the contents into a single triple-quoted string literal: print('''...''').
In a triple-quoted literal, the exact spacing and formatting inside the quotes are preserved. Use this to specify indentation levels visually instead of using manually padded space prefixes (e.g., ' ').
If there are empty print() or print('') statements serving as vertical separators between output segments, replace them by letting the trailing newline of a multi-line string block handle the separation naturally.
If the opening triple-quote is immediately followed by a newline, the compiler discards it.
fresh line in the source code for clean layout.
line inside the triple-quoted block, or use \n explicitly at the beginning:
print('''
This starts with one blank line above it.''');print()print() automatically appends a trailing newline to the printed output.
''' on a new line (\n''');), an extra trailingblank line will be printed.
immediately after the final character:
// ✅ Emits standard output with no extra trailing empty line:
print('''
Header
Content''');When injecting optional content via interpolation (${condition ? '...' : ''}), placing the ${...} on its own line leaves behind its enclosing newline when the condition evaluates to '', producing an empty blank line in the output.
newline only renders when the content is present:
// ✅ Clean conditional rendering without ghost blank lines:
print('''
Branch Details:
Name: $branch${hasWarning ? '\n WARNING: $warningMessage' : ''}''');The lines_longer_than_80_chars lint rule automatically ignores lines inside multiline string literals. You can write long lines inside triple-quotes without triggering linter warnings or being forced to break them up.
Leverage Dart 3 switch expressions directly inside string interpolations to dynamically select and inject optional lines, conditional labels, or helper instructions. This avoids cluttering the surrounding code with imperatively constructed strings or multiple if statements:
print('''
Status: ${status.isSuccess ? 'PASS' : 'FAIL'}${switch (status) {
Status.failed => '\nError details: $errorMessage',
_ => '',
}}''');Avoid:
void printGerritView(String branch, String desc, bool hasConflicts) {
print('Branch Details:');
print(' Name: ' + branch);
print(' Description: ' + desc);
print('');
if (hasConflicts) {
print(' WARNING: This branch has conflicts.');
print(' Run `git merge origin/main` to resolve.');
}
}Prefer:
void printGerritView(String branch, String desc, bool hasConflicts) {
print('''
Branch Details:
Name: $branch
Description: $desc${hasConflicts ? '''
WARNING: This branch has conflicts.
Run `git merge origin/main` to resolve.''' : ''}''');
}~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.