OpenHands / OpenHands/extensions
[fix]: make GitHub skills work cleanly on Windows, macOS, and Linux
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 148
- Forks
- 90
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 36
Description
Problem
GitHub-related skills in extensions still include POSIX/bash-specific setup patterns (/tmp, heredocs, mkdir -p, ar -czf, python3, sed, grep). Even after the filename fixes in #317, native Windows is still not an out-of-the-box experience.
Scope
- Update github, github-pr-review, github-pr-reviewer, and github-repo-monitor`n- Remove bash-only setup paths as the default
- Prefer shell-neutral instructions, Python/file-editor flows, or dual PowerShell + bash examples
- Avoid /tmp and other POSIX-only path assumptions
Goal
A user on Windows, macOS, or Linux can use these GitHub skills in Agent Canvas without WSL, Git Bash, or manual shell translation.
Out of scope
Automation runtime/bootstrap changes.
Likely this issue will take care of that https://github.com/OpenHands/automation/issues/178
This issue was created by an AI agent (OpenHands) on behalf of the user.
And the human user edited this too. And read it.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the definitions for the github, github-pr-review, github-pr-reviewer, and github-repo-monitor skills, then inspect their setup instructions for /tmp, heredocs, mkdir -p, tar, python3, sed, and grep. Replace default POSIX-only paths with shell-neutral or cross-platform guidance, and verify that the four skills can be followed on Windows, macOS, and Linux without WSL or manual translation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, powershell, python
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100