Loading...
Loading...
Found 236 Skills
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
Analyze existing repositories, maintain structure, setup guardrails and best practices
Clean code principles, SOLID, and code review practices
Use this skill whenever creating or editing any markdown file. Do not wait for an explicit request — if a markdown file is being created or edited, this skill applies.
Fix knip "Unused exports" violations. Handles all violation categories: test-only exports (extract to new file), dead barrel re-exports (remove from index.ts), and internally-only-used exports (un-export). Use when `npm run knip` reports unused exports.
Configures and enforces SwiftLint in Swift projects using build tool plugins, run scripts, and CI. Covers .swiftlint.yml configuration, disabled_rules, opt_in_rules, only_rules, analyzer_rules, baselines, autocorrect, swiftlint:disable suppressions, reporter formats (sarif, json, checkstyle), strict and lenient modes, SwiftLintBuildToolPlugin via SimplyDanny/SwiftLintPlugins, swift package plugin swiftlint, Xcode run script phases, CI integration, multiple configuration files, and rollout strategies for existing codebases. Use when setting up SwiftLint, configuring lint rules, suppressing warnings, creating baselines, choosing between build tool plugin and run script, or integrating SwiftLint into CI.
Use when asking about Rust code style or best practices. Keywords: naming, formatting, comment, clippy, rustfmt, lint, code style, best practice, P.NAM, G.FMT, code review, naming convention, variable naming, function naming, type naming, 命名规范, 代码风格, 格式化, 最佳实践, 代码审查, 怎么命名
Validate TypeScript/JavaScript code quality with ESLint, Prettier, type checking, and security analysis. Use for TypeScript/JS codebases to ensure code quality and standards.
Verifies code changes by running tests and generation scripts
Format code on the current branch using Biome. Use when asked to format, lint, or clean up code before committing or creating a PR.
Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language
Work with the Inpoxia repository's local tools and workflows for CLI usage, GraphMail library changes, and quality checks. Use when tasks involve running or updating `inpoxia` commands, modifying files under `src/inpoxia/**`, validating behavior with `pytest`, or enforcing style/type checks with `ruff` and `pyright`.