knowledge-hooks
Reference knowledge for hooks: events (PreToolUse/PostToolUse/Stop), security patterns, exit codes, configuration types. Use when understanding hooks. No execution logic.
Discover Research skills, compare source repositories and read the instructions for each workflow.
Reference knowledge for hooks: events (PreToolUse/PostToolUse/Stop), security patterns, exit codes, configuration types. Use when understanding hooks. No execution logic.
Code review, PR analysis, and quality feedback. USE WHEN user mentions review, PR, pull request, code quality, best practices, feedback, suggestions, improvements, code smell, or asks to look at code for issues...
TypeScript strictest patterns, type guards, optional properties (exactOptionalPropertyTypes), Drizzle query safety, null checks. Use when fixing type errors, implementing complex types, or when user mentions Ty...
Document and explain existing codebases without critique or recommendations. Use when the user asks to research, investigate, or "look into" codebases (e.g., "research", "research this", "research the codebase...
Debugging, error diagnosis, and problem resolution. USE WHEN user mentions bugs, errors, crashes, exceptions, not working, broken, debugging, fix, issue, problem, stack trace, logs, or asks why something isn't...
Improving and debugging skills through metacognitive analysis. Use when needing to analyzes skill execution patterns, identifies flaws in instructions, and refines skill content to improve performance.
Provide educational insights and explanations about code. Use when the user asks questions like "how does this work", "explain", "why", "what does this do", "help me understand", or when exploring/learning abou...
Inspects what context is available
Performance tuning, profiling, and optimization. USE WHEN user mentions slow, performance, optimize, speed, latency, throughput, memory, CPU, bottleneck, profiling, caching, or asks why something is slow or how...
Review code for best practices and potential issues. Use when reviewing code, checking PRs, or analyzing code quality.
Audits code quality and patterns
Structural code search and refactoring via ast-grep (optional)
Log exploration and analysis using Quickwit search engine. Incident investigation, error pattern analysis, and observability workflows. Three index discovery modes for different performance and convenience trad...
Systematic debugging: reproduce, isolate, form hypotheses, instrument, fix, and add regression tests. Use when troubleshooting errors, failing tests, or unexpected behavior.
Auto-extract patterns from development sessions
Track data lineage และ provenance เพื่อเข้าใจ data flow, dependencies และ impact analysis
Code exploration and research without making changes
Gates สำหรับตรวจจับ performance regression ผ่าน benchmarks, bundle size, และ load time monitoring
Reverse engineers binary formats or code using appropriate CLI tools for the job."
OpenTelemetry observability - use for distributed tracing, metrics, instrumentation, Sentry integration, and monitoring
Analyze claude-trace JSONL files for session health, patterns, and actionable insights. Use when debugging session issues, understanding token usage, or identifying failure patterns.
Analyzes Xcode build timing to identify slow targets and optimization opportunities. Use when build is slow, user asks "why is the build so slow?", or wants to optimize compile times.
Comprehensive guide to CPU and memory profiling in Node.js and Python for identifying bottlenecks and optimizing performance
ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.
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.