code-quality
2
fix-line-endings-check-bash
Fix line endings AND check bash syntax in one step (recommended). Use after creating or editing bash scripts.
ManuelKugelmann
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
code-quality
2
frontend-quality-bar
Enforce a high-quality, production-ready standard for changes in this Next.js + Chakra UI frontend repo. Use for UX polish, accessibility, performance, error/loading states, code hygiene, and “ready to merge” checks (lint/format/build).
Stacked-Labs
testing-security
code-quality
2
code-review
Review code changes and remove AI-generated patterns like excessive comments, gratuitous defensive checks, type escape hatches, and over-engineering.
HexSleeves
testing-security
code-quality
2
code-reviewer
Reviews PHP/CakePHP code for quality, standards compliance, and best practices
masanao-ohba
testing-security
code-quality
2
receiving-code-review
Verification-first approach to code review feedback. Use when receiving review comments during the implement phase. Evaluate suggestions rigorously before implementing - no performative agreement.
bostonaholic
testing-security
code-quality
2
boy-scout-rule
Always leave code better than you found it. Use this when encountering any code quality issues, even if unrelated to your current task.
ffMathy
testing-security
code-quality
2
code-style-checker
Checks python code for use of print statements and suggests using logging instead. Use this when the user asks to review code or check for bad practices.
duizendstra
testing-security
code-quality
2
project-validator
Validate project structure, dependencies, and configuration files. Use when setting up projects, checking project health, or troubleshooting configuration issues.
tomada1114
testing-security
code-quality
2
rust-style-conventions
Foundational Rust style conventions that apply universally to all Rust code. Covers import organization, naming conventions, and code formatting standards. This skill is automatically applied to all Rust implementations and should be referenced by all other Rust skills.
matthewharwood
testing-security
code-quality
2
validation
This skill should be used when the user asks to "validate requirements", "review requirements quality", "check requirements completeness", "verify traceability", "check INVEST compliance", "validate user stories", "requirements health check", "quality gate check", or when running /re:review validation.
sjnims
testing-security
code-quality
2
applying-sun-lab-style
Applies Sun Lab Python coding conventions when writing, reviewing, or refactoring code. Covers .py files, docstrings, type annotations, naming conventions, README.md files, git commit messages, and Claude skill files. Use when writing new code, modifying existing code, reviewing pull requests, creating documentation, writing commit messages, or when the user asks about coding standards.
Sun-Lab-NBB
testing-security
code-quality
2
reviewing-code
Code review methodology for evaluating implementation changes. Use when reviewing code changes for quality, design, correctness, and maintainability. Focuses on changes made during implementation using Conventional Comments for clear, actionable feedback.
bostonaholic
testing-security
code-quality
2
code-review
Use after completing tasks to review code for quality and spec compliance. Two-stage review: Spec Compliance first, then Code Quality.
HankLiu447
testing-security
code-quality
2
comment-analyzer
Use when asked to review code comments for accuracy/quality or explicitly asked to run the comment-analyzer subagent.
troykelly
testing-security
code-quality
2
design-tokens-validator
[Design System] Validate that code and styles use official design tokens instead of hard-coded values. Use when (1) reviewing CSS/SCSS/Tailwind/styled-components for hard-coded colors/spacing, (2) checking SwiftUI/UIKit for raw color/font values, (3) auditing Unity styles for magic numbers, (4) enforcing design system compliance, (5) user asks to 'check design tokens', 'validate tokens', 'find hard-coded values', or 'audit design system usage'.
CANTAGESTUDIO
testing-security
code-quality
2
refactoring
Linter-driven refactoring patterns to reduce complexity and improve code quality. Use when linter fails with complexity issues (cyclomatic, cognitive, maintainability) or when code feels hard to read/maintain. Applies storifying, type extraction, and function extraction patterns.
buzzdan
testing-security
code-quality
2
basedpyright-type-checking
Basedpyright static type checker configuration, installation, and usage patterns. Use when implementing type checking, configuring LSP, comparing type checkers, or setting up strict type validation in Python projects. Triggered by: basedpyright, pyright, type checking, LSP, mypy alternative, static analysis.
laurigates
testing-security
code-quality
2
code-review
Guide for conducting thorough code reviews focusing on correctness, security, performance, maintainability, and best practices
vinnie357
testing-security
code-quality
2
code-metrics-analyzer
Calculate code quality metrics - complexity, coverage, maintainability
paleoterra
testing-security
code-quality
2
verification-stack
Use when running verification pipelines, checking test/lint/type status, or ensuring code quality gates pass before completing work
JoshuaOliphant
testing-security
code-quality
2
docusaurus-config
Use when working with docusaurus.config.js/ts files to validate or modify Docusaurus configuration
mcclowes
testing-security
code-quality
2
markdown-validation
Validate markdown documentation files for formatting issues, syntax errors, broken links, and quality standards. Use when checking .md files for compliance with documentation standards or after editing markdown files.
auldsyababua
testing-security