ruff-linter
Pythonコードのリンタ、フォーマッタ、コードレビュー。Pythonファイル(.py)を編集・作成・修正した後に必ず実行する。ruffによる品質チェックとフォーマット、さらにコードレビューを行い問題があれば修正する。
Découvrez les skills content media code quality, comparez leurs dépôts et consultez leurs instructions.
Pythonコードのリンタ、フォーマッタ、コードレビュー。Pythonファイル(.py)を編集・作成・修正した後に必ず実行する。ruffによる品質チェックとフォーマット、さらにコードレビューを行い問題があれば修正する。
AI-powered code review using CodeRabbit CLI. Use when reviewing code changes, checking PR readiness, getting feedback on staged/committed changes, or when the user mentions code review, CodeRabbit, or wants the...
Reviews code for logic flaws, edge cases, performance bottlenecks, security vulnerabilities, maintainability concerns, architecture best practices, and adherence to local patterns and CLAUDE.md guidelines. Use...
Enforce strict type safety, accessibility standards, and code quality for TypeScript/JavaScript projects using Biome's formatter and linter. Use when writing, reviewing, or fixing TS/JS/TSX/JSX code, checking f...
Automated code quality assistant that formats code, fixes syntax/type errors, detects bugs, and validates fixes across Python, JavaScript, TypeScript, Java, Go, and Rust
Validates Claude skill files for correct structure, YAML frontmatter, Python imports, naming conventions, and compliance with official documentation
Analyzes codebase for refactoring needs, generates todo reports, and validates completion
Analyzes codebases by impact scope (low/medium/high), generates refactoring checklists, supports interactive review, executes refactors with QA, and produces detailed optimization reports.
コーディング規約、テスト、Lint、型チェック、後方互換性。規約、コーディング、テスト、Lint、型チェック時に使用。
Review Go code for this project following Clean Architecture principles, Go best practices, and project conventions. Use when reviewing code, pull requests, or checking code quality.
各言語/フレームワークの安定版バージョン確認ガイド。 LTSの考え方、EOLチェック、アップグレード判断をサポート。
Analyzes code for complexity issues. Use when code feels hard to understand, reviewing maintainability, or planning refactoring.
Reviews code comments for quality. Use when reviewing documentation or evaluating if code is self-documenting.
Review and finalize (REVIEWER + DOCUMENTER phases) - runs adversarial code review, commits changes, completes task, and records reflection to capture pattern outcomes.
Review and finalize (REVIEWER + DOCUMENTER phases) - runs adversarial code review, commits changes, completes task, and submits reflection to update pattern trust scores.
Framework and stack identification with detection scripts and patterns. Use when detecting project type, analyzing framework, identifying stack, initializing projects, or when user mentions project detection, f...
Reviews Claude Code skills against official best practices and quality standards. Validates YAML frontmatter, checks SKILL.md length under 500 lines, verifies progressive disclosure patterns, assesses descripti...
This skill should be used when writing code in any opinionated framework's distinctive style. It applies when writing framework-based applications, creating models/controllers/views, or any framework code. Trig...
Code review checklist and patterns for thorough PR reviews
Assists with careful Git commits in any repository. Activates when committing changes, checking .gitignore, or generating commit messages. Ensures proper file exclusion (credentials, MCP configs, personal setti...
Assists with code refactoring by detecting code smells, suggesting improvements, and providing refactoring patterns. Activates when writing/editing code, explicitly requested refactoring, or when code quality i...
⚡ PRIMARY TOOL for semantic code search AND structural analysis. NEW: AST tree navigation with map, symbol, callers, callees, context commands. PageRank ranking. ANTI-PATTERNS: Reading files without mapping, G...
⚡ PRIMARY TOOL for: 'comprehensive audit', 'deep analysis', 'full codebase review', 'multi-perspective investigation', 'complex questions'. Combines ALL detective perspectives (architect+developer+tester+debug...
코드 리뷰에 대한 요청이 있을 시, 코드를 확인하여 프론트엔드/백엔드인지 구분하고 프론트엔드/백엔드 관점에 맞는 리뷰 가이드를 참조합니다.
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é.