debugging
0
test-runner
Know exactly what failed, where, and why. No output parsing.
Technikhighknee
tools
domain cluster
Tools & Utilities
Essential command-line tools and system utilities.
32082 skillsall categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
debugging
0
tracing-compilation-events
Logs every compilation event with timing, tier (T1/T2), success/failure, and invalidation reasons. Use to verify hot code is compiling, diagnose compilation failures/bailouts, track recompilation cycles, and understand tiered compilation behavior. Shows WHEN compilation happens. Combine with detecting-performance-warnings to understand WHY compilation fails.
antonykamp
tools
debugging
0
browser-security
Analyze browser extensions and web code for security/privacy issues. Use when user mentions 'content blocker', 'extension security', 'XSS', 'fingerprinting', 'privacy leak', or 'CSP bypass'.
ali
tools
debugging
0
performance-optimization
性能优化技能：诊断和优化 React 前端、API 响应、数据库查询性能。 Use when: 页面加载慢、组件渲染卡顿、API 响应超时、数据库查询慢。 Triggers: "性能", "优化", "慢", "卡顿", "加载", "响应时间", "渲染"
dseirz-rgb
tools
debugging
0
dev-test-chrome
Chrome MCP browser testing. Console/network debugging, JS execution, GIF recording.
edwinhu
tools
debugging
0
optimizing-performance
Web/モバイル/バックエンド全体のパフォーマンス最適化を支援します。Core Web Vitals 改善、データベースクエリ最適化、インフラリソース最適化を提供します。パフォーマンス改善、ページ速度向上が必要な場合に使用してください。
sekka
tools
debugging
0
calculate-coverage
Calculate code coverage for .NET projects using local coverage scripts. Use when user asks to calculate coverage, check coverage, coverage metrics, test coverage. For NEW CODE coverage (what SonarCloud Quality Gate checks), use when user says "new code coverage", "coverage on new code", "changed code coverage", "feature branch coverage". For OVERALL coverage, use when user says "overall coverage", "total coverage", "full coverage", "complete coverage".
CodexForgeBR
tools
debugging
0
debug-mode
Run an iterative, hypothesis-driven “debug mode” loop to diagnose and fix a bug using targeted instrumentation and log capture. Use when the user wants an interactive debug loop, when you need to quickly narrow a failure via added debug statements, or when you need a lightweight way to centralize logs from a repro run (via `agent-skills debug` server + SSE UI).
strantalis
tools
debugging
0
website-audit
A comprehensive auditing suite for the JupitLunar website. It performs deep scans for broken links, console errors, accessibility issues, SEO compliance, and feature verification. Use this when the user asks to "audit the website", "check for broken links", "verify features", or "do a health check".
JupitLunar
tools
debugging
0
debugreact
Debug React issues systematically. Use when encountering component errors like "Cannot read property of undefined", infinite re-render loops with "Too many re-renders", stale closures in hooks, key prop warnings, memory leaks with useEffect, hydration mismatches in SSR/SSG applications, hook rule violations, missing dependency warnings, or performance bottlenecks. Covers functional components, hooks, and modern React 18/19 patterns including Server Components and concurrent features.
SnakeO
tools
debugging
0
fpf-skillverification-verify-behavior
Verifies that an execution trace complies with the FPF Behavioral Specification.
venikman
tools
debugging
0
scope-capture
REPL debugging tool for capturing and inspecting local scope at runtime. Use when debugging functions, investigating test failures, understanding intermediate values, or when you need to recreate the runtime context of code without manually fabricating values.
Ramblurr
tools
debugging
0
root-cause-tracing
Systematically trace bugs and issues to their root cause using debugging techniques and analysis methods
ljchg12-hue
tools
debugging
0
marimo-inspect
This skill should be used when inspecting marimo notebook execution results. Triggers include: - Checking notebook output - Viewing execution results - Reading __marimo__ HTML snapshots - Debugging notebook errors - Verifying cell outputs
dakesan
tools
debugging
0
p5-code-review
Reviews p5.js tower defense game code for architecture patterns, manager responsibilities, performance issues, and code quality. Use when reviewing enemies, towers, managers, renderers, or asking for code review.
LuluFur
tools
debugging
0
global-commenting
Write self-documenting code that explains itself through clear structure and naming, adding only minimal, evergreen comments for complex logic sections. Use this skill when deciding whether code needs comments, removing outdated temporal comments about changes/fixes, or writing concise explanations. Applies to all code files when balancing code clarity with necessary documentation, ensuring comments remain relevant far into the future rather than describing temporary states.
grimmolf
tools
debugging
0
bug-interview
Analyze and review bug reports to capture repro, evidence, and next diagnostic step. Use when a bug report lacks clear reproduction.
jscraik
tools
debugging
0
instrumentation-planning
Plan what to measure in web applications. Use when starting observability or prioritizing instrumentation.
nexus-labs-automation
tools
debugging
0
debugging-mastery
Systematic debugging methodologies for finding and resolving complex bugs. Use PROACTIVELY when encountering difficult bugs, mysterious failures, or issues that resist simple fixes. MUST BE USED when debugging spans multiple files, involves race conditions, or has eluded initial investigation attempts.
Danik911
tools
debugging
0
cljr-performance
Optimize Cljr compiler and runtime performance. Use when optimizing emitter output, runtime collections, REPL evaluation, or leveraging .NET 10/C# 14 features. Covers Span<T>, FrozenDictionary, AggressiveInlining, benchmarking, and allocation reduction strategies.
Dangercoder
tools