Maintainer of this skill?
# Add to your Claude Code skills
git clone https://github.com/jsmastery-pro/jsm-hqSee how jsm-hq compares with popular alternatives.
jsm-hq is an open-source devops skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by jsmastery-pro. It has 54 GitHub stars.
jsm-hq's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/jsmastery-pro/jsm-hq" and add it to your Claude Code skills directory (see the Installation section above).
jsm-hq is primarily written in TypeScript. It is open-source under jsmastery-pro on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other DevOps skills you can browse and compare side by side. Open the DevOps category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh jsm-hq against similar tools.
No comments yet. Be the first to share your thoughts!
Top skills in this category by stars
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
Run a team of AI coding agents on your repo, and watch them work in a pixel-art office.
One lead agent plans the work and hands out tasks. Each worker gets its own desk, its own copy of your repo and its own Docker Sandbox, then opens a pull request. You see it all happen: the plan on the wall, agents at their desks, PRs moving through review.
Agents run Claude Code or Codex. Everything runs on your machine.
From inside a git repo that has a GitHub remote:
npx @therealjsmastery/jsm-hq@latest
HQ opens in your browser and walks you through the rest:
First time? The getting-started guide takes you from a fresh machine to a working team in about 15 minutes, on macOS, Linux and Windows.
Just trying it? Use a throwaway repo:
mkdir hq-test && cd hq-test
git init -b main && echo "# HQ test" > README.md && git add . && git commit -m init
npx @therealjsmastery/jsm-hq@latest
jsm-hq --repo <path> the repo to manage (default: current folder)
--port <n> HQ port (default: 7420)
--no-open don't open the browser
--version, --help
Use it often? npm install -g @therealjsmastery/jsm-hq, then run jsm-hq in any repo.
| What | Why |
|---|---|
| Node.js 20+ | Runs HQ |
| git and a GitHub repo | Each agent clones it, pushes a branch and opens a PR |
GitHub CLI (gh) |
Reads PRs and reviews |
Docker Sandboxes (sbx) |
Each agent runs in its own VM |
| tmux (macOS, Linux) | Agents keep running if you close HQ |
| A Claude or ChatGPT account | For the agents themselves |
Sandboxes need macOS 14+ on Apple silicon, Windows 11, or Ubuntu 24.04+. On other machines, set agents to Local in Settings → Team: they run Claude Code or Codex directly on your machine, with permission prompts on.
You don't need to install these by hand first. HQ checks for each one and shows the exact command. The getting-started guide has every step.
main, makes a branch, writes the code and opens a PR titled [TASK-ID] ….Click any agent to open its drawer: its live terminal, a shell inside its sandbox, its task, its messages, and the websites it tried to reach. Drag the drawer's edge to make it wider, or maximize it. Terminal in the top bar opens your own shell in the repo or any agent's folder.
More detail on workspaces, sandboxes, MCP servers, app variables and what HQ saves: How it works.
| Problem | Fix |
|---|---|
| A setup check shows "!" but the tool works | You may be on an old HQ. Run npx @therealjsmastery/jsm-hq@latest (npx can keep an old version cached). |
| Start fails: "network policy has not been initialized" | A new Docker Sandboxes install needs a base policy once: sbx policy init balanced. |
| Agents fail to start with a sign-in error | Your Docker sign-in expired. Run sbx login, then Check again in the setup checklist. |
| Agents can't push or open PRs | Run sbx secret set github --command "gh auth token", and check the repo has a GitHub origin. |
| A Codex agent waits on "Do you trust this folder?" | Answer it once in the agent's terminal. HQ never answers trust prompts for you. |
A CLI sign-in in a sandbox opens the browser, then fails on localhost:<port> |
Press Forward port in the agent's drawer, then reload the page. |
| An agent's state never changes | The sandbox can't reach HQ. sbx policy ls should show localhost:<port> and host.docker.internal:<port> allowed; HQ adds them on start. |
| "Port 7420 is in use" | Another HQ is running. Stop it, or use --port 7421. |
Windows: listen EACCES on start |
Windows reserved that port. Use --port 8420. |
posix_spawnp failed when opening a terminal |
Run npx clear-npx-cache, then npx @therealjsmastery/jsm-hq@latest. |
Remove a project: delete each agent in Settings → Team (this removes its sandbox and, if you choose, its folder), then delete ~/.jsmhq/<project>.
Code: MIT. The JSM HQ name and logo are not covered by the license; see TRADEMARKS.md.