setup · fcakyon, qa — Claude Code skill: what it does, how to install
Skill for Claude Code configures real integration testing and user QA journeys across project codebases. It triggers when asked to set up QA or generate end-to-end testing flows.
Apache-2.0 ★ 1,216 updated 2026-11-16
/plugin marketplace add fcakyon/claude-codex-settings
/plugin install qa@claude-settingsWhat setup does
This skill sets up end-to-end QA harnesses across websites, extensions, backends, Android projects, and macOS native apps. The workflow starts by running project-qa discover to inspect routes, package manifests, and existing test suites for candidate coverage.
Next, project-qa setup builds .agents/qa/config.json, .agents/qa/suite.mjs, and .agents/skills/qa/SKILL.md while leaving existing custom files intact. Generated placeholders are replaced with real user journeys and real fixtures, removing mocked transport layers only after live flows verify the contract.
Node.js and the runner scripts inside the plugin root are required for execution. Native macOS applications require running Swift suites in a native macOS CI job, and UI verification requires inspecting actual journey screenshots.
What it helps with
- bootstrap an end-to-end QA harness for a project
- generate
.agents/qa/config.jsonand thesuite.mjstest runner - scan project routes and manifests using
project-qa discover - wire native macOS Swift suites into CI test pipelines
Example prompts for the agent
- Set up QA for this backend and web interface
- Create real integration tests for the browser extension
- Add project QA journeys for the macOS application
How to install setup
1Plugin marketplace
/plugin marketplace add fcakyon/claude-codex-settings/plugin install qa@claude-settingsThis installs the whole qa plugin with all its skills
2Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill setup -a claude-code3Manually: put the files in place
~/.claude/skills/setup/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/setup/
1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill setup -a codex2Manually: put the files in place
.agents/skills/setup/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill setup -a cursor2Manually: put the files in place
.cursor/skills/setup/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install fcakyon/claude-codex-settings plugins/qa/skills/setup2Manually: put the files in place
.github/skills/setup/SKILL.md1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill setup -a gemini-cli2Platform CLI
gemini skills install https://github.com/fcakyon/claude-codex-settings --path plugins/qa/skills/setupManually: put the files in place
.devin/skills/setup/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about setup
How to install setup in Claude Code?
Run /plugin marketplace add fcakyon/claude-codex-settings followed by /plugin install qa@claude-settings. You can also install it directly via npx skills add fcakyon/claude-codex-settings --skill setup -a claude-code.
What does the setup skill do?
It scans repositories using project-qa, locates untested routes, and generates .agents/qa configuration files. Once generated, it helps convert blocked template cases into working integration journeys.
What is required for the setup skill to run?
It requires running npm ci --prefix <plugin-root> and accessing node <plugin-root>/scripts/qa.mjs directly or via npm link. When running CI as root over external checkouts, the path must be added to git's safe.directory.
Source text
SKILL.md · Apache-2.0
--- name: setup description: This skill should be used when user asks to "set up QA", "create real integration tests", or "add project QA journeys" for websites, extensions, Android apps, native macOS apps or backends. --- # Set up project QA The plugin supplies the runner. The project owns journeys, selectors, fixtures and outcome assertions. Execution belongs in tracked scripts. Skills guide discovery and interpretation. 1. Run `npm ci --prefix <plugin-root>` once. Use `node <plugin-root>/scripts/qa.mjs` directly, or `npm link` from the plugin directory to install `project-qa`. In CI, pin the plugin to a commit and bump it on purpose. When CI runs as root over a checkout owned by another user, add it to git's `safe.directory`, or reports record an empty revision and a clean tree. 2. Run `project-qa discover --root <repo>`. Read the owning routes, callers, test commands, manifests and related repositories. Discovery identifies candidate coverage, not working features. 3. Run `project-qa setup --root <repo> --base-url <verified-url>`, adding `--extension <built-directory>` and repeated `--related <relative-repo>` where relevant. It creates `.agents/qa/config.json`, `.agents/qa/suite.mjs` and `.agents/skills/qa/SKILL.md`. Existing files are preserved. Discovery evidence stays in command output, so runtime configuration does not become a stale copy of package manifests. 4. Replace generated blocked cases with real journeys using [the API](../../references/runner.md) and [surface requirements](../../references/surfaces.md). Reuse existing integration tests before writing another owner for the same contract. 5. Configure [sessions](../../references/sessions.md) and [telemetry isolation](../../references/telemetry.md) before live runs. Test accounts have ordinary product permissions. 6. For a native macOS project, wire its real sandboxed Swift owner suite and app self-test into a macOS CI job. Reuse the same command locally and in CI through the shared macOS test CLI or `qa.swiftTests`. Require process success, positive test counts and no skipped tests. Linux adapter checks cannot replace this job. Verify the job is a required release check and executes on the candidate commit. 7. Run the suite, inspect failures, repair incorrect test assumptions, and rerun affected journeys. Run setup again to verify it preserves specialization. Update the local skill with commands and observed coverage. For a repaired bug, follow the regression and CI-selection guidance in [surface requirements](../../references/surfaces.md). Retain pure algorithm tests with meaningful edge cases. Remove mocked transport tests only after real journeys prove the same contract. A mocked expired-session response does not prove a provider's actual rejection. A root-page response, discovered component or assertion-free test is not full coverage. Missing credentials, unavailable titles, MFA and absent devices are blocked coverage. Expected outcomes come from independent fixtures and user contracts, not the implementation being tested. For native macOS permission onboarding, read [the native workflow](../../references/macos.md) and complete its capture-readiness steps before GUI work. The agent must inspect real journey screenshots before claiming UI acceptance. Ask the user only for an OS action they must perform. The shared driver supplies exact AX window selection, native mouse input and scoped captures. Projects own selectors and app outcomes. Run nonmutating protocol and signed-fixture checks in CI, with installed grants only in a separately authorized manual-live run.
© Fatih C. Akyon · Apache-2.0 · fcakyon/claude-codex-settings
Similar skills
All skills for Testing and QA →setup by other authors comes first.