Claude skill standardizes community node lint rules
A new skill guides developers through the complete process of adding ESLint rules to the community nodes plugin, replacing ad-hoc approaches with templates and a checklist.
Adding a new lint rule to the community nodes plugin now follows a clear path. A new Claude Code skill walks developers through six steps: understanding rule requirements, implementing the rule from a code template, writing tests, registering the rule in plugin configs, creating documentation, and running verification commands. The skill includes a reference catalog of AST and file utility helpers, plus a checklist ensuring nothing gets skipped. The approach codifies existing best practices into a repeatable workflow, reducing the cognitive load for developers new to the codebase.
View Original GitHub Description
Summary
Adds a Claude Code skill (n8n:create-community-node-lint-rule) that guides agents through the end-to-end process of adding new ESLint rules to @n8n/eslint-plugin-community-nodes. Includes a step-by-step checklist covering rule implementation, tests, plugin registration, docs, and verification, plus a reference file cataloging all available AST and file utility helpers.
Related Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/project/community-node-lint-improvements-540c680d5366/overview
Review / Merge checklist
- PR title and summary are descriptive. (conventions)
- Docs updated or follow-up ticket created.
- Tests included.
- PR Labeled with
release/backport(if the PR is an urgent fix that needs to be backported)