code-quality
2
refactor-simplify-branching
[Code Quality] Simplifies complex conditionals: deep nesting, long if-else chains, switch sprawl. Use when control flow is hard to follow or has high cyclomatic complexity.
CANTAGESTUDIO
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
code-quality
2
typescript-strict-mode
TypeScript strict mode configuration for 2025. Recommended tsconfig.json settings, strict flags explained, moduleResolution strategies (Bundler vs NodeNext), verbatimModuleSyntax, noUncheckedIndexedAccess. Use when setting up TypeScript projects or migrating to stricter type safety.
laurigates
testing-security
code-quality
2
brane-code-review
Review Brane SDK code for correctness, Java 21 patterns, type safety, and architectural consistency. Use when reviewing PRs, checking code changes, or validating implementations against Brane standards.
noise-xyz
testing-security
code-quality
2
check-bash
Check bash script syntax without executing. Use before committing bash scripts or when verifying syntax correctness.
ManuelKugelmann
testing-security
code-quality
2
river-reviewer
River Reviewer のメインエントリポイント。 レビュー依頼を適切な専門スキルへルーティングする。
s977043
testing-security
code-quality
2
backend-reviewer
Senior Backend Code Reviewer with 12+ years Java experience. Use when reviewing Java/Spring code, checking code quality and style, identifying code smells and anti-patterns, verifying security practices, ensuring test coverage, or configuring static analysis tools (Checkstyle, SpotBugs, SonarQube).
olehsvyrydov
testing-security
code-quality
2
code-simplifier
Refactor recently modified code to be clearer and more consistent without changing behavior; follow CLAUDE.md conventions and avoid “clever” one-liners.
diegobit
testing-security
code-quality
2
html-lint-runner
Runs automated HTML linting using @axe-core/playwright (WCAG accessibility) and markuplint (HTML standards). Use when user asks to "lint HTML", "run automated checks", "validate HTML", "check accessibility", or mentions "axe-core", "markuplint", "automated audit".
naporin0624
testing-security
code-quality
2
feature-validator
Validates new features against the project's feature system documented in docs/FEATURES.md. Ensures feature flags follow conventions, checks feature module structure, validates feature usage patterns, and verifies cross-platform compatibility. Use when adding new features, modifying feature modules, or reviewing feature-based changes.
lewisflude
testing-security
code-quality
2
project-validation
Validates project after initialization. Checks static files, endpoints, CSS, health. Use when: after rust-project-init, before TDD loop. Triggers: "validate project", "check project", "verify init".
timequity
testing-security
code-quality
2
generic-fullstack-code-reviewer
Review full-stack code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md compliance. Enforces TypeScript strict mode, input validation, GPU-accelerated animations, and design system consistency. Use when completing features, before commits, or reviewing pull requests.
travisjneuman
testing-security
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
code-quality
2
tui-cli
Ensures TUI+CLI+Documentation parity for all feature changes. CRITICAL - Use this for EVERY change that affects commands, screens, shortcuts, or settings. Validates that changes are reflected in TUI implementation, CLI commands, docs/cli/, docs/tui/, docs/tui/shortcuts.md, CLAUDE.md, and feature registry. Prevents documentation drift and missing implementations.
MateusTorquato
testing-security
code-quality
2
ruff-formatter
Fix Python code formatting issues using the Ruff formatter. Use when: (1) Formatting errors are detected by ruff format --check, (2) Python files need to be formatted to match project style, (3) Pre-commit hooks or CI fail due to formatting issues.
frizzle-chan
testing-security
code-quality
2
code-maturity-assessor
Systematic code maturity assessment using Trail of Bits' 9-category framework. Analyzes codebase for arithmetic safety, auditing practices, access controls, complexity, decentralization, documentation, MEV risks, low-level code, and testing. Produces professional scorecard with evidence-based ratings and actionable recommendations. (project, gitignored)
plurigrid
testing-security
code-quality
2
git-security-checks
Pre-commit security validation and secret detection. Runs detect-secrets scan and audit workflow, validates secrets baseline, and integrates with pre-commit hooks to prevent credential leaks. Use when user mentions scanning for secrets, detect-secrets, secret detection, credential scanning, pre-commit security, or .secrets.baseline.
laurigates
testing-security
code-quality
2
review-scope
Use before code review - determine if change is minor (review new code only) or major (review impacted code too)
troykelly
testing-security
code-quality
2
style-guide-adherence
Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language
troykelly
testing-security
code-quality
2
typescript-type-safety
TypeScript type safety guidelines. Use this when writing TypeScript code, especially when handling errors or unknown data types.
ffMathy
testing-security
code-quality
2
review-spec
Review specifications for soundness, completeness, and implementability - validates structure, identifies ambiguities, checks for gaps before implementation
rhuss
testing-security
code-quality
2
backend-code-review
Conducts comprehensive backend code reviews including API design (REST/GraphQL/gRPC), database patterns, authentication/authorization, caching strategies, message queues, microservices architecture, security vulnerabilities, and performance optimization for Node.js, Python, Java, Go, and C#. Produces detailed review reports with specific issues, severity ratings, and actionable recommendations. Use when reviewing server-side code, analyzing API implementations, checking database queries, validating authentication flows, assessing microservices architecture, or when users mention "review backend code", "check API design", "analyze server code", "validate database patterns", "security audit", "performance review", or "backend code quality".
DauQuangThanh
testing-security
