take-screenshots
A Windows screenshot skill that provides both programmatic full-screen capture and interactive region selection.
Découvrez les skills research debugging, comparez leurs dépôts et consultez leurs instructions.
A Windows screenshot skill that provides both programmatic full-screen capture and interactive region selection.
Manage Claude Code hooks for workflow automation. Create, configure, test, and debug hooks that execute at various lifecycle points. Supports all hook events (PreToolUse, PostToolUse, SessionStart, etc.) with e...
Use to analyze and document any project codebase. Creates comprehensive reference documentation for AI-assisted development including architecture and patterns.
Comprehensive code review skill for TypeScript, JavaScript, Python, Swift, Kotlin, Go. Includes automated code analysis, best practice checking, security scanning, and review checklist generation. Use when revi...
Code review using reviewer agent. Thorough analysis of code quality, security, and best practices.
SUPERSEDED by persistent-cache-gap-filling (v2.8.0). Cache data during symbol selection for instant repeat runs.
Efficient development testing workflow for HPC environments with VS Code tunneling. Trigger: testing code changes on HPC, development workflow with external data directories, VS Code Remote SSH development
Evaluate a React component against the Design System and propose UX/UI improvements based on Figma best practices. Use when reviewing components for design compliance, checking UI consistency, or improving user...
Claude Code Hook system reference for capabilities, possibilities, and limitations. Use when you want to know what hooks can do.
Reviews code changes for bugs, style issues, performance problems, and best practices. Use when reviewing PRs, checking code quality, or auditing existing code.
触发并汇总预览结果(Java转发到Node Preview),输出预览链接与渲染耗时/错误快照。用户要预览或验收预览时调用。
生成发布审计报告(版本组合、操作者、耗时、结果),支持评审/复盘。上线评审、事故复盘或合规抽查时调用。
Context-gathering for finding files to read. Maps codebase structure, returns overview + prioritized file list with line ranges. Thoroughness: quick for lookups, medium for bugs/features, thorough for multi-are...
Audit code for bugs, logic errors, race conditions, and edge cases. Read-only analysis producing actionable report. Use before PR, after implementation, or when debugging. Triggers: review bugs, find bugs, chec...
Audit code for DRY violations, dead code, complexity, and consistency issues. Read-only analysis with actionable recommendations. Use before PR or for code quality review. Triggers: review maintainability, code...
Audit test coverage for code changes. Identifies untested logic and provides specific test recommendations. Read-only analysis. Use before PR or after implementation. Triggers: review coverage, check tests, tes...
Audit TypeScript/typed code for type safety issues. Identifies any abuse, missing type guards, and opportunities to make invalid states unrepresentable. Read-only. Triggers: review types, type safety, check typ...
Analyze code performance, detect bottlenecks, suggest optimizations for algorithms, queries, and resource usage. Use when improving application performance or investigating slow code.
Analyze project dependencies for vulnerabilities, updates, and optimization opportunities. Use when auditing dependencies or managing package versions.
Analyze application logs to detect errors, patterns, anomalies, and generate insights. Use when troubleshooting issues or analyzing system behavior.
Generate, optimize, and explain SQL queries with best practices. Use when writing database queries or optimizing SQL performance.
Analyze and prioritize technical debt with refactoring recommendations. Use when evaluating code quality or planning debt reduction.
Automated code review with security, performance, and best practices analysis. Use when reviewing pull requests or analyzing code for vulnerabilities, performance issues, or maintainability concerns.
Detect code smells including long methods, large classes, duplicated code, and deep nesting. Use when identifying code quality issues or planning refactoring.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.