coalesce-labs/error-impact-analysis
plugins/debugging/skills/error-impact-analysis/SKILL.md
Analyze the impact and scope of production errors
$ install --global
skillsauthnpx skillsauth add coalesce-labs/catalyst error-impact-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, 3:12 AM227.6s1 file scanned
SKILL.md
- name:
- error-impact-analysis
- description:
- Analyze the impact and scope of production errors
- disable-model-invocation:
- false
- allowed-tools:
- Task, TodoWrite
- version:
- 1.0.0
Error Impact Analysis
Assess the severity, reach, and business impact of production errors.
Usage
/error-impact-analysis <error-or-timeframe>
Examples:
/error-impact-analysis "ISSUE-789"
/error-impact-analysis "checkout errors last 7 days"
/error-impact-analysis "critical errors this week"
/error-impact-analysis "impact of recent deployment"
What This Analyzes
Quantitative Impact
- Number of occurrences
- Number of users affected
- Error rate over time
- Affected environments/releases
Qualitative Impact
- Error severity (critical, high, medium, low)
- Affected user workflows
- Business function impact (checkout, signup, etc.)
- User experience degradation
Trend Analysis
- Is it increasing or decreasing?
- When did it start?
- Related to specific release?
- Correlation with traffic/usage
Example Analyses
Single Issue Impact
/error-impact-analysis "What's the impact of MYAPP-123? How many users, revenue impact?"
Category Impact
/error-impact-analysis "Overall impact of all payment-related errors this month"
Release Health
/error-impact-analysis "Error impact comparison: current release vs previous release"
Critical Errors
/error-impact-analysis "Show all critical errors and their combined user impact"
Output Format
Analysis includes:
Scope:
- Total occurrences
- Unique users affected
- Affected countries/regions
- Browser/device breakdown
Severity Assessment:
- Error frequency
- User impact score
- Business criticality
- Blocking vs non-blocking
Trends:
- Occurrence over time (chart/data)
- Peak times
- Growth rate
- Comparison to baseline
Business Impact:
- Affected revenue-generating flows
- Customer support tickets related
- SLA implications
- Reputation risk
Prioritization:
- Recommendation on urgency
- Comparison with other errors
- ROI of fixing
Integration with Analytics
Enable both plugins for deeper impact analysis:
/plugin enable catalyst-debugging
/plugin enable catalyst-analytics
/error-impact-analysis "How many users who hit error X churned vs users who didn't?"
This combines:
- Sentry error data (who hit the error)
- PostHog behavior data (did they churn)
Incident Response Workflow
1. Assess Impact
/error-impact-analysis "new spike in errors at 3pm"
2. Determine Severity
Based on output:
- Critical: >1000 users, blocking checkout/signup
- High: >100 users, degraded experience
- Medium: <100 users, minor inconvenience
- Low: <10 users, edge case
3. Prioritize Response
> "Based on this impact, should we rollback or hotfix?"
4. Track Resolution
> "After fix, compare error rates before and after"
Tips for Impact Analysis
- Consider timeframe - "last hour" for incidents, "last week" for trends
- Segment users - Impact on paid vs free users may differ
- Check related errors - One root cause may affect multiple error types
- Compare releases - Pinpoint when impact started
- Business context - Impact during peak hours is more severe
Context Cost
Plugin uses ~20k tokens. Disable after analysis:
/plugin disable catalyst-debugging
See also: /catalyst-debugging:debug-production-error, /catalyst-debugging:trace-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