security-quick-scan
Scan code or configuration for common security issues. Use when a mid-level developer needs a quick security pass.
Discover blockchain code quality skills, compare source repositories and read the instructions for each workflow.
Scan code or configuration for common security issues. Use when a mid-level developer needs a quick security pass.
Review infrastructure-as-code changes for safety and correctness. Use when a mid-level developer needs a second look on IaC.
Run a basic accessibility checklist for UI changes. Use when a junior developer needs quick a11y guidance.
Review a pull request for correctness, regressions, and missing tests. Use when a mid-level developer needs structured review guidance.
Explain lint errors and propose fixes. Use when a junior developer needs help resolving common lint or format warnings.
Audit dependencies for licensing, security, and maintenance risk. Use when a senior developer needs risk assessment.
Validate feature doc format against .patterns/feature-docs.md. Use when reviewing PRs, after editing feature docs, or before commits
Format Rust and TypeScript code automatically. Use immediately after editing .rs/.ts files, when user mentions formatting, code style, or before commits/PRs. Ensures consistent code style following project conv...
Validate and lint code after changes. Use after editing Rust/TypeScript files, when user mentions compilation errors, type checking, linting, clippy warnings, or before commits/PRs. Ensures all code passes chec...
Run shellcheck on shell scripts after editing scripts or when debugging shell errors. Use for linting scripts in a repo (especially scripts/), catching issues like set -u with unset vars, bad subshell usage, or...
Static Application Security Testing orchestration skill for running and managing SAST tools across codebases. This skill should be used when performing static code analysis, writing custom security rules, triag...
Lightweight code review for diffs/PRs focusing on high-signal simplifications, code smells, security, performance, and whether new tests are needed; focus on recently modified code unless instructed otherwise.
Analyze the impact scope of code changes using static dependency analysis
Guide for running and validating quality gates (build, lint, test, coverage, regression). Use when validating code, running tests, or checking if a phase can proceed.
Validates code changes against the project's consolidated knowledge and configuration rules. Use on push to catch violations of agreed-upon standards like installation scripts, linking patterns, and configurati...
Testing conventions and patterns for the Leather monorepo. Use when writing tests, creating test fixtures, or following TDD workflow. Covers Vitest setup, naming conventions, and common patterns.
Review pull requests for code quality, security, and adherence to repo patterns. Use when reviewing PRs, checking code changes, performing code review, or validating changes before merge.
Apply this repository's coding conventions and patterns. Use when writing or reviewing code in this codebase to ensure consistency with established patterns for DI, logging, error handling, testing, and documen...
Proactive code quality review. Triggers on significant code changes to check security, performance, architecture, and project patterns.
Validate and enforce markdown document structure including frontmatter positioning, heading hierarchy, and content organization. Use when creating or validating markdown files.
Detect and document existing code patterns in a codebase. Use to maintain consistency with established conventions when writing new code.
Enforce SOLID, DRY, KISS principles during implementation. Auto-activated when writing or modifying code.
Review code for quality, security, performance, and maintainability. Auto-activate after code modifications.
Follow git conventions for commits, branches, and PRs. Auto-activated during git operations.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.