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/migrate-dual-harness
development
VerifiedTrustedCommunity
Migrate a single-harness repo to the dual-harness layout so both Claude Code and Codex load the same instructions and skills — AGENTS.md as the portable canonical doc, a thin CLAUDE.md `@AGENTS.md` bridge, and a `.agents/skills` dir with a `.claude/skills` symlink onto it. Use when asked to migrate to dual-harness, make this repo work in both Claude and Codex, or for agent metadata cleanup.
17SKILL.mdUpdated Jul 27, 2026
coalesce-labs/recovery-pass
tools
VerifiedTrustedCommunity
Goal-driven senior-engineer pipeline-unstick sweep (CTL-1176 rung 3). Given the stuck/failed/needs-human set (or ONE ticket handed by the recovery router), its GOAL is to get the pipeline MOVING again — not to fix one ticket's review findings (that is phase-remediate). It runs AFTER the eyes (diagnostician evidence) and the hands (deterministic unstuck-sweep seams) have already tried, and it CONSUMES their output from a recovery-pass.json brief rather than re-diagnosing or redoing their narrow work. It acts like a senior engineer with full tool access — it resolves merge conflicts, rebases, force-pushes, merges green PRs, and re-dispatches stalled phases AUTONOMOUSLY — and escalates to the operator ONLY for a genuine value judgment / something that degrades other functionality / a real cost-benefit trade-off / a serious architecture change / an ADR conflict. On escalation it AUTHORS the operator inbox row + the push notification (executive-voiced). Dispatched as a `claude --bg` job by phase-agent-dispatch via slash command, AND invocable bare by the operator as a sweep — hence `user-invocable: true`. Ships behind CATALYST_RECOVERY_PASS (off by default — no live behavior change until shadow/enforce).
17SKILL.mdUpdated Jun 18, 2026
coalesce-labs/setup-catalyst
tools
VerifiedTrustedCommunity
Diagnose and fix Catalyst setup issues. Validates tools, database, config, OTel, direnv, and thoughts. Automatically fixes what it can — creates directories, initializes the database, sets WAL mode, runs migrations. Use for new installs, upgrades, or when something isn't working.
17SKILL.mdUpdated Jun 7, 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
17SKILL.mdUpdated May 18, 2026