file-analyzer
Analyze files and extract useful information including statistics, type detection, and code structure
Discover tools code quality skills, compare source repositories and read the instructions for each workflow.
Analyze files and extract useful information including statistics, type detection, and code structure
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter
Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development
Multi-agent code review orchestration following 2024-2025 best practices. Use when: - Reviewing code changes before commit or merge - PR review with comprehensive analysis needed - Security audit of code change...
Guidance for writing valid Emacs Lisp code with incremental validation. Use when writing or modifying elisp functions, especially complex nested forms with cl-loop, multiple let* bindings, or lambdas.
Proactively run GitHub Actions pipeline checks locally before pushing code. Use when making code changes to catch test, lint, and type-check failures early.
Comprehensive rules for Go development, covering gRPC, error handling, domain-driven design, logging, and infrastructure configuration. Use these rules when writing, reviewing, or refactoring Go code.
Implement comprehensive validation on both server and client sides with specific error messages, input sanitization, and consistent validation across all entry points. Use this skill when validating user input,...
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 c...
Write self-documenting code with minimal, helpful comments that explain complex logic without documenting temporary changes or fixes. Use this skill when adding comments to code, documenting functions or classe...
Security reminder hook that warns about potential security issues when editing files, including command injection, XSS, and unsafe code patterns
Run quality checks on code changes. Use after implementation, before commits, or when the user mentions review, check, validate, or lint.
Audit codebase for secret handling issues. Scans for accidentally committed secrets, validates gitignore patterns, and ensures proper .env templates exist.
Intelligently detects project type (Node.js/React or Python) and runs appropriate linting tools. Use when checking code quality or validating project for style issues.
Visualize proposed code changes in a structured ASCII format with file tree, impact summary, syntax-highlighted diff, and rationale. Use this skill when proposing refactors, simplifications, or any code modific...
Execute code quality refactorings from gdscript-quality-checker reports. Use this when the user wants to implement the recommendations from a code review report.
Analyze GDScript code for quality, best practices, anti-patterns, and refactoring opportunities. Use this when the user wants to review code quality, check for Godot-specific issues, or improve code maintainabi...
6-phase read-only analysis workflow for Python code in markdown documents. Detects design principle violations, code smells, and suggests modern Python improvements. Applies project-type-aware thresholds (POC,...
Coding style guidelines for NixOS, Neovim, and Git. Use when writing or formatting Nix code, Neovim config, or working with Git workflow.
Perform comprehensive code reviews using OpenAI Codex CLI. This skill should be used when users request code reviews, want to analyze diffs/PRs, need security audits, performance analysis, or want automated cod...
Code review with Codex CLI. Use for PR review, diff review, code analysis, or when user says "codexでレビュー", "コードレビュー".
Request code review by dispatching reviewer subagent with proper context and git SHAs. WHEN: MUST use after completing major features or before merge. Invoke with "/requesting-code-review" or "request code revi...
Handle code review feedback with technical rigor, verification, and appropriate pushback. WHEN: MUST use when received code review feedback. Invoke with "/receiving-code-review" or "handle this review feedback"...
Professional code review for anti-patterns, extensibility, architectural soundness, and code quality. Use when users request code review, ask to check for anti-patterns, need architectural validation, want to e...
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.