Results for “runtime-analysis”

Diagnose failures from runtime evidence before editing code.

Catches type errors before runtime using static type checking with gradual typing, strict mode, and Protocol support for Python projects.

Mounts a fetch-native CopilotRuntime on any JS server, wires middleware, selects an AgentRunner, and integrates built-in or external agent frameworks.

runtime-and-process

Generates detailed, technology-agnostic implementation blueprints by analyzing project architecture, technology stacks, and data flow patterns.

Analyze a screen recording of a manual process and produce targeted, working automation scripts. Extracts frames and audio narration from video files, reconstructs the step-by-step workflow, and proposes automation at multiple complexity levels using tools already installed on the user machine.

Systematically profile Node.js, Python, and Go applications to identify CPU, memory, and I/O bottlenecks, generate flamegraphs, analyze bundle sizes, optimize database queries, and run load tests with k6 and Artillery.

Analyzing session replays, extracting persona-based behavioral patterns, and storytelling UX issues. Reads the 'why' from real user operation logs. Works with Field/Echo for persona validation.

Analyzes game AI systems in a codebase, covering behavior trees, finite state machines, GOAP, utility AI, pathfinding, steering, perception, difficulty adaptation, NPC dialogue, and AI debugging tools for Unity, Unreal, and Godot projects.

AL debugging and diagnostics for Business Central. Use when performing snapshot debugging, CPU profiling, analyzing telemetry, or troubleshooting runtime issues.

Performance regression detection using the browse daemon. Establishes baselines for page load times, Core Web Vitals, and resource sizes. Compares before/after on every PR. Tracks performance trends over time. Use when: "performance", "benchmark", "page speed", "lighthouse", "web vitals", "bundle size", "load time". (gstack) Voice triggers (speech-to-text aliases): "speed test", "check performance".

Retro

Performance profiling principles. Measurement, analysis, and optimization techniques.

Resume an interrupted AgenTeam run with verify-first strategy.

Weekly engineering retrospective. (gstack)

A runbook written in a wiki decays silently: the dashboard is renamed, the

Analyze sprint retrospectives for patterns and action item tracking. Usage: /retro analyze <retro_data.json>

Long Tasks

Most teams run one test — expected peak for ten minutes — and believe they have

Reverse-engineers custom JavaScript-based WASM virtual machines and risk-control engines by identifying DSL VM patterns, extracting opcodes, analyzing constant tables, and tracing exported functions through static analysis and runtime injection.

Analyzes core dumps and live processes with GDB, correlating source code with runtime state to diagnose crashes, deadlocks, and memory issues in C/C++ programs.

Tests and debugs web applications in real browsers using Chrome DevTools MCP, enabling DOM inspection, console error capture, network analysis, performance profiling, and visual verification with live runtime data.

Use when investigating a bug, runtime error, unexpected behavior, test failure, or crash. For systematic root cause analysis, error message interpretation, stack trace reading, reproduction steps, and targeted fixes. Activate when the user says "it's broken", "this doesn't work", "I'm getting an error", or "help me debug".

Operations, debugging, and optimization for DAG workflows. Performs root cause analysis on failures, profiles execution performance, aggregates results from parallel branches, bridges context between nodes, and learns patterns from execution history. Activate on "DAG failed", "why did it fail", "root cause", "performance profile", "aggregate results", "merge branches", "execution patterns", "optimize DAG". NOT for planning DAGs (use dag-planner), executing DAGs (use dag-runtime), or validating outputs (use dag-quality).