linting-engineer

Automate linting and type checking for JavaScript/TypeScript and Python projects.

4|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/oxhagolli/clawdskillz --skill linting-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linting-engineer
Source: https://github.com/oxhagolli/clawdskillz/tree/main/skills/linting-engineer
Command: npx skills add https://github.com/oxhagolli/clawdskillz --skill linting-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After every code change, linting and type checks guard against style drift, bugs, and inconsistent typing, ensuring the codebase stays clean.

Core Features & Use Cases

  • Run after every change using the repository's existing linters and type checkers.
  • Enforce consistent typing and formatting across the project without introducing new tools.
  • Integrate into CI pipelines and local workflows to catch issues early before merges.

Quick Start

Run linting and type checking after every code change to ensure code quality before committing.

Frequently Asked Questions about linting-engineer

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

FAQPage Schema
How do I automate linting and type checking after every code change?

Automate linting and type checking by running existing repository tools like ESLint, ruff, and mypy after every code change to validate code quality and enforce formatting without adding new dependencies.

Can I use this for linting both JavaScript and Python projects?

Linting targets both JavaScript/TypeScript and Python projects by utilizing existing configurations such as ESLint and ruff, ensuring consistent typing and formatting across diverse codebases in local or CI workflows.

What's the best way to enforce strict type checking in a CI pipeline?

Enforce strict type checking in a CI pipeline by applying strict mode when available through existing repository tools like mypy, catching type inconsistencies and bugs early before code merges.

Does this static analysis tool require installing new linters or dependencies?

Static analysis requires adherence to existing repository tooling and configurations, reporting findings to guide fixes without introducing new linter dependencies to your project environment.

Why does linting after every change matter for code quality?

Linting after every change guards against style drift, bugs, and inconsistent typing, ensuring the codebase stays clean and maintaining consistent formatting across the project before commits.