python-development
Use when writing Python code for clean, performant, and idiomatic implementations
Discover databases code quality skills, compare source repositories and read the instructions for each workflow.
Use when writing Python code for clean, performant, and idiomatic implementations
Use when reviewing code for architectural consistency, designing backend systems, or evaluating structural changes
Use when reviewing code for quality, security vulnerabilities, and best practices
Code review checkpoint for conductor gates. Calls codex/review MCP tool to analyze code changes. Returns structured result with pass/fail status, issues found, and whether visual QA is needed.
Review code changes with automated quality checks and confidence-based filtering
Documentation check checkpoint for conductor gates. Analyzes code changes to determine if documentation needs updating. Returns structured result with pass/fail status and documentation suggestions.
Guides development, updates, and refactoring across the entire MCP server codebase. Use when adding features, updating categories, refactoring code, checking test coverage, or making any code changes. Enforces...
Review code changes and remove AI-generated patterns like excessive comments, gratuitous defensive checks, type escape hatches, etc.
Review code for SolidJS reactivity issues, TypeScript type safety problems, and component design anti-patterns. Use when asked to review code, check for issues, review a PR, or audit code quality.
Guide for code refactoring, use this skill to guide you when user asked to refactor a components or functions and when an implementation of a plan requiring a code refactoring.
コードベースの品質・セキュリティ・パフォーマンスを包括的に検証し、改善計画を策定するスキル。コードレビュー、セキュリティチェック、バグ検出、パフォーマンス最適化が必要な場合に自動的にトリガーされる。対象:(1) コ...
コードベースの品質・セキュリティ・パフォーマンスを包括的に検証し、改善計画を策定するスキル。コードレビュー、セキュリティチェック、バグ検出、パフォーマンス最適化が必要な場合に自動的にトリガーされる。対象:(1) コ...
Lint and fix shell script issues using ShellCheck. Use when the user says "check this script", "lint shell", "shellcheck", "fix script warnings", "validate bash", or asks to review a shell script for issues.
Coding style for every case when coding. Use when coding.
Homeostatic sensor detecting requirements without implementation or test coverage. Scans for REQ-* keys in requirements docs and checks if they have corresponding code and tests. Use to find coverage gaps.
Homeostatic sensor validating all requirements have design coverage. Checks for requirements without components, APIs, or data models. Quality gate before Code stage. Use to ensure design completeness.
Homeostatic actuator that tags code, tests, and commits with REQ-* keys for traceability. Adds "# Implements:" tags to code and "# Validates:" tags to tests. Use when code or tests are missing requirement tags.
Apply and validate the 7 Key Principles to code - TDD, Fail Fast, Modular, Reuse, Open Source, No Debt, Excellence. Checks code compliance and suggests improvements. Use during code review or refactoring.
Expert-level code review focusing on quality, security, performance, and maintainability. Use this skill for conducting thorough code reviews, identifying issues, and providing constructive feedback.
Expert-level Python programming with PEP 8 standards and modern best practices. Use when writing Python code, debugging Python issues, explaining Python concepts, or reviewing Python code.
Expert-level CodeQL for static analysis, vulnerability detection, and security code scanning
Transform messy code into clean code through disciplined refactoring. Code smells, refactoring patterns, and the courage to improve without breaking. Leave every codebase better than you found it.
Conduct thorough, constructive code reviews that improve code quality and team knowledge. Focuses on what matters - architecture, logic, security, maintainability - while avoiding bikeshedding.
Standards for project structure, tooling, and configuration (justfile, uv, ruff, etc).
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.