code-quality
10K
code-review
Use to review code changes with a two-stage process - first checking spec/requirements compliance, then code quality. Works on staged changes, branches, or PRs.
open-metadata
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
code-quality
10K
verification
Use before claiming any task is complete. Requires running actual verification commands and showing evidence — no "should work" claims without proof.
open-metadata
testing-security
code-quality
9.6K
add-locale
Use when adding a new Humanizer locale or bringing an existing shipped locale to full parity. Trigger when work touches src/Humanizer/Locales, localization registries, shared locale engines, or culture-specific localization tests, and the locale must end with intentional coverage for every shipped localized surface with no English fallback, unsupported-locale gaps, or partial completion.
Humanizr
testing-security
code-quality
9.5K
unopim-code-review
Code review for UnoPim. Activates when reviewing code changes, checking standards compliance, flagging violations, or performing PR reviews; or when the user mentions review, standards, conventions, best practices, violations, or code quality.
unopim
testing-security
code-quality
9.4K
validate-contribution
Validate geographic data contributions against the CSC database schema. Use this skill whenever you encounter a PR that adds, modifies, or deletes data in the contributions/ directory. Trigger on: validate, check, review, verify, audit, inspect, or assess any data contribution, PR review requests, schema compliance checks, field validation, or when someone says "is this correct", "check my data", "validate this", or "review my PR". Also use when asked about required fields, allowed values, or data format rules. Read schema-rules.md in this directory for the complete field specification.
dr5hn
testing-security
code-quality
9.4K
python-review
Python code review guidelines for the Cog SDK
replicate
testing-security
code-quality
9.3K
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
microsoft
testing-security
code-quality
8.9K
risingwave-rust-analyzer
Use rust-analyzer CLI and editor/LSP settings to inspect, diagnose, and refactor RisingWave Rust code. Use when working in the RisingWave workspace and you need fast semantic analysis, unresolved-reference checks, macro-aware navigation, structured search/replace, or guidance on choosing the correct crate root and feature flags before heavier cargo or risedev commands.
risingwavelabs
testing-security
code-quality
8.9K
code-review
Review changed code against project standards. Checks for missing tests, dead code, type safety, lint issues, and coding conventions. Run after completing any implementation work.
vectorize-io
testing-security
code-quality
8.7K
perform-android-preflight-checklist
Quality gate checklist to run before committing or creating a PR. Use when finishing implementation, checking work quality, or preparing to commit. Triggered by "self review", "check my work", "ready to commit", "done implementing", "review checklist", "quality check".
bitwarden
testing-security
code-quality
8.6K
upgrade-dep
Upgrade a dependency in the Sentry JavaScript SDK. Use when upgrading packages, bumping versions, or fixing security vulnerabilities via dependency updates.
getsentry
testing-security
code-quality
8.6K
validate-prompts
Validate extracted Claude Code prompt data by reading files and checking rules directly — no external scripts or API calls needed. Checks JSON structure (30+ rules), generated markdown files, README consistency, and semantic variable name correctness. Use whenever asked to validate prompt JSON files, check generated output, run pre-release checks, debug validation errors, or analyze variable naming. Trigger phrases: "validate", "check prompts", "run validation", "verify prompts", "structural checks", "semantic check", "release prep". Also use when investigating a specific validation rule (A1–A21, B1–B6, C1–C7, A23) or when encountering errors in prompt data.
Piebald-AI
testing-security
code-quality
8.6K
verify-changelog
Verify changelog entries against actual prompt diffs by reading both JSON files and evaluating accuracy directly. Compares two prompt JSON versions (old → new), identifies added/removed/changed prompts, and checks that a human-written changelog accurately describes the changes. Use whenever writing, reviewing, or verifying a changelog entry for a new Claude Code version, when comparing prompt versions, when preparing a release, or when asked to "verify changelog", "check changelog", "changelog accuracy", or "diff vs changelog". Also use when asked whether a changelog is correct, complete, or well-worded, or when asked to help write a changelog for a version.
Piebald-AI
testing-security
code-quality
8.6K
code-review
Performs an architectural and quality code review on a specified file or set of files. Checks for coding standard compliance, architectural pattern adherence, SOLID principles, testability, and performance concerns.
Donchitos
testing-security
code-quality
8.6K
design-review
Reviews a game design document for completeness, internal consistency, implementability, and adherence to project design standards. Run this before handing a design document to programmers.
Donchitos
testing-security
code-quality
8.6K
release-checklist
Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.
Donchitos
testing-security
code-quality
8.6K
skill-improve
Improve a skill using a test-fix-retest loop. Runs static checks, proposes targeted fixes, rewrites the skill, re-tests, and keeps or reverts based on score change.
Donchitos
testing-security
code-quality
8.6K
skill-test
Validate skill files for structural compliance and behavioral correctness. Three modes: static (linter), spec (behavioral), audit (coverage report).
Donchitos
testing-security
code-quality
8.6K
repo-source-code-review
Review pull requests and source code changes in /library/src/. Use when reviewing PRs, validating implementation patterns, or checking code quality before merging. Covers code quality checks, type safety, documentation review, test coverage, and common issues to watch for.
open-circle
testing-security
code-quality
8.5K
license-compliance
Ensures all new files include proper Apache 2.0 license headers. Use when creating any new file in the Apache Beam repository.
apache
testing-security