vercel-satori
ALWAYS use when writing code importing "satori". Consult for debugging, best practices, or modifying satori.
ALWAYS use when writing code importing "satori". Consult for debugging, best practices, or modifying satori.
ALWAYS use when writing code importing "vitest". Consult for debugging, best practices, or modifying vitest.
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.
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.
์ฝ๋ ๋ฆฌ๋ทฐ ์๋ํ ํ ํ์ดํ๋ผ์ธ. ์คํ์ผโ๋ณด์โ์ฑ๋ฅโ์ํคํ ์ฒ 4๊ฐ ์์ญ์ ์์ด์ ํธ ํ์ด ํ์ ํ์ฌ ์ฒด๊ณ์ ์ผ๋ก ๋ฆฌ๋ทฐํ๋ค. '์ฝ๋ ๋ฆฌ๋ทฐํด์ค', '์ด ์ฝ๋ ๋ด์ค', '์ฝ๋ ๊ฒํ ', 'PR ๋ฆฌ๋ทฐ', '์ฝ๋ ํ์ง ๋ถ์', '๋ณด์ ๋ฆฌ๋ทฐ', '์ฑ๋ฅ ๋ฆฌ๋ทฐ', '์ํคํ ์ฒ ๋ฆฌ๋ทฐ', '์ฝ๋ ์คํ์ผ ๊ฒ์ฌ' ๋ฑ ์ฝ๋ ๋ฆฌ๋ทฐ ์ ๋ฐ์ ์ด ์คํฌ์ ์ฌ์ฉํ๋ค. ํน์ ์์ญ๋ง ์์ฒญํ๋ ๊ฒฝ์ฐ์๋ ์ง์ํ๋ค. ๋จ, ์ค์ CI/CD ํตํฉ, ์๋ ์์ (auto-fix), Git ์ปค๋ฐ/๋จธ์ง ์์ ์ ์ด ์คํฌ์ ๋ฒ์๊ฐ ์๋๋ค.
์๋งจํฑ ๋ฒ์ ๋(SemVer) ๊ท์น์ ๋ฐ๋ผ ๋ณ๊ฒฝ์ฌํญ์ ๋ถ์ํ๊ณ ์ ์ ํ ๋ฒ์ ๋ฒํธ๋ฅผ ๊ฒฐ์ ํ๋ ๋ฐฉ๋ฒ๋ก . 'SemVer ๋ถ์', '๋ฒ์ ๋ฒํธ ๊ฒฐ์ ', 'Breaking Change ํ์ ', '๋ฒ์ ๋ฒํ ๊ฒฐ์ ' ๋ฑ ๋ฒ์ ๊ด๋ฆฌ ์ ์ฌ์ฉํ๋ค. ๋จ, git ํ๊ทธ ์๋ ์์ฑ, CI/CD ๋ฆด๋ฆฌ์ค ์คํ์ ์ด ์คํฌ์ ๋ฒ์๊ฐ ์๋๋ค.
OKR(Objectives and Key Results)์ ํ์ง์ ์ฒด๊ณ์ ์ผ๋ก ๊ฒ์ฆํ๋ ๋ฐฉ๋ฒ๋ก . 'OKR ๊ฒ์ฆ', 'OKR ํ์ง ์ฒดํฌ', 'KR ์ธก์ ๊ฐ๋ฅ์ฑ', 'OKR ์ ๋ ฌ ํ์ธ', 'Objective ํ์ง' ๋ฑ OKR ๊ฒ์ฆ ์ ์ฌ์ฉํ๋ค. ๋จ, OKR ์ํํธ์จ์ด ์ค์ , ์ธ์ฌํ๊ฐ ์ฐ๋์ ์ด ์คํฌ์ ๋ฒ์๊ฐ ์๋๋ค.
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.
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.
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.
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.
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.
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.
**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.
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.
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.
Implement the requested changes. Write production-ready code, follow existing patterns, and run tests to verify your work.
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.
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.
๐ฅ ็จ Gordon Ramsay ้ฃๆ ผๆฏ่ๅๆงฝไปฃ็ ่ดจ้๏ผ็ๆๆ็ฌไธๅฎ็จ็ไปฃ็ ๅฎกๆฅๆฅๅ
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.