eslint-plugin-react-hooks 7.x

Use eslint-plugin-react-hooks ^7.0.0 correctly, including its flat and legacy presets, rule names, custom-hook dependency configuration, and the preset-shape changes from older releases.

For

eslint-plugin-react-hooks@7.1.1

Verified

2026-09-08, 2 examples executed

Package

@modootoday/pmcp-eslint-plugin-react-hooks@7.0.0

What it covers

• Presets
• Explicit rule configuration
• `exhaustive-deps` and custom hooks
• Runnable package-surface checks
• Plugin rules and exports
• Flat and legacy preset shapes
• What this skill does not cover

One example from this skill

This is the skill's own text, not a summary of it. It runs: that is what verifying means here.

import assert from 'node:assert/strict';
import reactHooks from 'eslint-plugin-react-hooks';

assert.equal(typeof reactHooks, 'object');
assert.equal(typeof reactHooks.rules, 'object');
assert.equal(typeof reactHooks.configs, 'object');

for (const name of [
  'exhaustive-deps',
  'rules-of-hooks',
  'component-hook-factories',
  'config',
  'error-boundaries',
  'gating',
  'globals',
  'immutability',
  'incompatible-library',
  'preserve-manual-memoization',
  'purity',
  'refs',
  'set-state-in-effect',
  'set-state-in-render',
  'static-components',
  'unsupported-syntax',
  'use-memo',
]) {
  assert.equal(typeof reactHooks.rules[name], 'object', `missing rule: ${name}`);
}

What it did in the sandbox

Verifying this skill meant installing the package and running code against it with no route out. Nothing was observed. The full ledger lists every package examined, including the ones that never became a skill.

Nothing observed is not a finding of safety. It means one run, under one policy, produced nothing to report.

Getting it

With a subscription:

npx -y @modootoday/pmcp login
npx -y @modootoday/pmcp install @modootoday/pmcp-eslint-plugin-react-hooks

It installs as a dev dependency of your project, and the MCP server finds it there like any other skill.