architecture-review
This skill should be used when the user asks to "review architecture", "analyze project structure", "check dependencies", "find circular imports", "analyze code patterns", "understand codebase structure", "map...
Discover tools code quality skills, compare source repositories and read the instructions for each workflow.
This skill should be used when the user asks to "review architecture", "analyze project structure", "check dependencies", "find circular imports", "analyze code patterns", "understand codebase structure", "map...
This skill should be used when the user asks to "check code quality", "analyze code metrics", "find dead code", "check style compliance", "measure complexity", "find unused imports", "check type hints", "run li...
Use ruff to lint, format, and modernize Python code. Activate when: (1) Fixing PEP 8 violations, (2) Removing unused imports, (3) Upgrading deprecated Python syntax (UP rules), (4) Auto-fixing code quality issu...
Testing patterns and best practices for unit, integration, and E2E testing.
Follow core coding style principles including SOLID, DRY, KISS, and YAGNI when writing code. Apply consistent naming conventions, meaningful variable names, small focused functions, automated formatting, and pr...
Write self-documenting code with clear structure and naming, using minimal but helpful comments only when necessary to explain complex logic. Use this skill across all code files when deciding whether to add co...
Review code for adherence to project guidelines, style guides, and best practices. Use after writing or modifying code, before committing changes or creating pull requests.
Analyze type design quality and invariants. Use when introducing new types, during PR creation with data models, or when refactoring type designs.
Analyze code comments for accuracy, completeness, and long-term maintainability. Use after adding documentation, before finalizing PRs with comment changes, or when reviewing existing comments for technical deb...
Identify silent failures, inadequate error handling, and inappropriate fallback behavior. Use when reviewing code with error handling, catch blocks, or fallback logic.
Clear writing standards based on Zinsser's principles. Use for documentation, commit messages, PR descriptions, and technical communication.
Code review workflow for evaluating changes against standards. Use when reviewing pull requests, commits, or diffs.
TRUST 5 검증, 사전 분석, 자동화된 모범 사례 적용을 포함한 엔터프라이즈 코드 품질 오케스트레이터
Applies Sun Lab C# and Unity coding conventions when writing, reviewing, or refactoring code. Covers .cs files, XML documentation, naming conventions, MQTT patterns, README.md files, git commit messages, and YA...
Git commit guidelines with conventional format, safety checks, and granular strategy. Use when making commits, staging changes, or writing commit messages.
Generate and improve unit tests using the Assured LLMSE approach from Meta's TestGen-LLM. Use this skill when users request help with writing unit tests, improving test coverage, adding test cases to existing t...
Garante padrões de código HTML limpo, semântico e consistente. Use quando criar ou modificar arquivos HTML, estruturar páginas, ou o usuário mencionar HTML, tags, atributos, ou estrutura de código.
GitHub Actions expert for CI/CD pipelines, workflows, build failures, test failures, lint errors, format checks, gh run, gh pr checks, ESLint, Prettier, TypeScript errors, quality gates, automated fixes, pipeli...
Scans codebases and dependencies for known vulnerabilities and security issues
Performs comprehensive security audits of codebases, identifying vulnerabilities and security best practices
Performs strict code review with comprehensive validation
Verifies code and configurations comply with security standards and regulations
Code review and audit agent for pull requests and code quality
Static analysis, code quality checks, and security scanning agent
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.