Menu
Debugging universal. Tests, FlowTrace, profiling, estrategias hibridas. Clasifica el bug y selecciona la estrategia optima.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Testing strategy, patterns, and coverage optimization for quality assurance. Use this skill whenever the task involves deciding what to test, how to structure tests, what coverage to aim for, when to use mocks vs real dependencies, or how to write tests that actually catch bugs (not just pass). Also use when the user asks about test pyramids, flaky tests, integration vs unit, TDD, or improving an existing test suite.
Production readiness validation — runs all checks before merging or deploying. Use this skill whenever the task involves verifying that code is ready to ship: type checking, linting, tests passing, coverage thresholds, dead code, security issues, or any pre-merge checklist. Also use when the user asks "is this ready?", wants a pre-PR review, or needs to confirm nothing is broken after a refactor.
Swift architecture reference — SwiftUI, UIKit, Combine, async/await, actors, and production best practices for Swift 5.9/6.0 (2024-2025). Use when making architectural decisions, reviewing Swift code, or selecting libraries. Also use when the user mentions iOS development, macOS apps, or Apple platform development.
UI/Frontend architecture reference - React 19, Next.js 15, Vue 3, Svelte 5, Angular 19, CSS modern features, component libraries, state management, and production best practices for 2024-2025. Use when building frontend UIs, selecting frameworks, reviewing component code, or making frontend architecture decisions.
UX design reference - research methods, design systems, accessibility (WCAG 2.2, EAA), UX laws, AI-driven workflows, tools (Figma, Penpot), and production best practices for 2024-2025. Use when making UX decisions, reviewing designs, implementing accessibility, selecting design tools, or applying UX principles.
C# architecture reference - frameworks, design patterns, ASP.NET Core, Entity Framework, Blazor, Unity, and production best practices for C# 12/13 and .NET 8/9 (2024-2025). Use when making architectural decisions, reviewing C# code, or selecting libraries.
| name | debug |
| description | Debugging universal. Tests, FlowTrace, profiling, estrategias hibridas. Clasifica el bug y selecciona la estrategia optima. |
| user-invocable | true |
| argument-hint | [help|debug|profile|test|status|clean] |
Framework de debugging universal multi-estrategia. Clasifica el tipo de bug y selecciona la herramienta optima: tests, FlowTrace, profiling, o combinaciones.
Parsea $ARGUMENTS para determinar la accion:
Muestra las herramientas organizadas:
Universal Debugger - Multi-Strategy
NATIVAS (siempre disponibles):
Read, Glob, Grep — Leer y buscar codigo fuente
Bash — Ejecutar tests, profilers, build tools
Write, Edit — Modificar codigo (solo en fase fix)
TEST FRAMEWORKS (auto-detectados):
cargo test — Rust (Cargo.toml)
npm test / vitest — Node.js (package.json)
go test — Go (go.mod)
pytest — Python (pyproject.toml)
dotnet test — .NET (*.csproj)
rspec / rake test — Ruby (Gemfile)
FLOWTRACE MCP (cuando disponible):
AUTOMATIZACION:
flowtrace.detect — Detectar lenguaje y framework
flowtrace.init — Inicializar FlowTrace en proyecto
flowtrace.build — Compilar proyecto
flowtrace.execute — Ejecutar con instrumentacion
flowtrace.cleanup — Limpiar logs
flowtrace.status — Estado del proyecto
ANALISIS DE LOGS:
log.open — Cargar JSONL, obtener sessionId
log.schema — Descubrir campos y fila de ejemplo
log.search — Filtrar filas por substring
log.timeline — Eventos cronologicos
log.sample — Muestras representativas
log.topK — Top N valores de un campo
log.aggregate — Agrupar y calcular count/sum/avg/max/min
log.flow — Correlacionar eventos por claves compuestas
log.errors — Auto-detectar patrones de error
log.export — Exportar a CSV/JSON
log.expand — Recuperar datos completos de entradas truncadas
log.searchExpanded — Buscar con auto-expansion
DASHBOARD DE PERFORMANCE:
dashboard.open — Analizar archivo + URL de dashboard
dashboard.analyze — Metricas JSON de performance
dashboard.bottlenecks— Top N por score de impacto
dashboard.errors — Hotspots de errores
ESTRATEGIAS POR TIPO DE BUG:
Serializacion/Data — Roundtrip tests, schema validation
Logica/Flujo — Unit tests + assertions
Performance — FlowTrace profiling o profilers nativos
Concurrencia — Stress tests + sanitizers + FlowTrace timeline
Integracion — FlowTrace + request replay
Memoria — Heap profiling + sanitizers
Activa el workflow graph para debugging estructurado:
graph_activate("debug-graph")
El workflow guia paso a paso:
Analisis enfocado en performance:
flowtrace.status -> verificar que hay logsdashboard.analyze con path al jsonl -> metricas completasdashboard.bottlenecks top 10 -> metodos con mayor impactodashboard.errors -> hotspots de erroreslog.aggregate por clase/metodo, metric avg durationMillis -> desgloselog.topK byField durationMillis, k=20 -> outlierscargo bench, flamegraph, criterion--prof, clinic.js, 0xcProfile, py-spypprof, go test -benchDetecta test framework y ejecuta tests:
Cargo.toml -> cargo test [filter]package.json -> buscar script "test", o npx vitest run [filter], o npx jest [filter]go.mod -> go test ./... -run [filter]pyproject.toml -> pytest [path] -k [filter]*.csproj -> dotnet test --filter [filter]debug si hay fallos complejosflowtrace.status con projectPath (si FlowTrace disponible)flowtrace.cleanup con projectPath (si FlowTrace disponible)FlowTrace NO es un MCP directo del agente. Se accede a traves del proxy execute_mcp_tool del workflow-manager:
execute_mcp_tool(
mcp_name="flowtrace",
tool_name="flowtrace_detect",
arguments={"projectPath": "/path/to/project"}
)
Los nombres de tools usan underscores: flowtrace_detect, flowtrace_init, log_open, log_search, dashboard_bottlenecks, etc.
/home/rixmerz/my_projects/flowtrace-debugger/mcp-server/flowtrace.jsonl en el directorio del proyecto