Fetch IDE diagnostics for TypeScript and ESLint issues in changed files.
npx skills add https://github.com/mkolb22/zen-plugin --skill ide-diagnostics-mkolb22
Please help me install this Agent Skill. Skill: IDE Diagnostics Source: https://github.com/mkolb22/zen-plugin/tree/main/skills/ide-diagnostics Command: npx skills add https://github.com/mkolb22/zen-plugin --skill ide-diagnostics-mkolb22
IDE diagnostics help catch TypeScript and ESLint errors during quality review, preventing blocked reviews and rework by surfacing issues early.
Run IDE diagnostics at the start of quality review to surface critical TypeScript and ESLint errors.
High-intent search queries and answers about installing and using this skill.
To catch TypeScript and ESLint errors before code review, run IDE diagnostics to surface blocking issues early. This automated quality gate fetches compiler and lint diagnostics across changed and touched files, presenting a structured report of suggested fixes.
Running IDE diagnostics during quality review is the best way to perform static analysis on changed files. It integrates with your IDE to fetch all diagnostics, identifying blocking TypeScript and ESLint issues across the implementation to prevent rework.
Yes, you can use IDE diagnostics to automate quality gates for TypeScript code. By fetching diagnostics at the start of a quality review, the tool blocks reviews when blocking compiler or type errors exist, ensuring codebase stability.
Fetching IDE diagnostics prevents blocked reviews by surfacing TypeScript and ESLint errors before the review process begins. It provides fast, integrated feedback by scanning changed files and presenting a structured report of blocking issues and suggested fixes.
Yes, IDE diagnostics supports integration with mcp__ide__getDiagnostics to fetch all diagnostics. This integration retrieves compiler, type, and lint issues across changed and touched files, presenting a structured report to catch blocking errors during quality review.
IDE diagnostics surfaces TypeScript compiler errors, type issues, and ESLint lint problems during a quality review. It covers broad diagnostics across changed and touched files, presenting a structured report of blocking issues and suggested fixes to prevent rework.
keshavraj936Lint and statically analyze Node.js and Python code modifications.
flosrnResolve ESLint and TypeScript errors across a codebase using parallel agents.
prototypdigitalUpdate and validate documentation alongside code changes within version control workflows.
cyhinverseRun automated linters and type checkers on Node.js/TypeScript and Python repositories.
