commit-standards
Standards for writing clear, concise git commit messages. Use when creating commits, reviewing commit history, or establishing git workflow conventions.
Discover content media code quality skills, compare source repositories and read the instructions for each workflow.
Standards for writing clear, concise git commit messages. Use when creating commits, reviewing commit history, or establishing git workflow conventions.
Strict TypeScript configuration with all safety flags enabled. Use when initializing TypeScript projects or enforcing type safety.
Mandatory verification protocol after code changes for JavaScript/TypeScript projects. Use after any code modification to ensure quality.
ESLint 9.x flat configuration patterns. Use when setting up ESLint with TypeScript.
Standards for maintaining high code quality including comments, test coverage, and documentation practices
Pre-commit hook setup with Husky and lint-staged. Use when configuring git hooks.
Code quality standards, linting rules, and best practices for clean Solidity code. Use when reviewing code quality or establishing project standards.
Biome linter/formatter setup. Use when configuring Biome as an alternative to ESLint + Prettier.
Creates and manages Biome GritQL custom lint rules to enforce coding patterns. Use when creating linter rules, enforcing code conventions, preventing anti-patterns, or when the user mentions Biome, GritQL, cust...
Testing patterns with Bun test runner, coverage thresholds, mocking, and CI/CD integration. Use when writing tests, organizing test files, or setting up quality gates.
Fix go vet warnings
Fix staticcheck issues
Plugin validation errors and fixes
Configure and run golangci-lint
Enforces style consistency for documentation and code with support for taxonomy, voice, and formatting domains. Use when creating or modifying files requiring: (1) markdown structure (headers, lists, tables, Di...
Code style principle-based review - checks SRP (Single Responsibility Principle), DRY (Don't Repeat Yourself), Simplicity First, YAGNI (You Aren't Gonna Need It), and Type Safety. Also evaluates code structure...
Comprehensive code quality review focusing on DRY (Don't Repeat Yourself), KISS (Keep It Simple, Stupid), and Clean Code (Easy to Read) principles. Use when reviewing code changes, analyzing code quality, or as...
Analyzes test directory structure, coverage gaps, and helper consolidation opportunities. Produces coverage reports and refactoring recommendations. Use when auditing test suites, planning test improvements, or...
Systematic code review with security, performance, and architecture analysis. Provides actionable fix suggestions and GitHub PR integration. Use when reviewing PRs, validating code changes, or checking code qua...
You MUST use this skill when the user asks you to setup a claude code project. You should also suggest it if there is no CLAUDE.md or when starting work on an empty codebase.
Roast a repository to identify issues, then translate to constructive feedback. Use when user wants code review, wants to find problems, asks to "roast" their code, or wants honest feedback about their codebase...
AI 驱动的代码审查能力,当用户提到代码审查、code review、审查代码、查看代码质量等关键词时自动触发。使用 9 个并行 Agent 进行全维度分析(Bug/质量/安全/性能)。
自動化代碼審查,檢查程式碼品質、架構合規性、編碼標準,並與規格定義進行比對。
代碼實作階段觸發。強制執行統一的編碼規範,支援 Java、TypeScript、Go 多語言。包含 Input/Output 模式、依賴注入、不可變物件等規範,確保代碼風格一致性。
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.