ast-grep
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform comp...
Discover tools code quality skills, compare source repositories and read the instructions for each workflow.
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform comp...
Review test quality before PR - semantic analysis of test design, not just linting
Claude Code プラグインの構造とメタデータを検証する。plugin.json の必須フィールド、各コンポーネントのフロントマター、パス整合性、JSON 構文をチェック。Use when validating plugin structure, checking plugin correct...
Testing guidelines for Bun/TypeScript projects using bun:test framework. Use when writing tests, creating test files, debugging test failures, setting up mocks, or reviewing test code. Triggers on *.test.ts fil...
AST-based structural code search, security scanning, and refactoring using ast-grep (sg CLI). Supports 40+ languages with pattern matching and code transformation.
Enterprise code quality orchestrator with TRUST 5 validation, proactive analysis, and automated best practices enforcement
Reviews React and Next.js code for performance, accessibility, security, and adherence to project standards. Use when asked to review frontend PRs or components.
Enforces strict TypeScript rules and patterns. Use when refactoring code to be type-safe or fixing TS errors.
Reviews code for best practices and potential issues
Prevent i18n regressions for ko/en/vi (missing keys, long Vietnamese text UI breakage). Use when changing messages/*.json or adding user-facing strings.
Comprehensive code review with best practices, security, and maintainability checks. Use when reviewing pull requests, pre-commit code checks, learning code review techniques, improving code quality, or perform...
When reviewing coding test solutions. This Skill reviews coding test solutions and provides feedback. it adds an evaluation section to the README.md file in the problem-solving folder, including areas for impro...
Review code for correctness, maintainability, performance, and security. Produce actionable, prioritized feedback and concrete fixes aligned with repo standards.
Use when comments are growing faster than clarity: many “what” comments, frequent drift, or code that needs explanation to be understood. Goal: encode intent in names and structure, and keep only high-value tex...
Verify Java architecture rules with ArchUnit. Use when you need to define or validate package or layer boundaries, dependency constraints, slices, or cyclic dependencies in Java projects, including during refac...
Conduct thorough, actionable code reviews that catch real problems without drowning in noise
Pre-review preparation with formatted diffs and clear PR descriptions
Code linting and formatting standards for consistent, maintainable codebases
Pre-review preparation with formatted diffs and clear PR descriptions
Lint the entire project. Use whenever you finish editing to ensure your code is clean and follows best practices.
Automatically suggest tests for new functions and components. Use when new code is written, functions added, or user mentions testing. Creates test scaffolding with Jest, Vitest, Pytest patterns. Triggers on ne...
Check dependencies for known vulnerabilities using npm audit, pip-audit, etc. Use when package.json or requirements.txt changes, or before deployments. Alerts on vulnerable dependencies. Triggers on dependency...
Detect exposed secrets, API keys, credentials, and tokens in code. Use before commits, on file saves, or when security is mentioned. Prevents accidental secret exposure. Triggers on file changes, git commits, s...
Automatic code quality and best practices analysis. Use proactively when files are modified, saved, or committed. Analyzes code style, patterns, potential bugs, and security basics. Triggers on file changes, gi...
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.