Discover tools code quality skills, compare source repositories and read the instructions for each workflow.
Review code using GPT-5.2 Pro via Claude Code's Chrome integration. Use when the user asks to review code with ChatGPT, use their ChatGPT Pro subscription, get GPT-5.2 Pro to review code, or wants a second opin...
[TMUX MODE] Send code to Codex via tmux file-based IPC. Only use when user explicitly runs /codex-review command. For natural language requests like 'review with codex', use the delegate_codex_review MCP tool i...
Provides expert code review guidelines and best practices
Expert code review for Python focused on correctness, maintainability, error handling, performance, and testability. Use after writing or modifying Python code, or when reviewing refactors and new features.
Expert bash/shell scripting system across ALL platforms. PROACTIVELY activate for: (1) ANY bash/shell script task, (2) System automation, (3) DevOps/CI/CD scripts, (4) Build/deployment automation, (5) Script re...
Validate Mojo syntax against current v0.26.1+ standards. Use to catch syntax errors before compilation.
Generate fix suggestions based on error patterns and best practices. Use when analyzing failures to get actionable remediation steps.
Measure test coverage and identify untested code. Use when assessing test completeness.
Identify code quality issues and anti-patterns. Use when reviewing code for maintainability problems.
Scan code for security vulnerabilities and unsafe patterns. Use before committing sensitive code or in security reviews.
Validate GitHub Actions workflow files for syntax, best practices, and correctness. Use before committing workflow changes or when workflows fail.
Run pre-commit hooks locally or in CI to validate code quality before committing. Use to ensure commits meet quality standards and CI will pass.
Validate type safety in Mojo code including parametric types and trait constraints. Use during code review or when type errors occur.
Detect security vulnerabilities in code and dependencies. Use when auditing security.
Validate agent YAML frontmatter and configuration. Use before committing agent changes or in CI.
Format Mojo code using mojo format command. Use when preparing code for commit or when formatting checks fail.
Comprehensively review a pull request including code changes, CI status, and adherence to project standards. Use when asked to review a PR.
Validate Mojo code patterns (out self, mut, List, etc.) against best practices. Use to ensure code follows project standards.
Analyze code complexity metrics including cyclomatic complexity and nesting depth. Use to identify code that needs refactoring.
Review PR changes with structured checklist for quality and standards compliance. Use for comprehensive PR code review.
Run all configured linters including mojo format, markdownlint, and pre-commit hooks. Use before committing code to ensure quality standards are met.
Validate markdown files for formatting, links, and style compliance using markdownlint. Use before committing documentation changes.
Check function inputs for correctness and safety. Use when implementing defensive programming.
Check code for style and quality issues. Use when validating code before commits.
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.