S2 Lint runs comprehensive code quality checks including TypeScript types, ESLint, and Stylelint to prevent CI failures.
Install
mkdir -p .claude/skills/s2-lint && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2355" && unzip -o skill.zip -d .claude/skills/s2-lint && rm skill.zipInstalls to .claude/skills/s2-lint
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
After modifying S2 project code, you must run lint to ensure there are no errors, avoiding issues when pushing to git.Key capabilities
- →Run type checking
- →Execute ESLint style validation
- →Validate CSS/LESS style consistency
- →Verify documentation formatting
- →Check word casing
How it works
Invokes the project-specific pnpm lint sequence to validate code against established static analysis and style rules.
Inputs & outputs
When to use s2-lint
- →Validate TypeScript types
- →Check style consistency
- →Verify documentation formatting
- →Pre-commit code validation
About this skill
S2 Lint
When to use this skill
After modifying any code files in the packages/ directory, you must use this skill before finishing the task.
This includes but is not limited to:
- Modifying
.ts,.tsx,.vuefiles - Adding new source code files
- Modifying type definition files (
.d.ts) - Modifying import/export statements
- Modifying
.lessstyle files - Modifying
.mddocumentation files
Execution Steps
After completing all code modifications, run the following command in the project root:
pnpm lint
This command runs the following checks sequentially:
lint:type- TypeScript type checkinglint:script- ESLint code style checkinglint:style- Stylelint CSS/LESS checkinglint:docs- MarkdownLint documentation checkinglint:word- Case-police word casing checking
Handling Errors
If the command reports errors:
- Carefully read the error message to determine the location and cause of the error.
- Fix all errors to ensure code quality.
- Re-run
pnpm lintto confirm all errors are fixed. - The task is considered complete only after lint passes.
Notes
- Do not ignore lint errors; they may cause build failures in the CI/CD pipeline.
- If some errors are difficult to fix, inform the user and discuss solutions.
- This check is a necessary step before pushing code to git.
When not to use it
- →Pre-coding development phases
- →Projects without defined S2 linting rules
Prerequisites
Limitations
- →Requires environment setup
- →Cannot fix complex logic errors automatically
How it compares
Mandates a multi-layer validation step specific to the S2 project structure prior to completion.
Compared to similar skills
s2-lint side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| s2-lint (this skill) | 2 | 6mo | Review | Beginner |
| testing-workflow | 16 | 9mo | Review | Intermediate |
| playwright-pro | 8 | 3mo | Review | Intermediate |
| e2e-test-developer | 4 | 6mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by antvis
View all by antvis →You might also like
testing-workflow
amo-tech-ai
Comprehensive testing workflow for E2E, integration, and unit tests. Use when testing applications layer-by-layer, validating user journeys, or running test suites.
playwright-pro
alirezarezvani
Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites. Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55 templates, 3 agents, smart reporting.
e2e-test-developer
eclipse-che
Comprehensive E2E test development guidance for Eclipse Che / Red Hat OpenShift Dev Spaces. Use this skill when writing, modifying, or reviewing TypeScript Mocha Selenium tests, page objects, utilities, or test infrastructure. Provides code style rules, patterns, dependency injection setup, and best practices.
testrail
alirezarezvani
Sync tests with TestRail. Use when user mentions "testrail", "test management", "test cases", "test run", "sync test cases", "push results to testrail", or "import from testrail".
azure-microsoft-playwright-testing-ts
microsoft
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.
browserstack
alirezarezvani
Run tests on BrowserStack. Use when user mentions "browserstack", "cross-browser", "cloud testing", "browser matrix", "test on safari", "test on firefox", or "browser compatibility".