Read, edit, and refresh Code Trace Tree plugin data (VS Code and JetBrains). Use when the user asks to add/update/remove trace points (line, file, or directory), inspect or modify Code Trace Tree profiles, sync agent-written traces into the IDE, ask the IDE to reload plugin data, or select/navigate to trace points in…
Use when reviewing architecture, refactors, state/data ownership, duplication, code and test structure, failure handling, debug discipline, work-in-progress hygiene, or concurrency policy against Alex's eight fixed invariants.
Generate a high-level TLA+ model from source code (C, C++, Rust, etc.). Analyzes code to understand its purpose, creates abstractions, writes TLA+ specification, and proposes invariants and properties. Use when the user wants to model source code in TLA+, create a formal specification from implementation, or verify…
Resolve which dependency versions are actually installed, from composer show and composer.lock, when diagnosing version-specific behavior such as a method, argument or class that does not exist in the release that is really running. For the PHP runtime itself (version, OS, loaded extensions) use the…
Diagnose iouring performance and correctness problems with uringscope, an eBPF tracer and analyzer. Use when a Linux process that uses iouring shows tail latency, unexplained iou-wrk- thread explosions, suspiciously syscall-heavy behavior, silent buffer corruption, or completions that never arrive, or when strace…
Pull a GitHub Actions xtbench run, extract failing namespaces per language/group, and triangulate whether the root cause is in the shared xt. source test or in a language-specific spec/rewrite.
Investigates firing alerts and incidents and drives root cause analysis across metrics, logs, and traces, prioritizing the alert's runbook. Use when the user mentions alerts, incidents, firing notifications, outages, or asks to find the root cause of a problem — even when they say "something is down", "why did we get…
Fix XML view/fragment issues that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs these rules: no-globals - For ALL global variable access in XML views — sap., jQuery., AND app-namespace globals (e.g., com.example.app.utils.Handler.onPress, my.app.formatter.method) no-ambiguous-event-handler…
A Russian-language diagnostic workflow for OpenClaw, an agent system. It checks areas such as the gateway, memory database, scheduled jobs, tokens, files, and security, and reports possible fixes.
Hand-computes a system's execution with explicit state at each step. Use when debugging races, state machines, async bugs, regressions; stress-testing a fix; scoping features on existing state; or approaching unfamiliar code. Especially useful for bugs involving client/server sequencing, background refreshes, recovery…
A general reverse-engineering toolkit for Windows programs, Android apps, iOS apps, web interfaces, and APIs. Reverse engineering means examining software to understand how it works and, where appropriate, how to modify and rebuild it.
Environment variable validation and configuration verification. Checks that required variables are set, config files parse correctly, ports are available, and system dependencies meet version requirements.
Five-level autonomous self-healing system for OpenClaw Gateway with preflight config validation, persistent learning, reasoning logs, and multi-channel alerts. Features Claude Code as the Level 3 emergency doctor for AI-powered diagnosis and repair.
Local-only MCP server that gives AI coding agents structural understanding of your codebase — symbol graph, blast radius, semantic search, and auto-detected project conventions. Reduces tool calls and tokens for any task that depends on understanding code relationships rather than reading text.
Diagnose why a PR's CI failed — compare the CI definition against the sandbox, classify the failure, and make the minimal repair. Use when a PR is red and you must work out why before changing anything.
Instrument web/web-app code with structured debug logging via a global variable (window.debuglogs). Produces a clean JSON timeline for reproducing and diagnosing bugs. Use when user wants to debug a feature or track down a bug.
Use this skill when the user needs help with Vivado in-system debugging, hardware programming, or debug core configuration. This includes ILA (Integrated Logic Analyzer) configuration and trigger strategies, VIO (Virtual I/O) usage for signal monitoring and control, JTAG-to-AXI Master for AXI transaction generation…
A project-analysis procedure that traces which functions call one another from a program’s entry point. It can present the result as an indented text chain or, when requested, as an HTML, Mermaid, or other visual diagram.
A workflow for investigating database crashes from core dump files, which are saved snapshots of a program's memory after a crash. It uses GDB, a debugger, to inspect threads and call stacks.
A skill for examining RenderDoc capture files and tracing how a selected part of a rendered frame was produced. RenderDoc is a graphics debugging tool, and an RDC file is a saved frame capture.
Analyze codebases using a graph database instead of reading source files. Use when understanding code architecture, finding functions or call patterns, tracing data flow, checking dependencies, or answering "where is X used?" questions. Grafema builds a queryable code graph from static analysis — prefer querying the…
★not rated 35 2mo agoA69 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: