wf0-remote_skill

Overview

This skill enables remote workflow monitoring and execution through GitHub Issue comments. It runs a daemon on your workstation (tmux session) that polls issue comments and executes approved workflow steps, letting reviewers approve progress from mobile while the PC performs actions. Auto mode can discover and process labeled issues in bulk, including a revision flow for PR feedback.

How this skill works

Targets are resolved from state.json (work IDs, patterns, or --all) and the skill launches a tmux session per work that polls the linked GitHub issue. Issue comments from authorized collaborators containing the whitelist commands (e.g., /approve, /next, /pause, /stop) control the daemon. State is recorded in state.json and auto mode maintains .wf/auto.json to track session and progress.

When to use it

• Enable mobile approval for CI steps where a human must confirm each change.
• Run long-running or multi-step local workflows while reviewers use GitHub Issues to drive progress.
• Batch-process many repository issues via auto mode (label-based discovery).
• Handle PR revision cycles automatically by prioritizing needs-revision labeled issues.

Best practices

• Keep state.json backed up and under repository control to avoid drift between runs.
• Limit auto mode --max and set cooldown to avoid GitHub rate limits.
• Restrict collaborator permissions on the repo to trusted accounts (admin/write/maintain) since only those comments are processed.
• Run the daemon inside tmux and name sessions as wf-remote-<work-id> for easy management.
• Use the --dry-run option when tuning auto queries to validate targets before execution.

Example use cases

• Start monitoring a single work: /wf0-remote start FEAT-123 to enable mobile approvals for that issue.
• Stop monitoring several works: /wf0-remote stop FEAT-* to kill sessions and mark remote.disabled.
• Auto-discover and process up to 3 issues: /wf0-remote auto --max 3 --cooldown 10 --dry-run to preview work.
• Trigger a revision cycle automatically when a reviewer adds the needs-revision label to a completed issue.