What happens if I decline a detected change?

The tool does not modify anything unless you approve; you can keep your current config.

Can this modify documentation files?

No. It only reads existing docs and updates the qa-artifacts/.qa-config.json.

Where does the tool store ignore recommendations?

It analyzes the configured output and suggests adding qa-artifacts/ to the project's .gitignore when appropriate.

setup

npx machina-cli add skill cyberwalk3r/qa-toolkit/setup --openclaw

Files (1)

SKILL.md

1.7 KB

QA Toolkit Setup

Read qa-artifacts/.qa-config.json for auto-detected project context.

Workflow

Show the user what was detected — languages, frameworks, test tools, CI/CD, package manager
Read existing docs if found:
- CLAUDE.md — project conventions, existing guidelines
- README.md — project overview
- TESTING.md — testing standards (if exists)
- CONTRIBUTING.md — contribution workflow (if exists)
Ask the user to confirm or correct:
- Is the detected tech stack correct?
- What bug tracker does the team use? (Jira / GitHub Issues / Azure DevOps / Linear)
- Any high-risk areas of the app the team should focus on?
Update qa-artifacts/.qa-config.json with corrections and preferences
Suggest adding output directory to .gitignore if not already present:
- Check if qa-artifacts/ (or the configured outputDir) is in the project's .gitignore
- If not, suggest adding it — QA artifacts contain machine-specific paths and session-specific output that shouldn't be committed
- Example line to add: qa-artifacts/
Summarize what's configured and which skills are most relevant for this project

Important

Read only — do not create or modify CLAUDE.md, README, or any existing project files
This is a configuration step, not a documentation generator

Suggested Next Steps

After setup is complete, suggest:

"Start with a PR review (/qa-toolkit:pr-review) or generate test cases from your requirements (/qa-toolkit:test-cases)."

Source

git clone https://github.com/cyberwalk3r/qa-toolkit/blob/main/skills/setup/SKILL.mdView on GitHub

Overview

QA Toolkit Setup reads the auto-detected project context from qa-artifacts/.qa-config.json, inspects existing docs, and prompts you to confirm or correct the detected stack. It then saves corrections back to the config and suggests ignoring the artifacts directory in .gitignore. This is a read-only step for docs and a config updater for artifacts.

How This Skill Works

The tool displays detected tech stack (languages, frameworks, test tools, CI/CD, package manager) from qa-artifacts/.qa-config.json, reads existing docs (CLAUDE.md, README.md, TESTING.md, CONTRIBUTING.md) if present, and prompts you to confirm or adjust detections. Upon confirmation, it updates qa-artifacts/.qa-config.json with corrections and recommends adding qa-artifacts/ to .gitignore, then summarizes what’s configured and which skills are most relevant.

When to Use It

When starting a QA automation setup for a repo with an auto-detected config
During onboarding to verify the detected tech stack against the actual project
When existing docs are present and you want to align tool configuration with them
If the detected stack seems incorrect or incomplete
Before finalizing the setup to ensure qa-artifacts is ignored and a summary is produced

Quick Start

Step 1: Display auto-detected context from qa-artifacts/.qa-config.json
Step 2: Read existing docs (CLAUDE.md, README.md, TESTING.md, CONTRIBUTING.md) if present
Step 3: Confirm or correct detections and save corrections to qa-artifacts/.qa-config.json; check .gitignore for qa-artifacts/ and suggest adding if missing

Best Practices

Always verify the detected tech stack against team knowledge before saving
Respect the read-only constraint on CLAUDE.md, README.md, and other docs
Limit changes to qa-artifacts/.qa-config.json only
Check for qa-artifacts/ in the project's .gitignore and propose adding if missing
Provide a concise summary of the configured context and relevant skills

Example Use Cases

Detected stack: Python, PyTest, GitHub Actions; user confirms and saves corrections to qa-artifacts/.qa-config.json
Monorepo with Node and multiple tools; detected tools refined to reflect per-package configs and saved
Docs present (CLAUDE.md, README.md); setup reads them but does not modify them, updates only config
CI/CD on Azure DevOps; tool identifies the pipeline and records it in the config
No existing docs or config; user validates detections and a baseline qa-artifacts/.qa-config.json is created

Frequently Asked Questions

Add this skill to your agents