mcpbeat

Lint Check

microsoft/lint-check

Run lint on affected packages, parse errors, and auto-fix common issues (design tokens, React.FC, SSR safety, import restrictions)

567 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
20188
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/microsoft/fluentui --skill lint-check

What it tells the agent to use

found in the instruction text
Bash runs shell commands — read the instruction before connecting

The instruction itself

3 sections, as written by the author

Lint Check and Auto-Fix

Run linting and fix common issues for Fluent UI packages.

Steps

  • Determine scope. If $ARGUMENTS is provided, lint that specific package. Otherwise, lint affected packages:
   # Specific package
   yarn nx run @fluentui/$ARGUMENTS:lint

   # Or affected packages
   yarn nx affected -t lint
  • Parse the output and categorize errors by the custom Fluent UI ESLint rules:

| Rule | What it catches | How to fix |

| --------------------------------------- | ------------------------------------------- | ----------------------------------------------------- |

| @fluentui/ban-context-export | Context exported from wrong layer | Move to react-shared-contexts package |

| @fluentui/ban-instanceof-html-element | instanceof HTMLElement (breaks iframes) | Use element.tagName or feature detection |

| @fluentui/no-global-react | React.FC, React.useState etc. | Use named imports: import { useState } from 'react' |

| @fluentui/no-restricted-imports | Banned import paths | Use the allowed import path from the error message |

| @fluentui/no-context-default-value | Context created without undefined default | Use createContext(undefined) and add a guard hook |

  • Auto-fix any issues found by editing the source files directly. For each fix:
  • Read the file
  • Apply the fix
  • Verify the fix by re-running lint on that specific file
  • Report a summary of what was found and fixed.

References

  • ESLint plugin source: packages/eslint-plugin/src/rules/
  • Design tokens guide: docs/architecture/design-tokens.md
  • Component patterns: docs/architecture/component-patterns.md

How to use it

Copy the folder

Take microsoft/lint-check from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.