lint-and-typecheck

Runs mypy, ruff, tsc, and ESLint checks on Python and TypeScript code before integration.

1|9|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul --skill lint-and-typecheck-agenticgogol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lint-and-typecheck
Source: https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul/tree/main/.claude/skills/lint-and-typecheck
Command: npx skills add https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul --skill lint-and-typecheck-agenticgogol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Runtime smoke tests only prove the one path they exercise works, leaving type errors in untested branches and lint issues that signal real bugs undetected until much later. This Skill adds a static-analysis gate that catches those problems before integration. ## Core Features & Use Cases - Python Static Checks: Runs mypy (or pyright) for type checking and ruff for linting against backend and agent code. - TypeScript/Next.js Static Checks: Runs tsc --noEmit and next lint (or eslint) against frontend code. - Pipeline Gate: Blocks progression to integrate-and-assemble until every reported issue is fixed or a legitimate exception is documented in the project README. - Use Case: After scaffolding a Next.js frontend and FastAPI backend, run this gate to catch an unused variable, a wrong return type, or unreachable code before wiring the components together. ## Quick Start Run the lint-and-typecheck skill on the project to type-check and lint all backend and frontend code before integration.

Frequently Asked Questions about lint-and-typecheck

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I type check and lint a Python backend before deployment?▼

Run mypy (or pyright) for type checking and ruff check for linting against the backend directory. Fix every reported error rather than silencing real issues with type: ignore comments, and add both tools to the project's dev dependencies.

How do I run TypeScript type checking without emitting files?▼

Use tsc --noEmit to type check a TypeScript or Next.js project without producing output files. Pair it with next lint or eslint to catch style issues and common bugs in the same pass.

Should I use ruff or eslint for linting my project?▼

Use ruff for Python code since it is fast and covers common bugs plus style rules. Use eslint (or next lint for Next.js projects) for TypeScript and JavaScript code, as each tool targets its own language ecosystem.

Why is static analysis needed if runtime tests already pass?▼

A runtime smoke test only proves the one path it exercises works. Static analysis catches type errors in untested branches and lint issues like unused variables or unreachable code that the test never hit.

What should I do when a type check cannot pass legitimately?▼

Document the reason in the project README, for example when a third-party type stub is missing, instead of silently suppressing the error. Never proceed to integration with known unexplained type or lint errors.