setup-qa

Featured

Prepare the current DevSpace checkout or worktree for isolated local manual QA. Use when the user asks to set up QA, test a worktree locally, try an experiment in ChatGPT, or reset the local QA environment.

AI & Automation 4,646 stars 527 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
76
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Set up DevSpace manual QA 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. ## Prepare the checkout If this checkout has not been initialized for QA yet: ```bash pnpm dev:seed ``` `dev: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: ```bash pnpm build:app ``` The source server serves UI assets from `dist/ui`, not directly from `src/ui`. ## Run QA Start the source server from this checkout with: ```bash pnpm dev ``` It 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. ## Reset the QA snapshot Only when a fresh fork of the normal DevSpace state is needed: ```bash pnpm dev:reset ``` Run 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` o...

Details

Author
Waishnav
Repository
Waishnav/devspace
Created
2 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

DevOps & Infrastructure Listed

local-qa

Run local QA including formatting and linting for the repository. Use whenever any file has been updated.

2 Updated 1 weeks ago
dceoy
Testing & QA Listed

rc-qa-execution

Executes full-project QA like a real user by discovering the repository verification and E2E contracts, running build, lint, test, and startup commands, exercising core workflows end-to-end through CLI, HTTP, and browser interfaces, requiring automated regression coverage for supported critical flows, fixing root-cause regressions, and rerunning the full gate. Uses the agent-browser companion skill for Web UI validation when a web surface exists. Use when validating a branch, release candidate, migration, refactor, or risky commit. Do not use for static code review only, one-off unit test edits, planning test cases, or architecture brainstorming without execution.

19 Updated 1 months ago
rodolfochicone
Testing & QA Solid

qa

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.

14 Updated 2 days ago
HyperAITeam