remote-fix

Guide an AI through diagnosing, fixing, and reporting remote issues via PRs.

5|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/rbah31/claude-code-workflow --skill remote-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remote-fix
Source: https://github.com/rbah31/claude-code-workflow/tree/main/.claude/skills/remote-fix
Command: npx skills add https://github.com/rbah31/claude-code-workflow --skill remote-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remote fix workflow. Receives a diagnostic (from Cowork scheduled task, manual observation, or user report), investigates the issue, fixes it, and creates a PR. Designed for quick fixes triggered remotely via Channels (Discord/Telegram). Use when the user says "fix this", "handle this diagnostic", "the scheduled task found X", or sends a Cowork diagnostic summary.

Core Features & Use Cases

  • Step 1 — Understand the diagnostic
  • Step 2 — Investigate
  • Step 3 — Fix
  • Step 4 — PR and report
  • Step 5 — Verify (after merge)
  • Gotchas
  • You're being commanded from a phone. Keep responses SHORT.
  • Don't start a full sprint cycle. This is a surgical fix.
  • If you're not sure, SAY SO. Better to wait than ship a bad fix.
  • Never force-push to main. Always PR, always wait for merge.
  • The human may take hours to respond (they're at work). That's normal. Don't spam updates.
  • If the diagnostic mentions multiple issues, fix only the most critical one. Add the rest to tasks/backlog.md.

Quick Start

Provide a diagnostic summary and instruct the AI to initiate the remote fix workflow following the five steps.

Frequently Asked Questions about remote-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate remote diagnostic fixes and create a pull request?

Automating remote diagnostic fixes requires investigating the issue, applying a targeted code change, and creating a branch-based pull request. This workflow ensures surgical fixes are tracked, safely reviewed, and merged without force-pushing to main.

How can I trigger code fixes from Discord or Telegram diagnostic summaries?

Triggering code fixes from chat platforms requires sending a diagnostic summary to the AI. The system interprets the diagnostic, investigates the root cause, applies a single critical fix, and generates a pull request report directly in the channel.

What is the best way to handle multiple issues found during a remote diagnostic scan?

When a remote diagnostic reports multiple issues, the best approach is to fix only the most critical one to maintain a single-fix policy. Remaining issues should be documented in a tasks backlog file for future investigation and resolution.

Does remote automated fix workflow support post-merge verification?

Yes, automated remote fix workflows support post-merge verification to ensure the pull request resolves the original diagnostic. After the PR merges, the system verifies the fix and reports the final status back through the remote channel.

When should I avoid using an automated remote fix workflow?

You should avoid automated remote fixes if you are unsure about the root cause, as shipping a bad fix is worse than waiting. Additionally, do not use it for full sprint cycles; it is designed only for surgical, single-issue fixes with strict branch policies.