Find the perfect capability for your agent.
Conduct a detailed technical review of recent changes or a specific feature. Use when user says "review PR", "code review", or "review [scope]". Analyzes for logic errors, bugs, style issues, and performance. Fixes critical/high issues automatically.
Security audit for GitHub repositories before installation. Use when user wants to check if a repo/app is safe to install, review install scripts for malicious code, verify an open source project isn't collecting data, or audit dependencies for suspicious packages. Triggers on phrases like "is this safe to install", "check this repo", "review this script", "audit this code", "is this sketchy".
Generates sonar-project.properties for SonarQube code quality analysis and coverage reporting. Auto-detects test framework (Jest/Vitest) and configures coverage paths.
Generates .prettierignore to exclude build outputs, dependencies, and generated files from Prettier formatting. Prevents formatting of dist/, node_modules/, and coverage/ directories.
Use proactively to ensure code quality through reviews and testing. This is particularly important after code generation or changes.
Generates .stylelintrc configuration for linting CSS, SCSS, and Vue component styles. Auto-detects stylesheet type and fetches latest package versions for plugins.
Validate code before committing - runs linting, formatting, and tests. Use when preparing to commit, before git add, or when checking if code is ready to push.
Generate .vscode/settings.json configuration.
Systematically analyzes and fixes GitHub CodeQL security alerts with proper documentation and testing
Run analyzer MCP tools (Ruff + optional dead-code scan) as a quality gate before QA/UAT/release.
Assist with automated, safe, and explainable Python refactorings. Detects simple anti-patterns and offers AST-based transformations with patches and unit-test friendly changes.
Generates .prettierrc configuration file for code formatting with Prettier. Defines formatting rules for consistent code style across the project.
This skill analyzes code for design quality improvements across 8 dimensions: Naming, Object Calisthenics, Coupling & Cohesion, Immutability, Domain Integrity, Type System, Simplicity, and Performance. Ensures rigorous, evidence-based analysis by: (1) Understanding code flow first via implementation-analysis protocol, (2) Systematically evaluating each dimension with specific criteria, (3) Providing actionable findings with file:line references. Triggers when users request: code analysis, design review, refactoring opportunities, code quality assessment, architecture evaluation.
This skill should be used when the user asks about "code quality", "formatting", "linting", "lint rules", "code style", "error handling", "unsafe code", "documentation comments", "doc comments", "rustfmt", "prettier", "eslint", "clippy", or needs guidance on code quality enforcement and configuration.
Review functional area and component documentation to check that it adheres to repo standards.
Comprehensive YAML syntax validation, error fixing, and schema validation for various formats (GitHub Actions, Docker Compose, Kubernetes, GitLab CI). Use when Claude needs to: (1) Validate YAML syntax, (2) Check YAML files for errors, (3) Fix common YAML formatting issues, (4) Validate against schemas like GitHub Actions workflows, Docker Compose files, Kubernetes manifests, or GitLab CI pipelines, (5) Debug YAML parsing errors. Triggers on phrases like "check yaml", "validate yaml", "fix yaml errors", "yaml syntax".
Guide for using the VSCode `markdownlint` extension to check and fix Markdown issues. Use this when asked to configure or run Markdown linting without introducing CLI tools.
Review a feature/component documentation to check that it adheres to repo standards.
Evaluates code changes and documents against product, architecture, security and coding standards.
