coalesce-labs/trace-analysis
plugins/debugging/skills/trace-analysis/SKILL.md
Analyze distributed traces and performance issues with Sentry
$ install --global
skillsauthnpx skillsauth add coalesce-labs/catalyst trace-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 1, 2026, 8:47 AM165.1s1 file scanned
SKILL.md
- name:
- trace-analysis
- description:
- Analyze distributed traces and performance issues with Sentry
- disable-model-invocation:
- false
- allowed-tools:
- Task, TodoWrite
- version:
- 1.0.0
Trace Analysis
Investigate distributed traces, transaction performance, and slow requests using Sentry.
Usage
/trace-analysis <trace-id-or-query>
Examples:
/trace-analysis "a4d1aae7216b47ff8117cf4e09ce9d0a"
/trace-analysis "slow API requests to /checkout"
/trace-analysis "traces with >5 second response time"
/trace-analysis "performance issues in payment service"
What This Analyzes
Trace Components
- Transaction spans (API calls, DB queries, external services)
- Timing breakdown per span
- Parent-child span relationships
- Span operations and descriptions
Performance Metrics
- Total transaction duration
- Time spent in each service
- Database query performance
- External API latency
- Network overhead
Bottleneck Identification
- Slowest spans in trace
- Sequential vs parallel operations
- N+1 query detection
- Inefficient operations
Example Analyses
Specific Trace Investigation
/trace-analysis "Analyze trace abc123def456: where's the bottleneck?"
Performance Pattern
/trace-analysis "Why are checkout API requests slow today?"
Service Comparison
/trace-analysis "Compare performance of payment service vs order service"
Database Performance
/trace-analysis "Find traces with slow database queries in user service"
Output Format
Analysis includes:
Trace Overview:
- Transaction name and operation
- Total duration
- Timestamp
- Environment and release
Span Breakdown:
Transaction: POST /api/checkout (2.4s)
├─ Authentication (45ms)
├─ Database Query: SELECT users (120ms)
├─ External API: Payment Gateway (1.8s) ⚠️ SLOW
├─ Database Query: INSERT orders (230ms)
└─ Email Service (180ms)
Performance Insights:
- Slowest operations
- Time distribution (pie chart/percentages)
- Parallel vs sequential execution
- Optimization opportunities
Recommendations:
- Cache frequently accessed data
- Optimize specific queries
- Implement async processing
- Add timeouts for external calls
Advanced Analysis
Multi-Trace Patterns
/trace-analysis "Find common bottlenecks across all slow checkout traces today"
Service Dependencies
/trace-analysis "Map service call chain for failed transactions"
Error Correlation
/trace-analysis "Traces that resulted in errors: what went wrong before?"
Integration Opportunities
With Error Debugging
# Enable debugging plugin (if not already)
/plugin enable catalyst-debugging
# Combine trace and error analysis
> "Show me the trace for the transaction that caused error ISSUE-456"
With Code Changes
After identifying bottleneck:
/catalyst-dev:create-plan "Optimize the slow payment gateway call identified in trace analysis"
Performance Optimization Workflow
1. Identify Slow Transactions
/trace-analysis "transactions with >2s response time in last hour"
2. Analyze Bottlenecks
> "Drill into the slowest trace: which span is the problem?"
3. Root Cause
> "Why is the database query taking 800ms?"
4. Implement Fix
/catalyst-dev:create-plan "Add database index for user lookups based on trace analysis"
5. Verify Improvement
> "After deploy, compare trace durations before and after"
Tips
- Start with aggregates - "slow checkouts" before diving into specific traces
- Look for patterns - One slow trace might be an outlier, many indicate systemic issue
- Check external dependencies - Third-party APIs often cause slowdowns
- Consider concurrency - Sequential operations that could be parallel
- Database queries - N+1 queries, missing indexes, inefficient queries
Context Cost
Plugin uses ~20k tokens. Disable after analysis:
/plugin disable catalyst-debugging
See also: /catalyst-debugging:debug-production-error, /catalyst-debugging:error-impact-analysis
Related Skills
coalesce-labs/phase-remediate
testing
VerifiedTrustedCommunity
Phase-agent that fixes a failing verify verdict so the pipeline self-heals instead of stalling to needs-human (CTL-653). Reads `${ORCH_DIR}/workers/<ticket>/verify.json`, fixes the `findings[]` (every severity:"high" plus the regression_risk drivers) directly via Edit/Write, commits the remediation, and emits `phase.remediate.complete.<ticket>`. The scheduler's router then re-dispatches `verify` to re-check (the verify⇄remediate cycle, cap 3). Dispatched as a `claude --bg` job by `phase-agent-dispatch`, which invokes it via slash command — hence `user-invocable: true`.
14SKILL.mdUpdated May 28, 2026
coalesce-labs/plugins/dev/skills/phase-triage
tools
VerifiedTrustedCommunity
--- name: phase-triage description: Phase agent that triages a Linear ticket — expands acronyms, classifies (feature/bug/docs/refactor/chore), identifies genuine blockers (a semantic second-pass over the backlog — NOT a prose scrape; CTL-838), estimates scope, writes triage.json, and posts a triage analysis comment to Linear. Triage completion is signaled by that comment plus the local triage.json — there is no `triaged` label. Emits phase.triage.complete.<TICKET> on success and phase.triage.fai
14SKILL.mdUpdated May 18, 2026
coalesce-labs/phase-research
tools
VerifiedTrustedCommunity
Phase agent for the research step of the 9-phase orchestrator pipeline (CTL-450). Wraps /catalyst-dev:research-codebase and produces thoughts/shared/research/<date>-<ticket>.md, then emits phase.research.complete.<ticket>. Reads triage.json from the worker dir as its prior-phase artifact. Spawned via plugins/dev/scripts/phase-agent-dispatch, which invokes it via slash command — hence `user-invocable: true`.
14SKILL.mdUpdated May 18, 2026
coalesce-labs/phase-pr
development
VerifiedTrustedCommunity
Phase-agent wrapper that opens the pull request after implementation completes (CTL-449 Initiative 1 Phase 3). Delegates to `/catalyst-dev:create-pr` (which already auto-runs `describe-pr` and transitions Linear to `inReview`), then writes the PR number + URL into the phase signal file so the downstream `phase-monitor-merge` agent can read it without re-querying GitHub. Dispatched as a `claude --bg` job by `phase-agent-dispatch`, which invokes it via slash command — hence `user-invocable: true`.
14SKILL.mdUpdated May 18, 2026