validate-skills
Validate all skills in the repository for proper structure, frontmatter, naming conventions, and required files. Use when you need to check skill quality before publishing or after making changes.
Discover tools code quality skills, compare source repositories and read the instructions for each workflow.
Validate all skills in the repository for proper structure, frontmatter, naming conventions, and required files. Use when you need to check skill quality before publishing or after making changes.
Analyze current project's Claude Code configuration and suggest improvements
Applies project-specific coding conventions and patterns. Use when writing, reviewing, or modifying code to maintain consistency with the codebase style.
Checks for breaking changes in API serializers before production release. Use when reviewing PRs to production branch.
Maintain code quality with Ruff for Python and ESLint/TypeScript for frontend. Run linters, fix issues, and ensure consistent formatting. Use when linting code, fixing style issues, or preparing to commit.
Enforce repo execution discipline: keep PRs small; run migration-smoke when invariants change; never hand-edit vendored contracts.
This skill should be used to remove AI-generated artifacts and unnecessary code before committing. It scans changed files for redundant comments, AI TODOs, excessive docstrings, and unnecessary markdown files....
Revisa código en documentos LaTeX para asegurar convenciones de nombrado. Usa cuando el usuario mencione revisar código, verificar nombres de variables/funciones, o validar estilo de código en documentos.
Code review checklist covering security, performance, defensive programming, and testing anti-patterns. Use before merging PRs, after implementing features, or when reviewing code quality.
Comprehensive code review of current branch using multi-agent verification across DDD/OOP compliance, DRY violations, clean code principles, architecture patterns, and test coverage
変更後の検証を標準化し、部分検証→全体検証(pnpm check)を実行する
Automatically scan code for security vulnerabilities when user asks if code is secure or shows potentially unsafe code. Performs focused security checks on specific code, functions, or patterns. Invoke when use...
Automatically check code against PHPCS, ESLint, WordPress Coding Standards, or Drupal Coding Standards when user asks about code style, standards compliance, or best practices. Invoke when user mentions "coding...
Automatically validate implementations in real browsers after code is written or when user says "test this". Uses Chrome DevTools MCP to test responsive breakpoints (320px, 768px, 1024px), check accessibility c...
Automatically analyze test coverage when user asks which code is tested, mentions coverage gaps, or shows code asking about testing. Identifies untested code paths and suggests test additions. Invoke when user...
Automatically generate test scaffolding when user writes new code without tests or mentions needing tests. Supports unit, integration, e2e, and data tests for PHP and JavaScript. Invoke when user mentions "test...
代码审查流程,系统化分析代码质量、安全性和最佳实践
Orchestrates disciplined refactoring with scope boundaries and behavior verification. Infers refactor type and adapts verification approach. Prevents scope creep and ensures behavior unchanged. Use when improvi...
Refactor planning and execution discipline using LSP/Pyright. Use when making non-trivial refactors (splitting files, renaming symbols, moving modules) and you want compiler-accurate references/definitions, plu...
Lua/Neovim coding standards. Use when: writing or reviewing Lua code (*.lua) for Neovim plugins or configuration.
TypeScript coding standards. Use when: writing or reviewing TypeScript code (*.ts, *.tsx).
Analyze code for style violations, pattern compliance, and quality issues
Detect documentation drift (docs out of sync with code). Use after changes, periodically, or when something feels wrong. Returns severity-rated findings with specific fixes.
Validates a plan against documentation constraints before coding. Use after doc-discovery and before implementation. Returns PASS, WARN, or FAIL with specific issues. Gate 1 of 2-gate flow.
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.