code-quality

Enforce code quality standards via ESLint, oxlint, and TypeScript checks.

3|2|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Paxeer-Network/Sidiora-Perpetual-Protocol --skill code-quality-paxeer-network
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/Paxeer-Network/Sidiora-Perpetual-Protocol/tree/main/.windsurf/skills/code-quality
Command: npx skills add https://github.com/Paxeer-Network/Sidiora-Perpetual-Protocol --skill code-quality-paxeer-network

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses issues related to code quality, linting errors, unused variables, and documentation standards, ensuring a cleaner and more maintainable codebase.

Core Features & Use Cases

  • Linting and Type Checking: Run pre-commit hooks and CI checks for TypeScript, ESLint, and oxlint.
  • Code Standards Enforcement: Enforces English-only comments, single responsibility, and avoids over-abstraction.
  • Use Case: Automatically fix lint warnings, ensure all comments are in English, and verify that functions adhere to the single responsibility principle before committing code.

Quick Start

Run yarn lint:staged to check code quality for staged files.

Frequently Asked Questions about code-quality

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

FAQPage Schema
How do I enforce English-only comments and single responsibility in TypeScript?▼

You can enforce English-only comments and single responsibility by running automated linting and type-checking tools that specifically flag incorrect commenting and adherence to development principles during pre-commit hooks.

How do I run pre-commit hooks for ESLint and TypeScript linting?▼

Run pre-commit hooks for ESLint and TypeScript linting by executing `yarn lint:staged` to check staged files. This script validates code hygiene and automatically fixes lint warnings before code is committed.

What is the best way to automatically fix lint warnings for staged files?▼

The best way to automatically fix lint warnings for staged files is using yarn scripts for pre-commit hooks. Running `yarn lint:staged` checks code quality and addresses common issues like unused variables directly before committing.

Does this code quality tool support oxlint for CI validation?▼

Yes, this code quality tool supports oxlint for CI validation. It runs pre-commit hooks and CI checks for TypeScript, ESLint, and oxlint to ensure comprehensive code hygiene across your codebase.

Why does my CI pipeline fail on unused variables and over-abstraction?▼

Your CI pipeline fails on unused variables and over-abstraction because automated linting standards actively enforce avoiding over-abstraction and flag unused variables to maintain a cleaner, more maintainable codebase.