[Requests and ideas] I’d like to share feedback about using the agent-merge skill on Windows.

**Mood:** 😔
**Category:** Requests and ideas

I’d like to share feedback about using the agent-merge skill on Windows.

The overall workflow works, but setup and execution were not smooth compared to macOS/Linux. I hit multiple environment-specific issues before the script could run successfully:

The script assumes bash, gh, and jq are readily available in the same shell environment, which was not true on Windows.
Running via the default bash entry did not reliably expose gh.
Running via Git Bash introduced path-conversion issues for GitHub API endpoints (for example, leading /repos/... paths were rewritten as local filesystem paths).
jq was not available by default in the shell used by the script, and had to be installed and manually added to PATH.
I had to set MSYS_NO_PATHCONV=1 to prevent endpoint/path mangling.
After these fixes, the script worked, but the out-of-box experience on Windows is fragile.

Suggestions to improve Windows compatibility:

Add a Windows-specific preflight check in check-merge-conditions.sh for bash, gh, and jq.
Document the recommended shell explicitly (for example, Git Bash) and required environment variables.
Detect and guard against MSYS path conversion issues (or set MSYS_NO_PATHCONV=1 in-script when safe).
Improve error messages so users can quickly identify whether the failure is tool availability, path conversion, or API/auth related.
This would make agent-merge much more reliable and user-friendly on Windows.

---
| Field | Value |
| --- | --- |
| App version | 1.0.3 |
| OS | Windows 10.0.26200 |
| Theme | Tokyo Night |
| Path | /chat |
| Tenure | Week 6 |

まず check-merge-conditions.sh を読み、Windows 上で bash、gh、jq、Git Bash をどのように呼び出しているかを追跡します。最初に、報告されている PATH と MSYS のパス変換のケースを確認します。Windows ユーザーが明確な事前チェックまたはエラーのガイダンスを受けられ、推奨されるシェルと環境のセットアップが文書化されていれば完了です。

索引モデルが issue の本文から書いたものです。