pr-helper
Standardized Pull Request creation with consistent formatting. Use when user says "create pr" or "ready to merge".
Discover tools code quality skills, compare source repositories and read the instructions for each workflow.
Standardized Pull Request creation with consistent formatting. Use when user says "create pr" or "ready to merge".
Request structured code review to catch correctness, security, performance, and readability issues. Reviews should happen early and often. Use this skill when: - Completing a task and need quality check - Afte...
Fixes corrupted Panda CSS styled-system when styles appear broken, CSS isn't applying, or the build fails with styled-system errors. Use when CSS looks wrong, styles are missing, or after prettier/formatters ma...
Review pull requests for code quality, architectural compliance, security issues, test coverage, and provide actionable feedback with suggested improvements
コードレビュアーとして回答。コード品質、セキュリティ、パフォーマンス、保守性を包括的にチェックする。
Perform a comprehensive code review
Python best practices and patterns. Use when writing, reviewing, or debugging Python code. Provides PEP 8 guidance, type hints, testing with pytest, and async patterns.
TypeScript best practices and patterns. Use when writing, reviewing, or debugging TypeScript code. Provides strict typing, ESLint configuration, testing patterns, and framework guidance.
Apply kinemotion development standards. Use when writing Python code, creating tests, modifying the kinemotion codebase, or reviewing code quality.
Apply kinemotion development standards. Use when writing Python code, creating tests, modifying the kinemotion codebase, or reviewing code quality.
Validate JSON file formats by scanning directories and checking for correct JSON syntax
Review code for quality, correctness, and standards. Use before commits or when reviewing PRs.
Expertise in reviewing code for style, security, and performance. Use when the user asks for "feedback," a "review," or to "check" their changes.
Must always be enabled when writing/reviewing TypeScript code.
Perform code review for PhotoClove codebase. Automatically invoked when reviewing code changes, PRs, or when asked to check code quality. Uses project-specific guidelines and knows what NOT to flag.
Validate, critique, and iterate on generated specifications
Comprehensive review and update of the documentation hub. Analyzes recent code changes, detects drift, validates structure, and proposes specific updates to keep documentation synchronized with the codebase.
Deep analysis of codebase vs documentation alignment. Detects drift, identifies undocumented code, extracts missing glossary terms, and provides actionable recommendations without making changes.
Detect over-engineering and YAGNI violations. Stricter than /review. Use when asked to "critique my code", "find over-engineering", or "check for unnecessary complexity".
Write structured code review comments using Conventional Comments format. Use when reviewing PRs, writing code review feedback, or asked to "comment on this code" or "review this PR".
Enforces modern, minimal, professional UI standards and rejects outdated or visually noisy web design patterns.
Verify code changes using syntax checking, linting, and build dry-runs. Must be run before committing any changes to Nix configuration files.
Proporciona ayuda para revisar código siguiendo las mejores prácticas de Roastr, verificando calidad, seguridad y documentación antes de crear un PR.
Review code changes for quality, spec compliance, and OSS readiness. Use when reviewing staged changes, PRs, or specific files for issues.
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.