code-quality
Expertise in automated testing, code review practices, and quality standards enforcement. Activates when working with "lint", "test", "review", "coverage", "quality", "standards", or test automation.
Skills matching the name, description or GitHub author.
Expertise in automated testing, code review practices, and quality standards enforcement. Activates when working with "lint", "test", "review", "coverage", "quality", "standards", or test automation.
Comprehensive code review knowledge including security, performance, accessibility, and quality standards across multiple languages and frameworks
Review code changes for Jira issue. Use when the user wants to "review code", "code review", "jira review", or "check implementation".
Comprehensive code review knowledge including security, performance, accessibility, and quality standards across multiple languages and frameworks
Use this agent when you need a brutally honest Rails code review from the perspective of David Heinemeier Hansson. This agent excels at identifying anti-patterns, JavaScript framework contamination in Rails cod...
Code reviewer providing objective quality metrics, security analysis, and actionable feedback. Use for code reviews with scoring, linting, type checking, and duplication detection.
Ruthless code review for Python, Kubernetes, and AWS. Hunts for downstream problems, security issues, and unnecessary complexity. Use on 'review', 'check', 'audit', 'what could go wrong'.
Perform code reviews using OpenAI Codex CLI to identify bugs, security vulnerabilities, performance issues, and code quality problems. Use when the user asks to review code, check for issues, security audit, or...
Perform code reviews using GitHub Copilot CLI to identify bugs, security vulnerabilities, performance issues, and code quality problems. Use when the user asks to review code, check for issues, security audit,...
Critical Code Reviewer. Focuses on security, performance (Big O), and strict typing.
Use when you have received code review feedback and need to process it. [DEPRECATED] Routes to code-review --feedback
External AI code review using Codex or Gemini. Reads project.yaml to determine which provider to use for frontend vs backend tasks. Includes hallucination detection to avoid blindly applying AI suggestions.
Evaluate external PR suggestions (Gemini, CodeRabbit) against project conventions. Use when asked to review or agree with external code review comments.
Use during verification phase when conducting thorough code reviews and providing constructive feedback based on universal software quality principles.
Reviews the git changes, identifies critical and high-priority issues, generates review summaries, and collects metrics data for local use. Use this when users need to code review or analyzing code changes for...
Domain specialist for code quality assessment, maintainability, complexity analysis, code smells detection, anti-patterns identification, and code style enforcement. Scope: code review methodologies, naming con...
代码简化与优化专家/代码简化。Use this agent when you need to simplify, optimize, refactor, or clean up code. This agent helps reduce complexity, improve readability, and ensure code follows best practices like...
FTC skill code quality and structure checks. Activates when reviewing PRs, validating skills, or checking plugin compliance with marketplace standards. Use when reviewing pull requests, running local code revie...
Detect common code smells and anti-patterns providing feedback on quality issues a senior developer would catch during review. Use when user opens/views code files, asks for code review or quality assessment, m...
Comprehensive code review guidelines for React 19 TypeScript projects
Code review methodology, severity classification, and quality assessment patterns
Systematic code review guidance covering correctness, maintainability, security, and performance. Activates for PR reviews and code quality checks.
Streamlined code review workflow - gets SHAs and invokes superpowers:code-reviewer without permission prompts
This skill should be used when the user asks about "code quality", "file size limits", "function length", "KISS", "DRY", "YAGNI", "SRP", "best practices", "clean code", "cyclomatic complexity", "code review che...
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.