architecture-patterns-analysis
This skill should be used when the user asks to "analyze architecture", "review code structure", "check SOLID principles", "evaluate layering", "assess separation of concerns", "review module organization", or...
Découvrez les skills tools code quality, comparez leurs dépôts et consultez leurs instructions.
This skill should be used when the user asks to "analyze architecture", "review code structure", "check SOLID principles", "evaluate layering", "assess separation of concerns", "review module organization", or...
Code quality review patterns including quality gates, checklists, and language-specific checks.
Pack codebases into context-optimized formats for analysis and understanding.
Semantic code research across GitHub repositories for finding implementations, patterns, and conducting PR/security reviews.
Perform comprehensive code review with best practices analysis
This skill should be used when the user asks to "review code", "check code quality", "find improvements", "refactor code", "fix code issues", "perform code review", "check for bugs", "improve code", "analyze co...
內容一致性檢查器 — 確保程式碼、文檔、多來源之間保持一致
Perform comprehensive dead code and clean-up analysis in Python projects using static analysis, coverage, dependency checks, and security scanning. Use when asked to clean up code, find unused code, analyze dep...
Code Smells refactoring skill
Code review and quality assurance specialist for ensuring code quality, security, and maintainability
Verify and enforce coding standards, AI guidelines, and workspace compliance across repositories. Use for standards propagation, compliance verification, and enforcing development best practices.
Enforces immutable coding principles, function structure ordering, functional programming patterns, TDD, clean deletion, and YAGNI+SOLID+DRY+KISS principles for this codebase. This skill should be used when wri...
Enforces JSDoc documentation standards for this TypeScript project. This skill should be used when writing or reviewing TypeScript code to ensure proper documentation with file preambles, function docs, interfa...
This skill enforces the project's directory structure standards when creating or moving files. Use this skill when creating new components, screens, features, hooks, utilities, or any other code files to ensure...
Review code quality, receive feedback with technical rigor, verify completion claims. Use before PRs, after implementing features, when claiming task completion, for subagent reviews.
Setup and manage git hooks for pre-commit, pre-push automation (lint, test, format)
Validate governance constraints, CALM compliance, and architecture boundaries using spec-guard, flow-lint, and CALM validation. Use when checking if changes comply with SEA™ governance rules, enforcing invarian...
Validates code-documentation parity using tree-sitter static analysis. Use when user asks about documentation validation, doc parity, checking if docs are up to date, or whether code matches documentation.
Use when creating Git commits to ensure they follow the Conventional Commits specification. Provides guidance on commit message structure, types, scopes, and best practices for clear, consistent commit messages...
Check that no sorry placeholders exist in the codebase. Use after making changes or when asked to verify proof completeness.
Code review guidelines for commits and file changes. Covers four categories: Quality (security, correctness, maintainability), Regression (breaking changes, API compatibility), Documentation (code docs, changel...
PR 기준으로 시니어 소프트웨어 엔지니어 관점의 코드 리뷰를 수행합니다
Maintain Python code quality using Black formatting, Ruff linting, and mypy type checking. Use when formatting code, running linters, fixing style issues, or adding type hints.
Set up and configure Git pre-commit hooks for code quality, secrets scanning, and commit message validation. Use when installing git hooks, configuring pre-commit checks, or enforcing code standards.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.