code-quality
536
vercel-satori
ALWAYS use when writing code importing "satori". Consult for debugging, best practices, or modifying satori.
nuxt-modules
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
code-quality
536
vitest-skilld
ALWAYS use when writing code importing "vitest". Consult for debugging, best practices, or modifying vitest.
nuxt-modules
testing-security
code-quality
535
backpack-code-review-checklist
Multi-agent review orchestrator for Backpack component PRs. Runs 5 parallel specialist agents, then confidence-scores findings to reduce false positives. Use for PR review, Constitution compliance checks, and pre-merge validation.
Skyscanner
testing-security
code-quality
529
okr-quality-checker
A methodology for systematically verifying OKR (Objectives and Key Results) quality. Used for 'OKR verification,' 'OKR quality check,' 'KR measurability,' 'OKR alignment check,' and 'Objective quality' when validating OKRs. Note: OKR software configuration and performance review integration are outside the scope of this skill.
revfactory
testing-security
code-quality
529
code-reviewer
코드 리뷰 자동화 풀 파이프라인. 스타일→보안→성능→아키텍처 4개 영역을 에이전트 팀이 협업하여 체계적으로 리뷰한다. '코드 리뷰해줘', '이 코드 봐줘', '코드 검토', 'PR 리뷰', '코드 품질 분석', '보안 리뷰', '성능 리뷰', '아키텍처 리뷰', '코드 스타일 검사' 등 코드 리뷰 전반에 이 스킬을 사용한다. 특정 영역만 요청하는 경우에도 지원한다. 단, 실제 CI/CD 통합, 자동 수정(auto-fix), Git 커밋/머지 작업은 이 스킬의 범위가 아니다.
revfactory
testing-security
code-quality
529
semver-analyzer
시맨틱 버저닝(SemVer) 규칙에 따라 변경사항을 분석하고 적절한 버전 번호를 결정하는 방법론. 'SemVer 분석', '버전 번호 결정', 'Breaking Change 판정', '버전 범프 결정' 등 버전 관리 시 사용한다. 단, git 태그 자동 생성, CI/CD 릴리스 실행은 이 스킬의 범위가 아니다.
revfactory
testing-security
code-quality
529
okr-quality-checker
OKR(Objectives and Key Results)의 품질을 체계적으로 검증하는 방법론. 'OKR 검증', 'OKR 품질 체크', 'KR 측정 가능성', 'OKR 정렬 확인', 'Objective 품질' 등 OKR 검증 시 사용한다. 단, OKR 소프트웨어 설정, 인사평가 연동은 이 스킬의 범위가 아니다.
revfactory
testing-security
code-quality
522
code-review
Performs thorough code reviews for Flutter/Dart pull requests and merge requests. Use when asked to review a PR, MR, branch, or a set of changed files. Follows a structured checklist covering correctness, security, style, testing, and documentation.
evanca
testing-security
code-quality
521
code-review
Perform code reviews following Sentry engineering practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.
getsentry
testing-security
code-quality
521
code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
getsentry
testing-security
code-quality
520
clean-code
Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing pull requests for readability, refactoring messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.
wondelai
testing-security
code-quality
520
refactoring-patterns
Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", or "decompose conditional". Also trigger when cleaning up legacy code, preparing code for new features by restructuring, or identifying which transformation to apply to a specific code smell. Covers smell-driven refactoring, safe transformation sequences, and testing guards. For code quality foundations, see clean-code. For managing complexity, see software-design-philosophy.
wondelai
testing-security
code-quality
519
sql-review
Pre-merge SQL quality gate — lint 26 anti-patterns, grade readability/performance A-F, validate syntax, and scan for injection threats. Use before committing or reviewing SQL changes.
AltimateAI
testing-security
code-quality
515
azd-preflight
**WORKFLOW SKILL** — Runs `mage preflight` from `cli/azd/` and auto-fixes failures. Covers linting, formatting, copyright, spelling, build, and tests. Iterates fix-then-rerun cycles until all checks pass. INVOKES: mage CLI, go CLI, golangci-lint, cspell, bash/sh, ask_user. USE FOR: azd preflight, run preflight, preflight checks, pre-commit checks, azd lint, azd build and test, validate azd changes, check azd code quality, mage preflight. DO NOT USE FOR: deploying azd (use azure-deploy), changelog (use changelog-generation), creating PRs (use pull-request), running only unit tests without the full suite.
Azure
testing-security
code-quality
512
dataset-evaluation
Validates dataset formatting and quality for SageMaker model fine-tuning (SFT, DPO, or RLVR). Use when the user says "is my dataset okay", "evaluate my data", "check my training data", "I have my own data", or before starting any fine-tuning job. Detects file format, checks schema compliance against the selected model and technique, and reports whether the data is ready for training or evaluation.
awslabs
testing-security
code-quality
512
security-review
Security review skill for the vykar backup tool (Rust). Use when reviewing code for security issues, auditing cryptographic implementations, checking for credential leaks, reviewing unsafe code, or validating the security model of the backup tool. Covers encryption, key management, repository integrity, hook execution, config parsing, dependency auditing, and backup-specific attack surfaces.
borgbase
testing-security
code-quality
511
implementation
Implement the requested changes. Write production-ready code, follow existing patterns, and run tests to verify your work.
ceedaragents
testing-security
code-quality
508
indexing-config
Use when writing or editing config.yaml. Chain/contract structure, addresses, start_block, event selection, field_selection, custom event names, env vars, address_format, schema/output paths, YAML validation, and deprecated options.
enviodev
testing-security
code-quality
506
config-setup
Set up or tune .codemap/config.json so Codemap focuses on code-relevant parts of the repo. Use when config is missing, boilerplate, noisy, or mismatched to the stack.
JordanCoin
testing-security
code-quality
500
lint-and-validate
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.
Asymmetric-al
testing-security