motlin/code-generation
plugins/code/skills/code-generation/SKILL.md
This skill should be used when the user asks to "fix formatter-off", "fix code generation formatting", "fix auto-formatted string concatenation", "add formatter off", or when writing, reviewing, or generating Java code generators that build source code via string concatenation. Also applies proactively when creating new code generation methods or modifying existing ones — always use @formatter:off guards and the one-output-line-per-source-line convention.
$ install --global
skillsauthnpx skillsauth add motlin/claude-code-plugins code-generationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 19, 2026, 4:10 AM35.0s1 file scanned
SKILL.md
- name:
- code-generation
- description:
- This skill should be used when the user asks to "fix formatter-off", "fix code generation formatting", "fix auto-formatted string concatenation", "add formatter off", or when writing, reviewing, or generating Java code generators that build source code via string concatenation. Also applies proactively when creating new code generation methods or modifying existing ones — always use @formatter:off guards and the one-output-line-per-source-line convention.
Code Generation Formatting
Purpose
Java code generators that build source code via string concatenation must use // @formatter:off / // @formatter:on guards. Without these, IntelliJ's auto-formatter breaks concatenation chains across multiple lines, destroying the correspondence between Java source lines and generated output lines.
The Rule
Each line of generated output (terminated by \n) must occupy a single Java source line. A new line in the Java source should only occur where there is a \n in the template string.
Bad (auto-formatted)
setterBody = ""
+ " domainObject.get"
+ propNameUpper
+ "().clear();\n"
+ " return;\n";
Good (one output line per Java line)
// @formatter:off
setterBody = ""
+ " domainObject.get" + propNameUpper + "().clear();\n"
+ " return;\n";
// @formatter:on
How to Identify Violations
Search for string concatenation blocks that contain \n literals but are NOT wrapped in // @formatter:off. Common patterns:
- Multi-line
+chains where each+is on its own line and template variables are separated from their surrounding string literals .collect()lambdas producing single-line templates that got broken across multiple lines- Return statements wrapped in parentheses
return ( "" + ... )instead of directreturn "" + ...
Fix Procedure
- Search generator files for string concatenation containing
\nthat lacks@formatter:offguards - For each violation:
- Add
// @formatter:offbefore the block - Collapse string concatenation so each
\n-terminated segment is on one Java source line - Add
// @formatter:onafter the block
- Add
- For
.collect()lambdas that produce single-line templates (one\n), collapse the entire template string onto one line - For multi-line templates, each
\n-terminated segment gets its own line with+continuation - Use the same indentation style as existing
@formatter:offblocks in the file
Indentation Style
Match the existing convention in each file. The typical pattern uses tabs with + aligned:
// @formatter:off
// language=JAVA
return ""
+ "package " + packageName + ";\n"
+ "\n"
+ "public class " + className + "\n"
+ "{\n"
+ "}\n";
// @formatter:on
For .collect() lambdas with single-line output, keep it all on one line:
// @formatter:off
String fields = properties
.collect((p) -> " public final " + this.getType(p) + " " + p.getName() + ";\n")
.makeString("");
// @formatter:on
Additional Markers
When the string block contains valid Java source, add // language=JAVA after // @formatter:off to enable IntelliJ language injection for syntax highlighting inside the strings.
Related Skills
motlin/finish
tools
VerifiedTrustedCommunity
This skill should be used after completing any task, before returning control to the user. Always run this skill — it handles the case where there's nothing to do.
13SKILL.mdUpdated Apr 19, 2026
motlin/git-workflow
development
VerifiedTrustedCommunity
Commit message format and git workflow rules. ALWAYS use this skill for every git commit — no exceptions — and whenever rewording an existing commit message.
12SKILL.mdUpdated Apr 19, 2026
motlin/cli
tools
VerifiedTrustedCommunity
CLI guidelines. Use whenever using the Bash tool, which is almost always. Also use when you see "command not found: __zoxide_z" errors.
11SKILL.mdUpdated Apr 19, 2026
motlin/maven-cli
tools
VerifiedTrustedCommunity
Maven CLI invocation patterns. Use whenever running `mvn` commands in Java/Maven projects. Covers when `-am` is required, why `-o` (offline) mode hides bugs in multi-worktree setups, and how to verify compile/test cleanly without trusting stale `~/.m2` artifacts.
10SKILL.mdUpdated May 7, 2026