home / skills / jeremylongshore / claude-code-plugins-plus-skills / windsurf-linting-config

windsurf-linting-config skill

safe

/plugins/saas-packs/skill-databases/windsurf/skills/windsurf-linting-config

This skill configures and enforces code quality with AI-assisted linting across ESLint, Prettier, and CI pipelines.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill windsurf-linting-config

Review the files below or copy the command above to add this skill to your agents.

Files (5)

SKILL.md

1.9 KB

---
name: "windsurf-linting-config"
description: |
  Configure and enforce code quality with AI-assisted linting. Activate when users mention
  "configure linting", "eslint setup", "code quality rules", "linting configuration",
  or "code standards". Handles linting tool configuration. Use when configuring systems or services. Trigger with phrases like "windsurf linting config", "windsurf config", "windsurf".
allowed-tools: "Read,Write,Edit,Bash(cmd:*)"
version: 1.0.0
license: MIT
author: "Jeremy Longshore <[email protected]>"
---

# Windsurf Linting Config

## Overview

This skill enables comprehensive linting configuration within Windsurf. Cascade assists with ESLint, Prettier, Stylelint, and other linting tool setup, helping resolve configuration conflicts, suggesting rules based on project patterns, and automating code quality enforcement. Proper linting configuration catches errors early and maintains consistent code style.

## Prerequisites

- Windsurf IDE with Cascade enabled
- Node.js for JavaScript/TypeScript projects
- Package manager (npm, yarn, pnpm)
- Understanding of code style preferences
- Team agreement on quality standards

## Instructions

1. **Choose Base Configuration**
2. **Configure Rules**
3. **Set Up Prettier Integration**
4. **Add Pre-Commit Hooks**
5. **Integrate with CI**


See `{baseDir}/references/implementation.md` for detailed implementation guide.

## Output

- Configured .eslintrc.js
- Prettier configuration
- Pre-commit hooks
- CI integration

## Error Handling

See `{baseDir}/references/errors.md` for comprehensive error handling.

## Examples

See `{baseDir}/references/examples.md` for detailed examples.

## Resources

- [Windsurf Linting Guide](https://docs.windsurf.ai/features/linting)
- [ESLint Documentation](https://eslint.org/docs/latest/)
- [Prettier Integration](https://prettier.io/docs/en/integrating-with-linters.html)

Overview

This skill configures and enforces code quality with AI-assisted linting for Windsurf projects. It helps set up ESLint, Prettier, Stylelint and related tools, resolve configuration conflicts, and produce CI and pre-commit integrations. The skill accelerates consistent style adoption and catches common errors early across teams.

How this skill works

The skill inspects project files, dependencies, and coding patterns to recommend a base configuration and specific rules. It generates or updates .eslintrc, Prettier settings, stylelint configs, package.json scripts, pre-commit hooks, and CI job snippets. It can suggest rule sets tailored to frameworks (React, Node, Next.js, Vue) and surface conflicts between formatters and linters for automatic resolution.

When to use it

Initializing linting in a new JavaScript/TypeScript project
Standardizing code style across a team or mono-repo
Integrating linting into CI pipelines and pre-commit hooks
Migrating formatting rules to Prettier or consolidating multiple linters
Resolving conflicting rules between linters and formatters

Best practices

Start with a shared base config and extend it per package or workspace
Integrate Prettier with ESLint to avoid overlapping rules and use recommended plugins
Add pre-commit hooks (husky, lint-staged) to catch issues before commits
Run linting in CI as a blocking check and provide autofix suggestions where safe
Document rule exceptions and rationale in the repo to reduce future churn

Example use cases

Create .eslintrc.js and Prettier config for a React + TypeScript app with recommended rules
Add lint-staged and husky to enforce autofix on staged files before commit
Generate GitHub Actions snippet that runs ESLint and style checks on pull requests
Detect conflicting rules (e.g., trailing-comma vs Prettier) and apply safe overrides
Suggest rule tightening gradually (warn -> error) to avoid disruption in large codebases

FAQ

Can the skill autofix existing files?

Yes. It will generate scripts and recommend running eslint --fix or prettier --write, and can add lint-staged hooks to apply fixes on staged files.

Which projects does it support?

It focuses on JavaScript and TypeScript ecosystems and common tools like ESLint, Prettier, and Stylelint, including framework-specific presets for React, Next.js, Vue, and Node.