{"slug": "i-open-sourced-24-qa-skills-for-claude-code-from-spec-to-release", "title": "I open-sourced 24 QA skills for Claude Code — from spec to release", "summary": "Open-source release of \"QA Claude Skill,\" a collection of 24 production-grade QA skills for Claude Code covering test design, automation, performance, security, and mutation testing. The skills are designed to be configurable for any team via a `config.json` file, with support for multiple modes (including markdown-only for solo developers) and bilingual documentation in Traditional Chinese and English. The project is available under a dual license (MIT for non-commercial use, with commercial licenses available case-by-case).", "body_md": "TL;DR— I just open-sourcedQA Claude Skill— 24 production-grade QA skills for[Claude Code]covering test design, automation, performance, security, mutation testing, and more. MIT for non-commercial use..[GitHub repo]\n\n## The problem\n\nFor two years I've been iterating a personal Claude Code workspace for QA work — bug reports, test plans, review checklists, regression matrices. It saved me hours every week.\n\nBut every time a colleague asked \"how do you write a test plan that fast?\" — handing them my workspace meant they got dozens of files hard-coded with my JIRA project key, my Slack user ID, my AWS bucket. Useless to anyone else.\n\nSo I spent the last two weeks extracting **24 skills** into a properly generalized, open-source repo. Drop in your team's IDs via `config.json`\n\nand it works for any team, any stack.\n\n## What's in the box\n\n**24 skills across 8 categories:**\n\n| Category | Skills |\n|---|---|\nTest Design (8) |\ntest-master · flutter-test-master · test-review · regression-test · speckit-to-tc · tc-version-diff · sheet-md-sync · smoke-test-analyzer |\nAutomation (3) |\ntest-automation · flutter-test-automation · tc-to-pytest |\nBug Management (1) |\nbug-report |\nQuality Quantification (2) |\nmutation-testing · property-based-test-gen |\nReporting (1) |\npublish-regression |\nPerformance & Security (3) |\nperformance-test-gen · security-scan · api-contract-test |\nCI Health (2) |\nvisual-regression-gen · flaky-test-hunter |\nQuality Specialties (4) |\na11y-audit · localization-test · push-notification-test · test-data-factory |\n\n## What it actually does\n\nEach skill activates on natural language triggers. Some examples:\n\n### 1. \"I want to file a bug\"\n\nThe `bug-report`\n\nskill walks you through RIDER format (Reproduction / Impact / Device / Expected vs Actual / References), checks JIRA for duplicates, does root-cause analysis from git history, creates the ticket with the right priority, and sends a Slack DM — in one conversation.\n\n### 2. \"Plan tests for this new feature\"\n\n`test-master`\n\nreads your JIRA ticket (or your description), scans both iOS and Android repos for affected modules, designs a test pyramid (70% Unit / 20% Integration / 10% UI), generates **black-box + white-box test cases** in Google Sheets, identifies coverage gaps against existing tests, and builds an automation ROI roadmap.\n\nIt also enforces a11y must-checks per UI feature (Dynamic Type / VoiceOver / contrast / touch targets) — no more \"we forgot accessibility\" at the end of the sprint.\n\n### 3. \"Are my tests actually catching bugs?\"\n\n`mutation-testing`\n\nruns `mutmut`\n\non your Python backend. It changes `<`\n\nto `<=`\n\n, `True`\n\nto `False`\n\n, or numeric literals — then re-runs your pytest. If your tests still pass with the broken code, that mutation **survived** = your TCs have fake coverage.\n\nThen `property-based-test-gen`\n\ntakes those survived mutations and generates `hypothesis`\n\nstrategies that fuzz 200 inputs per test to close the gap.\n\n### 4. \"Which tests should run on every PR?\"\n\n`smoke-test-analyzer`\n\nscans your existing test suite (iOS XCUITest / Android Espresso / pytest), scores each test on 5 weighted criteria (criticality / speed / stability / independence / coverage value), and tiers them:\n\n-\n**T0 PR Smoke**(< 3 min) — runs every PR -\n**T1 Daily**(< 10 min) — runs nightly -\n**T2 Release**(< 60 min) — pre-release full regression -\n**T3 Manual**— exploratory, visual, a11y\n\nThen it generates `.xctestplan`\n\nfor iOS or Gradle filters for Android.\n\n## Three modes for any tool stack\n\nNot every team has the same MCP servers installed. Same skills, three modes:\n\n| Mode | When to use |\n|---|---|\n`full-mcp` |\nYou have Atlassian + Slack + Google Workspace MCPs |\n`partial-mcp` |\nSome MCPs missing — skills degrade gracefully |\n`markdown-only` |\nSolo dev / no MCP / pure documentation flow |\n\nThe `markdown-only`\n\nmode is what makes this actually portable — every skill can still produce useful Markdown reports under `.claude/testing/`\n\nwithout external dependencies. Solo developers can use the full suite without setting up anything.\n\n## 6 ready-to-use presets\n\n```\ncp config/presets/full-stack.json     config/config.json   # All MCPs\ncp config/presets/jira-only.json      config/config.json   # JIRA only\ncp config/presets/markdown-only.json  config/config.json   # Pure docs\ncp config/presets/startup.json        config/config.json   # Small startup\ncp config/presets/enterprise.json     config/config.json   # 5 team boards\ncp config/presets/government.json     config/config.json   # High-compliance\n```\n\n## Why I made it bilingual + 简体\n\nI'm Taiwanese, and most of the test-engineering content out there is English-first. So every skill ships with:\n\n-\n`SKILL.md`\n\n— Traditional Chinese (primary) -\n`SKILL.en.md`\n\n— English mirror -\n`concept-zh.md`\n\n— Beginner intros for unfamiliar concepts (mutation testing, property-based testing, spec-driven dev, test tiering)\n\nThe README is in English (primary), Traditional Chinese, and Simplified Chinese.\n\n## The license model\n\nI went with a **dual license**:\n\n- 🟢\n**MIT**— Personal use / education / research / non-profits / 30-day evaluation / open-source contributions - 🔴\n**Commercial**— For-profit company internal use, paid products, SaaS, paid consulting\n\n[See LICENSE-COMMERCIAL.md](https://github.com/kao273183/qa-claude-skill/blob/main/LICENSE-COMMERCIAL.md) for how to obtain a commercial license. I'm doing this case-by-case via GitHub Issues — the goal isn't to monetize aggressively, but to leave space for sustainable enterprise support if it grows.\n\n## Quick start\n\n```\ngit clone https://github.com/kao273183/qa-claude-skill.git\ncd qa-claude-skill\ncp config/config.example.json config/config.json   # Edit your IDs\n./install.sh\n```\n\nIn Claude Code:\n\n```\nGenerate test plan for a user login feature\n```\n\nThe `test-master`\n\nskill activates and walks you through. Or try:\n\n`\"I want to file a bug — the checkout crashes on Android\"`\n\n`\"Review these test cases [Google Sheet URL]\"`\n\n`\"Check if my tests actually catch bugs in src/auth/\"`\n\nWindows users — there's a PowerShell version (`install.ps1`\n\n) as of v1.3.0.\n\n## What's still missing\n\nThis is v1.6.2. The roadmap still has:\n\n- Japanese translation\n- Web UI for editing config.json visually\n- More skills (test-impact-analyzer, oauth-flow-test, websocket-realtime-test, llm-quality-eval...)\n\nPRs welcome. The CONTRIBUTING.md has the template for adding a new skill.\n\n## Try it\n\n**GitHub: kao273183/qa-claude-skill**\n\nI'd love to hear what skills are missing for your team's stack — drop an issue or comment below.\n\nIf this saves your team time, you can [buy me a coffee](https://buymeacoffee.com/minikao) ☕ — but a ⭐ on the repo helps more.\n\n*This is a community / personal project for Claude Code users — NOT an official Anthropic product.*", "url": "https://wpnews.pro/news/i-open-sourced-24-qa-skills-for-claude-code-from-spec-to-release", "canonical_source": "https://dev.to/kao273183/i-open-sourced-24-qa-skills-for-claude-code-from-spec-to-release-2d57", "published_at": "2026-05-22 03:16:52+00:00", "updated_at": "2026-05-22 03:32:39.826919+00:00", "lang": "en", "topics": ["open-source", "developer-tools", "artificial-intelligence", "large-language-models", "products"], "entities": ["Claude Code", "JIRA", "Slack", "AWS", "Google Sheets", "RIDER", "GitHub", "MIT"], "alternates": {"html": "https://wpnews.pro/news/i-open-sourced-24-qa-skills-for-claude-code-from-spec-to-release", "markdown": "https://wpnews.pro/news/i-open-sourced-24-qa-skills-for-claude-code-from-spec-to-release.md", "text": "https://wpnews.pro/news/i-open-sourced-24-qa-skills-for-claude-code-from-spec-to-release.txt", "jsonld": "https://wpnews.pro/news/i-open-sourced-24-qa-skills-for-claude-code-from-spec-to-release.jsonld"}}