lint-and-validate

Automate linting, type checking, and security audits for Node.js and Python projects.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/achmf/KostaHub --skill lint-and-validate-achmf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-and-validate
Source: https://github.com/achmf/KostaHub/tree/main/.agent/skills/lint-and-validate
Command: npx skills add https://github.com/achmf/KostaHub --skill lint-and-validate-achmf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the risk of shipping broken, unoptimized, or insecure code by automating the execution of linters, type checkers, and security audits.

Core Features & Use Cases

  • Unified Quality Control: Automatically detects project type (Node.js or Python) and runs the appropriate suite of tools.
  • Static Analysis & Security: Performs syntax linting, type coverage analysis, and security vulnerability scanning.
  • Use Case: After refactoring a complex module, use this skill to verify that your changes haven't introduced type errors, style violations, or high-level security vulnerabilities.

Quick Start

Run the lint and validate skill on the current directory to perform a full quality audit of the codebase.

Frequently Asked Questions about lint-and-validate

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

FAQPage Schema
How do I automate static analysis and security auditing for Python and Node.js projects?

Automating static analysis and security auditing requires executing linters, type checkers, and security scanners against your codebase to detect syntax errors, type mismatches, and high-level vulnerabilities.

What's the best way to run linting and type checking after refactoring a module?

Running linting and type checking after refactoring involves executing project-specific validation tools to verify your changes haven't introduced type errors, style violations, or security vulnerabilities into the codebase.

Do I need to install eslint, tsc, ruff, and bandit locally before running code validation?

Yes, you must install standard development tools like eslint, tsc, ruff, and bandit locally, as the validation process requires these dependencies to execute comprehensive code analysis and security audits.

Can I use automated linting for both Node.js and Python in the same project directory?

Yes, automated linting supports both Node.js and Python by automatically detecting the project type and executing the appropriate suite of validation tools to ensure code compliance with established standards.

Why does static type checking fail to catch security vulnerabilities in my codebase?

Static type checking focuses on type coverage and syntax compliance, whereas security vulnerability scanning requires dedicated audit tools like bandit to identify security risks and enforce best practices.