Tools & Utilities
Essential command-line tools and system utilities.
code-review
Review implementation for code quality, style consistency, and best practices. Runs before security review. READ-ONLY - reports issues but does not fix them.
code-formatter
Auto-format code with Prettier and ESLint, fix linting errors, and enforce code style standards. Use when user says "format code", "fix linting", "prettier", "eslint", or when code needs style fixes.
dotnet-format-analyzers
Define canonical dotnet format and analyzer verification commands, and provide scripts that generate a format/analyzer report. Use when checking formatting or Roslyn analyzers without reformatting everything.
global-coding-style
Write clean, consistent code following established naming conventions, formatting standards, and the DRY principle with meaningful names and small focused functions. Use this skill when writing or editing any code file in any programming language. When naming variables, functions, classes, or files. When formatting code, organizing imports, or structuring functions. When refactoring code to remove duplication or dead code. When ensuring consistent indentation, code style, and readability. This skill applies universally to all code files including `.js`, `.ts`, `.py`, `.rb`, `.java`, `.go`, `.php`, and any other programming language files.
code-smell-detector
Detects code smells, anti-patterns, and common bugs with quantified thresholds and severity scoring. Use when reviewing code quality, finding maintainability issues, detecting SOLID violations, or identifying technical debt.
ringlinting-codebase
Parallel lint fixing pattern - runs lint checks, groups issues into independent streams, and dispatches AI agents to fix all issues until the codebase is clean.
code-quality
Reviews code for best practices, refactoring opportunities, complexity, and dead code
google-shell-style
Use when the user asks to "refactor shell script", "fix bash style", "apply Google style guide to shell", "review shell script style", "format bash script", or when writing, reviewing, or refactoring shell/bash scripts. Provides Google Shell Style Guide rules for formatting, quoting, naming, control flow, and common anti-patterns.
code-review
Review code for dealflow-network project conventions, error handling, type safety, and best practices. Use when reviewing pull requests, checking code quality, or validating implementations. This skill is read-only and will not modify files.
codereview-testing
Review test coverage and quality. Analyzes unit tests, integration tests, determinism, and test design. Use when reviewing test files or code that should have tests.
review-ruby-code
Comprehensive Ruby and Rails code review using Sandi Metz rules and SOLID principles. Automatically runs rubycritic and simplecov, analyzes changed files in current branch vs base branch, identifies OOP violations, Rails anti-patterns, security issues, and test coverage gaps. Outputs REVIEW.md with VSCode-compatible file links. Use when reviewing Ruby/Rails code, conducting code reviews, checking for design issues, or when user mentions code review, pull request review, or code quality analysis.
complexity
Analyzes code for complexity issues. Use when code feels hard to understand, reviewing maintainability, or planning refactoring.
rubycritic
Integrate RubyCritic to analyze Ruby code quality and maintain high standards throughout development. Use when working on Ruby projects to check code smells, complexity, and duplication. Triggers include creating/editing Ruby files, refactoring code, reviewing code quality, or when user requests code analysis or quality checks.
code-style-analyzer
Analyzes code for style and formatting issues including inconsistent formatting, naming conventions, code organization, comment quality, unused code, and magic numbers. Returns structured style issue reports with suggestions for improvement.
biome-gritql
Creates and manages Biome GritQL custom lint rules to enforce coding patterns. Use when creating linter rules, enforcing code conventions, preventing anti-patterns, or when the user mentions Biome, GritQL, custom lint rules, or AST-based linting.
code-review
This skill should be used when conducting comprehensive code reviews and codebase audits. Invoke when the user requests to review code quality, security vulnerabilities, performance issues, or best practices across entire codebases, directories, or specific files. Typical requests include "Review the codebase in ./src", "Audit this project for security issues", or "Review all Python files for quality".
code-quality
コードレビュー、コミットメッセージ生成、リファクタリング提案、テスト作成支援。静的解析、コーディング規約チェック、セキュリティスキャン。「レビュー」「コミット」「リファクタリング」「テスト」「コード品質」に関する質問で使用。
