Community Triage
roryeckel/wyoming_openai
GitHub issues, pull requests, bug reports, scope questions, and support threads.
Prepares the current DevSpace checkout or worktree for isolated local manual QA, covering QA state seeding, UI asset builds and snapshot resets.
$ npx skills add Waishnav/devspace --skill setup-qa -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Waishnav/devspace setup-qa --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Waishnav/devspace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/setup-qa .claude/skills/setup-qa && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "setup-qa" agent skill from https://github.com/Waishnav/devspace/tree/main/.agents/skills/setup-qa into .claude/skills/setup-qa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-qa", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Waishnav/devspace/tree/main/.agents/skills/setup-qaType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Waishnav/devspace --skill setup-qa -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Waishnav/devspace setup-qa --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Waishnav/devspace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/setup-qa .agents/skills/setup-qa && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "setup-qa" agent skill from https://github.com/Waishnav/devspace/tree/main/.agents/skills/setup-qa into .agents/skills/setup-qa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-qa", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Waishnav/devspace --skill setup-qa -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Waishnav/devspace setup-qa --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Waishnav/devspace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/setup-qa .cursor/skills/setup-qa && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "setup-qa" agent skill from https://github.com/Waishnav/devspace/tree/main/.agents/skills/setup-qa into .cursor/skills/setup-qa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-qa", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Waishnav/devspace.git --path .agents/skills/setup-qa--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Waishnav/devspace --skill setup-qa -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Waishnav/devspace setup-qa --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Waishnav/devspace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/setup-qa .gemini/skills/setup-qa && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "setup-qa" agent skill from https://github.com/Waishnav/devspace/tree/main/.agents/skills/setup-qa into .gemini/skills/setup-qa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-qa", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Waishnav/devspace setup-qaInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Waishnav/devspace --skill setup-qa -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Waishnav/devspace.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/setup-qa .github/skills/setup-qa && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "setup-qa" agent skill from https://github.com/Waishnav/devspace/tree/main/.agents/skills/setup-qa into .github/skills/setup-qa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-qa", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Waishnav/devspace --skill setup-qa -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Waishnav/devspace setup-qa --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Waishnav/devspace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/setup-qa .opencode/skills/setup-qa && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "setup-qa" agent skill from https://github.com/Waishnav/devspace/tree/main/.agents/skills/setup-qa into .opencode/skills/setup-qa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-qa", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
setup-qaPrepares the current DevSpace checkout or worktree for isolated local manual QA, covering QA state seeding, UI asset builds and snapshot resets.
The skill uses the current checkout or worktree and keeps its QA state in `.devspace-dev/` instead of your normal DevSpace state. If the checkout has not been initialized, `pnpm dev:seed` forks your current config, auth, local skills and agents, and SQLite state into that folder. For ChatGPT app, widget, CSS or icon changes, `pnpm build:app` must run first, since the source server serves UI assets from `dist/ui` rather than `src/ui`.
QA itself runs with `pnpm dev`, which starts the source server under `tsx watch` using `.devspace-dev/config`, so server TypeScript changes reload on their own while frontend changes need another build. The seeded state usually lets ChatGPT keep its existing connector and tunnel, and a fresh tool result after a rebuild makes it load the new hashed Vite assets. When a clean copy of your normal state is needed, `pnpm dev:reset` runs with the dev server stopped, and a custom `DEVSPACE_CONFIG_DIR` is preserved.
Read from SKILL.md and the folder at commit 531d3f9. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
pnpmtsxFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
DevSpace Manual QA Setup loads about 440 tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 212 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from Waishnav/devspace at commit 531d3f9, republished under its MIT licence (© Waishnav). 212 words, ~440 tokens.
.claude/skills/setup-qa/SKILL.md (or your agent's skills folder).Use the current checkout or worktree. DevSpace's repo-local QA state lives in .devspace-dev/ and should be used instead of the user's normal DevSpace state.
If this checkout has not been initialized for QA yet:
pnpm dev:seeddev:seed forks the user's current DevSpace config, auth, local skills/agents, and SQLite state into this checkout's .devspace-dev/ directory.
For ChatGPT app, widget, CSS, or icon changes, build the UI assets before testing:
pnpm build:appThe source server serves UI assets from dist/ui, not directly from src/ui.
Start the source server from this checkout with:
pnpm devIt uses .devspace-dev/config and runs the source server under tsx watch, so server-side TypeScript changes reload automatically. Frontend changes still need another pnpm build:app.
The seeded QA state usually lets ChatGPT keep using the existing connector and tunnel while switching from the installed DevSpace server to this checkout's server.
For UI work, trigger a fresh tool result after rebuilding so ChatGPT loads the new hashed Vite assets.
Only when a fresh fork of the normal DevSpace state is needed:
pnpm dev:resetRun this with pnpm dev stopped, then start pnpm dev again so the replaced snapshot is loaded. If the user's normal installation uses a custom DEVSPACE_CONFIG_DIR, preserve it while running dev:seed or dev:reset.
© Waishnav, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/setup-qa of Waishnav/devspace.
Open the folder on GitHubat commit 531d3f9
DevSpace Manual QA Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| DevSpace Manual QA Setup this skillWaishnav/devspace | 5.2k | — | ~440 | Automated safety check: Pass | MIT | |
| Community Triageroryeckel/wyoming_openai | 218 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Worktree StackLanternOps/breeze | 130 | — | ~1.2k | Automated safety check: Notes | AGPL-3.0 | |
| OpenWork Desktop CDP Driverdifferent-ai/openwork | 24k | — | ~465 | Automated safety check: Pass | Custom licence | |
| Nagentdavidondrej/skills | 4.1k | — | ~1.7k | Automated safety check: Notes | MIT | |
| Release Candidate Prepopenai/openai-agents-python | 30k | — | ~4.9k | Automated safety check: Pass | MIT |
roryeckel/wyoming_openai
GitHub issues, pull requests, bug reports, scope questions, and support threads.
LanternOps/breeze
A skill your agent uses when an agent needs a running, seeded, Playwright-ready Breeze stack for the current git worktree.
different-ai/openwork
Drives a running OpenWork desktop window over CDP from the shell to evaluate JS, take screenshots, start sessions and send prompts for hand checks.
davidondrej/skills
Launch a new bb worker thread with the right project, model, worktree, and task brief.
openai/openai-agents-python
Prepare a local Python SDK release candidate in a dedicated worktree.
qixing-jk/all-api-hub
Control, debug, and test the live dev browser extension UI (Options, Popup, Sidepanel) via CDP with persistent login states and accounts.
Waishnav/devspace
Delegates a focused piece of work to a DevSpace subagent through the devspace CLI, picking a target, writing a self-contained brief, and waiting on or continuing the resulting agent.
Categories
Prepares the current DevSpace checkout or worktree for isolated local manual QA, covering QA state seeding, UI asset builds and snapshot resets. devspace-dev/` instead of your normal DevSpace state. If the checkout has not been initialized, `pnpm dev:seed` forks your current config, auth, local skills and agents, and SQLite state into that folder.
DevSpace Manual QA Setup fits situations like: setting up a fresh worktree for manual QA; trying a change in ChatGPT against local DevSpace code; resetting the local QA environment to a fresh copy of your normal state.
Run `npx skills add Waishnav/devspace --skill setup-qa -a claude-code`. Or copy the skill folder (.agents/skills/setup-qa in Waishnav/devspace) into .claude/skills/setup-qa in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Waishnav/devspace --skill setup-qa -a codex`. Or copy the skill folder (.agents/skills/setup-qa in Waishnav/devspace) into .agents/skills/setup-qa in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Waishnav/devspace --skill setup-qa -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/setup-qa, .gemini/skills/setup-qa, .github/skills/setup-qa and .opencode/skills/setup-qa in your project.
Going by SKILL.md and its folder, DevSpace Manual QA Setup needs the command-line tools its instructions call (pnpm and tsx). Our summary lists: pnpm; A DevSpace checkout or worktree; A ChatGPT connector for testing app changes.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
DevSpace Manual QA Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 440 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with DevSpace Manual QA Setup: Community Triage (roryeckel/wyoming_openai, 218 stars), Worktree Stack (LanternOps/breeze, 130 stars), OpenWork Desktop CDP Driver (different-ai/openwork, 24k stars) and Nagent (davidondrej/skills, 4.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Waishnav (a GitHub user) maintains it in Waishnav/devspace, which has 5,205 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 5, 2026.
Source: Waishnav/devspace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.