sync-health-monitor — Claude Code command: GitHub-Linear sync
A slash command that checks GitHub-Linear sync health: API limits, webhooks, latency, error patterns. Useful when issues stop reaching the other side.
npx claude-code-templates@latest --command sync/sync-health-monitorWhat sync-health-monitor does
The command reads the current sync environment: remaining GitHub API rate limit via gh api rate_limit, Linear MCP server status and auth, active webhooks, and event processing metrics. Then it runs diagnostics across six areas: API health, throughput and latency, recurring failures, webhook delivery, data integrity, and automated recovery steps.
Scope comes from the argument: --github, --linear, --webhooks, --performance or --report. Leave it out and you get the general health pass. Output is a report with metrics, error breakdown and suggested fixes.
You need the gh CLI configured and a Linear MCP server authenticated. If the GitHub API check fails, the command just notes that a check is needed and moves on — worth sorting out your token and rate limit before you rely on the report.
What it helps with
- see how many GitHub API requests are left
- confirm the Linear MCP server is authenticated
- spot recurring sync failures and their types
- test webhook delivery and processing latency
- find orphaned records after a failed sync
Example prompts for the agent
- /sync-health-monitor --report
- /sync-health-monitor --webhooks
- /sync-health-monitor --performance
How to install sync-health-monitor
1claude-code-templates
npx claude-code-templates@latest --command sync/sync-health-monitor2Manually: put the files in place
.claude/commands/sync-health-monitor.mdCall it with /sync-health-monitor. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/sync-health-monitor.mdCall it with /prompts:sync-health-monitor. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/sync-health-monitor.prompt.mdManually: put the files in place
.gemini/commands/sync-health-monitor.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about sync-health-monitor
How do I install sync-health-monitor in Claude?
Use the templates installer: npx claude-code-templates@latest --command sync/sync-health-monitor. The command file lands at .claude/commands/sync-health-monitor.md.
What does sync-health-monitor do?
It checks GitHub-Linear sync health: API rate limits, Linear connectivity, webhooks, latency and error patterns. You get a report with metrics and recommended fixes.
What does sync-health-monitor need to run?
A configured gh CLI and an authenticated Linear MCP server. Without them the GitHub API and Linear checks won't go through.
Source text
sync-health-monitor.md · MIT
--- allowed-tools: Read, Write, Edit, Bash argument-hint: "[scope] | --github | --linear | --webhooks | --performance | --report" description: Monitor and diagnose GitHub-Linear sync health with performance analytics and automated troubleshooting --- # Sync Health Monitor Monitor comprehensive GitHub-Linear synchronization health and performance: **$ARGUMENTS** ## Current Sync Environment - GitHub API status: !`gh api rate_limit -q '.rate | "GitHub: \(.remaining)/\(.limit) requests"' 2>/dev/null || echo "GitHub API check needed"` - Linear connectivity: Linear MCP server status and authentication validation - Webhook status: Active webhook configurations and event processing health - Sync performance: Current throughput, latency metrics, and error rates ## Task Implement comprehensive sync health monitoring with automated diagnostics and performance optimization: **Monitor Scope**: Use $ARGUMENTS to specify GitHub health, Linear connectivity, webhook diagnostics, performance analysis, or complete health report **Health Monitoring Framework**: 1. **API Health Assessment** - Monitor GitHub/Linear API status, rate limits, authentication, connectivity issues 2. **Sync Performance Analysis** - Track throughput metrics, latency patterns, processing times, queue depths 3. **Error Pattern Detection** - Identify recurring failures, classify error types, analyze failure trends 4. **Webhook Diagnostics** - Validate webhook configurations, test event delivery, monitor processing latency 5. **Data Integrity Validation** - Verify sync consistency, detect orphaned records, validate cross-references 6. **Automated Troubleshooting** - Run diagnostic tests, suggest fixes, implement automated recovery procedures **Advanced Features**: Real-time health dashboards, predictive failure detection, automated recovery workflows, comprehensive performance profiling. **Diagnostic Capabilities**: Deep error analysis, bottleneck identification, configuration validation, automated testing suites. **Output**: Complete health assessment with performance metrics, error analysis, recommended optimizations, and automated diagnostic reports.
© davila7 · MIT · davila7/claude-code-templates