[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EGM7HF5RF06XSGPXY249A2":3,"skill-same:01M7EGM7HF5RF06XSGPXY249A2":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7EGM7HF5RF06XSGPXY249A2","release-readiness",null,"WAY 12 — go \u002F no-go report for a release or milestone. Use when the user says \"release check\", \"go no go\", \"are we ready to release\", \"release readiness\" with a milestone or version.","GhassenAZZOUZ\u002Fclaude-qa-agent","GhassenAZZOUZ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75794579?v=4","01M7EGG6N5NXG9KJJ0KMA7JKBZ","Ghassen AZOUZ","01M7EGG6P7YNY9P555TAPR46XZ",5,"MIT","https:\u002F\u002Fgithub.com\u002FGhassenAZZOUZ\u002Fclaude-qa-agent\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frelease-readiness\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: release-readiness\ndescription: WAY 12 — go \u002F no-go report for a release or milestone. Use when the user says \"release check\", \"go no go\", \"are we ready to release\", \"release readiness\" with a milestone or version.\n---\n\n# WAY 12 — Release Readiness\n\n## Step 1: Gather inputs\n- **Milestone** (required): a milestone title, Jira fixVersion, or Azure iteration path. Ask, and offer the open milestones from recent issues if the user doesn't know it\n- Optional thresholds: `--min-pass \u003Cpct>` (default 95, quarantined tests excluded) · `--allow-sev3 \u003Cn>` (default unlimited) · `--branch` (default: the default branch)\n\n## Phase 1: Collect evidence (read-only)\n\n| Signal | Source |\n|---|---|\n| Open bugs by severity | `issue.list` (milestone, label `bug`, open), grouped by `sev-*` |\n| Bugs `fix-failed` \u002F not yet `verified` | same list, by label |\n| Stories with unanswered Missing Information | `issue.list` (milestone, label `user-story`) (plus any with an ACs table). Check each body's Missing Information section |\n| Latest QA results | newest `qa-artifacts\u002Fruns\u002F*\u002Fresults.json` for each test folder whose index `**Source:**` is in the milestone. Fall back to the newest session report |\n| Untested stories | milestone stories with no test folder whose `**Source:**` points at them |\n| CI | `ci.latest_run` on the branch. Its status, plus the `qa-*` jobs if `ci-test-setup` was done |\n| Flaky \u002F quarantined | `flaky-triage` output if run in the last 7 days, otherwise count `@quarantine` tags |\n\nIf a source can't be read, write \"unknown\" and say why. Never treat unknown as passing.\n\n## Phase 2: Verdict\n\n- **NO-GO** if any of: an open `sev-1` or `sev-2` bug · any `fix-failed` · the latest CI run on the branch failed · the QA pass rate is below `--min-pass`\n- **GO WITH RISKS** if no NO-GO condition applies but any of: an open `sev-3` above `--allow-sev3` · untested stories · stories with open Missing Information · quarantined tests in milestone features · an \"unknown\" signal\n- **GO** otherwise\n\n## Phase 3: Report\nSave `.\u002Fqa-artifacts\u002Freleases\u002F\u003Cmilestone>-\u003CYYYY-MM-DD>.md`:\n\n```markdown\n# Release Readiness — \u003Cmilestone>\n**Verdict: 🔴 NO-GO | 🟠 GO WITH RISKS | 🟢 GO** — \u003Cone-line reason>\n**Date:** \u003CISO> · **Branch:** \u003Cbranch> @ \u003Csha-short>\n\n## Blockers\n- \u003Cref> \u003Ctitle> (sev-1) …\n\n## Risks\n- …\n\n## Evidence\n| Signal | Value | Source |\n|---|---|---|\n| Open bugs | sev-1: 0 · sev-2: 1 · sev-3: 4 · sev-4: 2 | tracker milestone |\n| QA pass rate | 47\u002F50 (94%), 2 quarantined excluded | runs\u002F2026-10-09T14-30-00 |\n| CI | ✅ run #8812 on main | code host |\n| Untested stories | #151, #155 | traceability |\n\n---\n🤖 _Generated by DevOps QA Agent — review before acting on this._\n```\n\nPrint the verdict and blockers. Ask the user before filing it as an issue labeled `release-readiness`. This WAY gives a recommendation. The release decision stays with the team.\n","# WAY 12 — Release Readiness\n\n## Step 1: Gather inputs\n- **Milestone** (required): a milestone title, Jira fixVersion, or Azure iteration path. Ask, and offer the open milestones from recent issues if the user doesn't know it\n- Optional thresholds: `--min-pass \u003Cpct>` (default 95, quarantined tests excluded) · `--allow-sev3 \u003Cn>` (default unlimited) · `--branch` (default: the default branch)\n\n## Phase 1: Collect evidence (read-only)\n\n| Signal | Source |\n|---|---|\n| Open bugs by severity | `issue.list` (milestone, label `bug`, open), grouped by `sev-*` |\n| Bugs `fix-failed` \u002F not yet `verified` | same list, by label |\n| Stories with unanswered Missing Information | `issue.list` (milestone, label `user-story`) (plus any with an ACs table). Check each body's Missing Information section |\n| Latest QA results | newest `qa-artifacts\u002Fruns\u002F*\u002Fresults.json` for each test folder whose index `**Source:**` is in the milestone. Fall back to the newest session report |\n| Untested stories | milestone stories with no test folder whose `**Source:**` points at them |\n| CI | `ci.latest_run` on the branch. Its status, plus the `qa-*` jobs if `ci-test-setup` was done |\n| Flaky \u002F quarantined | `flaky-triage` output if run in the last 7 days, otherwise count `@quarantine` tags |\n\nIf a source can't be read, write \"unknown\" and say why. Never treat unknown as passing.\n\n## Phase 2: Verdict\n\n- **NO-GO** if any of: an open `sev-1` or `sev-2` bug · any `fix-failed` · the latest CI run on the branch failed · the QA pass rate is below `--min-pass`\n- **GO WITH RISKS** if no NO-GO condition applies but any of: an open `sev-3` above `--allow-sev3` · untested stories · stories with open Missing Information · quarantined tests in milestone features · an \"unknown\" signal\n- **GO** otherwise\n\n## Phase 3: Report\nSave `.\u002Fqa-artifacts\u002Freleases\u002F\u003Cmilestone>-\u003CYYYY-MM-DD>.md`:\n\n```markdown\n# Release Readiness — \u003Cmilestone>\n**Verdict: 🔴 NO-GO | 🟠 GO WITH RISKS | 🟢 GO** — \u003Cone-line reason>\n**Date:** \u003CISO> · **Branch:** \u003Cbranch> @ \u003Csha-short>\n\n## Blockers\n- \u003Cref> \u003Ctitle> (sev-1) …\n\n## Risks\n- …\n\n## Evidence\n| Signal | Value | Source |\n|---|---|---|\n| Open bugs | sev-1: 0 · sev-2: 1 · sev-3: 4 · sev-4: 2 | tracker milestone |\n| QA pass rate | 47\u002F50 (94%), 2 quarantined excluded | runs\u002F2026-10-09T14-30-00 |\n| CI | ✅ run #8812 on main | code host |\n| Untested stories | #151, #155 | traceability |\n\n---\n🤖 _Generated by DevOps QA Agent — review before acting on this._\n```\n\nPrint the verdict and blockers. Ask the user before filing it as an issue labeled `release-readiness`. This WAY gives a recommendation. The release decision stays with the team.\n",{"name":5,"description":7},"main","1d5072195baea48c4081624f3d8466179bcabd7d",".claude\u002Fskills\u002Frelease-readiness",4,"https:\u002F\u002Fgithub.com\u002FGhassenAZZOUZ\u002Fclaude-qa-agent","https:\u002F\u002Fgithub.com\u002FGhassenAZZOUZ","QA automation Engineer ","2026-11-06 18:32:27",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add GhassenAZZOUZ\u002Fclaude-qa-agent --skill release-readiness",{"tool":38,"command":39},"bunx","bunx skills add GhassenAZZOUZ\u002Fclaude-qa-agent --skill release-readiness",{"tool":41,"command":42},"pnpm","pnpm dlx skills add GhassenAZZOUZ\u002Fclaude-qa-agent --skill release-readiness","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGhassenAZZOUZ\u002Fclaude-qa-agent\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frelease-readiness\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7EGNW6C1N9425A4KW554XWA","write-tests","WAY 4 — write test cases only, no execution. Use when the user says \"write it\", \"write tests\", \"generate test cases\" — an approved test plan (`Plan:`), or requirements (text or a tracker issue) planned and approved first, optional App\u002FSpec\u002FMR or PR → exactly the planned test files.","https:\u002F\u002Fgithub.com\u002FGhassenAZZOUZ\u002Fclaude-qa-agent\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwrite-tests\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7EGNNESQM030EFGZD1BKK9P","verify-fix","WAY 9 — verify that a bug is fixed by running its regression test. Use when the user says \"verify it\", \"verify fix\", \"is #142 fixed\", \"check the fix\" with one or more bug refs (#142, SHOP-142), or \"verify all\" for every open bug that has a regression test.","https:\u002F\u002Fgithub.com\u002FGhassenAZZOUZ\u002Fclaude-qa-agent\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fverify-fix\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7EGNGAYM3WHT9P1JS0KTD2X","user-story-format","Reference only — the single definition of this project's user-story body (story, Gherkin ACs, Missing Information, DoD) and its AC\u002Fscenario rules. Read by user-story-enhancer (WAY 6) and benchmark-gap-story-writer (WAY 8) so stories they write stay identical in shape and WAY 6 can re-score WAY 8's output. Not a workflow on its own.","https:\u002F\u002Fgithub.com\u002FGhassenAZZOUZ\u002Fclaude-qa-agent\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fuser-story-format\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7EGNB3MZXAWXX7HQP534T9S","tracker","Provider-neutral contract for every issue-tracker and code-host action (create\u002Fupdate\u002Fcomment\u002Fclose issues, attach files, comment on MRs\u002FPRs, read CI runs and logs) plus label conventions and failure handling. Every WAY calls these operations; the matching provider-* skill says how to perform them on GitLab, GitHub, Jira, Azure DevOps, or Bitbucket.","https:\u002F\u002Fgithub.com\u002FGhassenAZZOUZ\u002Fclaude-qa-agent\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftracker\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7EGN66A9GH5MQQNKJFS8ADP","traceability","WAY 14 — requirements traceability matrix for a user story (each acceptance criterion) or a test folder written from plain text (each R-NN requirement) → the tests covering it → their latest result → open bugs. Use when the user says \"trace it\", \"traceability\", \"is #148 covered\", \"coverage of SHOP-148\", \"trace it \u003Cfolder>\".","https:\u002F\u002Fgithub.com\u002FGhassenAZZOUZ\u002Fclaude-qa-agent\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftraceability\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7EGMZ8K606CZT7ND3N2YHDV","test-plan","WAY 19 — design a test plan before any test code. Use when the user says \"plan it\", \"plan tests\", \"test plan\", \"design tests\" with requirements (text or a tracker issue), optional App\u002FSpec\u002FMR or PR. Output is the test plan (scope, levels, one row per Test#\u003Cnn> with category, tags, covers, priority, coverage, entry\u002Fexit criteria, risks), reviewed by `review-plan` (WAY 20), filed for approval; `write it Plan:` \u002F `e2e it Plan:` then write exactly that plan. Also holds the plan format every other WAY reads.","https:\u002F\u002Fgithub.com\u002FGhassenAZZOUZ\u002Fclaude-qa-agent\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftest-plan\u002FSKILL.md",[],[]]