Loading...
Loading...
Found 14 Skills
Analyze Swift and mixed-language compile hotspots using build timing summaries and Swift frontend diagnostics, then produce a recommend-first source-level optimization plan. Use when a developer reports slow compilation, type-checking warnings, expensive clean-build compile phases, long CompileSwiftSources tasks, warn-long-function-bodies output, or wants to speed up Swift type checking.
Comprehensive skills for working with @hairy/utils core utilities
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
Comprehensive quality gate integrating linting, type checking, specification review, and security auditing.
Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis.
Run the mandatory verification stack when changes affect runtime code, tests, or build/test behavior in the OpenAI Agents Python repository.
Use when working in a Ruby project - provides authoritative sources for documentation, typing, and tooling
Build health audit worker (L3). Checks compiler/linter errors, deprecation warnings, type errors, failed tests, build configuration issues. Returns findings with severity (Critical/High/Medium/Low), location, effort, and recommendations.
Set up formatting, linting, import sorting, type checking, and pre-commit hooks when scaffolding or starting a new project. Use this skill whenever creating a new project, initializing a repo, scaffolding an app, or when the user asks to add linting/formatting to an existing project. Triggers on: "new project", "scaffold", "init", "set up linting", "add formatter", "add pre-commit hooks", "configure biome", "configure ruff". The goal is to establish code quality tooling from day one so issues are caught incrementally, not in a painful bulk-fix later.
Run formatting, lint, typecheck, and tests for this repo; use when validating changes or investigating CI failures.
Upgrade Python dependencies using uv, then run post-upgrade checks to ensure nothing is broken.
Code quality standards — lint (eslint/oxlint), type check (tsc), pre-commit hooks, and comment conventions. All comments must be in English.