From 19a871a35ae9997ce352624b1081c96c54b73a9f Mon Sep 17 00:00:00 2001
From: Bryan Mishkin <698306+bmish@users.noreply.github.com>
Date: Fri, 2 Jul 2021 12:17:42 -0600
Subject: [PATCH] Docs: Suggest linting plugins for ESLint plugin developers
 (#14754)

---
 docs/developer-guide/working-with-plugins.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/docs/developer-guide/working-with-plugins.md b/docs/developer-guide/working-with-plugins.md
index 3809e3700d0..bea47021932 100644
--- a/docs/developer-guide/working-with-plugins.md
+++ b/docs/developer-guide/working-with-plugins.md
@@ -216,6 +216,14 @@ The plugin support was introduced in ESLint version `0.8.0`. Ensure the `peerDep
 
 ESLint provides the [`RuleTester`](/docs/developer-guide/nodejs-api.md#ruletester) utility to make it easy to test the rules of your plugin.
 
+### Linting
+
+ESLint plugins should be linted too! It's suggested to lint your plugin with the `recommended` configurations of:
+
+* [eslint](https://www.npmjs.com/package/eslint)
+* [eslint-plugin-eslint-plugin](https://www.npmjs.com/package/eslint-plugin-eslint-plugin)
+* [eslint-plugin-node](https://www.npmjs.com/package/eslint-plugin-node)
+
 ## Share Plugins
 
 In order to make your plugin available to the community you have to publish it on npm.