linter-autofix-patterns
Cross-language linter autofix commands and common fix patterns for biome, ruff, clippy, shellcheck, and more.
Cross-language linter autofix commands and common fix patterns for biome, ruff, clippy, shellcheck, and more.
Review generated code for bugs, security issues, performance, and best practices. Use when reviewing Claude-generated code, checking for vulnerabilities, auditing implementation quality, or validating code changes before commit.
Use when developing ALTO itself - editing devenv.nix, hooks/*.py, agents/*.md, or checking Claude Code hook/agent syntax. Reference guide with documentation URLs and patterns.
Python code formatting with ruff format. Fast, Black-compatible formatting for consistent code style. Use when formatting Python files, enforcing style, or checking format compliance.
Integrate ruff with editors, pre-commit hooks, and CI/CD pipelines. LSP configuration, GitHub Actions, GitLab CI, and development workflows. Use when setting up ruff tooling or configuring development environments.
Structural code pattern search and refactoring using ast-grep (sg). Use for finding functions, classes, methods, imports, or any code structure patterns. Supports syntax-aware analysis across multiple languages including JavaScript, TypeScript, Python, Ruby, Go, Rust, and more. Use when searching for code patterns based on structure rather than plain text.
Wrapper around Tizen Studio static analyzer. Detects memory leaks, buffer overflows, and coding vulnerabilities in C/C++/JavaScript.
Standards for this static HTML/CSS/JavaScript project. Use this skill when working with vanilla JavaScript modules, HTML templates, CSS stylesheets, Node.js tooling scripts, or package.json configuration. Apply when editing .html files, .js files in js/ directory, css/styles.css, package.json scripts, or configuring Prettier/Lighthouse/markdownlint tooling.
Comprehensive single-file review. Generates preview with variables replaced, finds and replaces hardcoded values, adds _latex equations, validates consistency.
This skill should be used when the user asks to "scan for TODOs", "find placeholders", "clean up stubs", "remove temporary code", "audit for incomplete code", or "erase substitutions from codebase". Scans existing files for placeholder tokens and generates remediation plan.
Enforces functional programming, immutability, and strict type safety when writing, reviewing, or editing TypeScript and React code.
[Code Quality] Scans codebase for technical debt indicators: code smells, complexity hotspots, duplications, outdated patterns, and anti-patterns. Use when starting a refactoring session to identify what needs attention.
AST-based code search using ast-grep for structural pattern matching. Use when searching for code patterns, refactoring, or performing semantic code analysis across multiple languages.
Coding style standards enforced by Prettier and ESLint. Use this skill when writing JavaScript, HTML, CSS, or JSON to ensure consistent formatting, naming conventions, and code quality. Apply when creating new files, refactoring code, or ensuring adherence to automated formatting rules.
Natural language wrapper for validation commands - automatically triggers /validate-and-fix when users request quality checks, linting, or auto-fixes
Enforces TypeScript best practices when writing code. Automatically enables strict typing for TypeScript projects, prevents `any` usage, and recommends generic constraints. Activate on TS/TSX files, new features, code reviews.
Automatically substitute modern performant tools in generated code. Triggers whenever Claude writes code using npm, find, pip, grep, wget, or curl. Substitutions - npm→bun, find→fd, pip→uv, grep→rg, wget/curl→aria2. Adapts flags and syntax appropriately. Skip substitution only when user explicitly requests legacy tool by name.
Use when mcp-language-server tools are available and you need semantic code intelligence for navigation, refactoring, or type analysis
Advanced Clippy configuration for comprehensive Rust linting with custom rules, categories, and IDE integration. Use when configuring linting rules, enforcing code standards, setting up CI linting, or customizing clippy behavior. Trigger terms: clippy, linting, code quality, clippy.toml, pedantic, nursery, restriction, lint configuration, code standards.
Content appropriateness review for FTC student code. Activates when checking variable names, comments, and strings for inappropriate content before sharing. Use when reviewing code that students will see, checking for inappropriate language, or ensuring content is suitable for ages 12-18.
Use when JetBrains MCP tools are available (mcp__jetbrains__*) - enforces IDE-native workflow with problem checking after file completion, and smart refactoring tools instead of grep/sed
Validates markdown files using markdownlint after writing or editing. Invoke this skill after creating or modifying any markdown file to ensure consistent formatting and zero linting violations.
Python code style, formatting, linting, and type hints for GMailArchiver. Use when writing Python code, fixing ruff or mypy errors, adding type hints, formatting imports, or reviewing code quality. Triggers on: style, format, lint, ruff, mypy, type hint, import order, line length, docstring.