[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EGK3Q6JDRX1BCF6YAS7AXM":3,"skill-same:01M7EGK3Q6JDRX1BCF6YAS7AXM":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},"01M7EGK3Q6JDRX1BCF6YAS7AXM","provider-bitbucket",null,"How to perform the tracker skill's code-host operations on Bitbucket Cloud — pull requests, diffs, PR comments, Pipelines runs and step logs — through the Bitbucket REST API. Bitbucket is a code host here; pair it with Jira (or another tracker) for issues. Load it when QA_CODE_HOST is bitbucket.","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\u002Fprovider-bitbucket\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: provider-bitbucket\ndescription: How to perform the tracker skill's code-host operations on Bitbucket Cloud — pull requests, diffs, PR comments, Pipelines runs and step logs — through the Bitbucket REST API. Bitbucket is a code host here; pair it with Jira (or another tracker) for issues. Load it when QA_CODE_HOST is bitbucket.\n---\n\n# provider-bitbucket\n\nBitbucket is used as a **code host only**: PRs, diffs and Pipelines. File issues in Jira (`QA_TRACKER=jira`), which is how most Bitbucket teams work.\n\n**Settings:** `BITBUCKET_WORKSPACE`, `BITBUCKET_REPO`, and secrets `BITBUCKET_EMAIL` + `BITBUCKET_API_TOKEN` (an Atlassian API token with repository and pull-request scopes). Load them only inside the command. The base URL is `https:\u002F\u002Fapi.bitbucket.org\u002F2.0\u002Frepositories\u002F$BITBUCKET_WORKSPACE\u002F$BITBUCKET_REPO`, called `$BB` below:\n\n```bash\nset -a; . .\u002F.env; set +a\nBB=\"https:\u002F\u002Fapi.bitbucket.org\u002F2.0\u002Frepositories\u002F$BITBUCKET_WORKSPACE\u002F$BITBUCKET_REPO\"\ncurl -s -u \"$BITBUCKET_EMAIL:$BITBUCKET_API_TOKEN\" \"$BB\u002Fpullrequests\u002F87\"\n```\n\n## Operations\n\n| Operation | Request |\n|---|---|\n| `change.get` | `GET $BB\u002Fpullrequests\u002F\u003Cid>` (title, description, `source.branch.name`, links), plus `GET $BB\u002Fpullrequests\u002F\u003Cid>\u002Fdiffstat` for changed files |\n| `change.diff` | `GET $BB\u002Fpullrequests\u002F\u003Cid>\u002Fdiff` (unified diff). Filter it to the files you need |\n| `change.comment` | `POST $BB\u002Fpullrequests\u002F\u003Cid>\u002Fcomments` with `{\"content\":{\"raw\":\"\u003Cmarkdown>\"}}` |\n| find the PR for a branch | `GET $BB\u002Fpullrequests?q=source.branch.name=\"\u003Cbranch>\"&state=OPEN` (the query must be URL-encoded) |\n| `ci.get_run` | `GET $BB\u002Fpipelines\u002F\u003Cuuid-or-build-number>`, then `GET $BB\u002Fpipelines\u002F\u003Cuuid>\u002Fsteps` for each step's state |\n| `ci.job_log` | `GET $BB\u002Fpipelines\u002F\u003Cuuid>\u002Fsteps\u002F\u003Cstep-uuid>\u002Flog`. Keep the tail |\n| `ci.latest_run` | `GET $BB\u002Fpipelines?target.branch=\u003Cbranch>&sort=-created_on&pagelen=1` |\n| `ci.lint` | no API. Check `bitbucket-pipelines.yml` parses and uses only known top-level keys (`image`, `definitions`, `pipelines`, `options`, `clone`) |\n| `project.check` | `GET $BB` |\n| issue operations | not supported here. Use `QA_TRACKER=jira` (`provider-jira`) |\n| `file.attach` | for PR comments, link the Pipelines artifacts of the run, or keep the local path |\n\n## Notes\n- **UUIDs** come wrapped in braces (`{1a2b…}`). URL-encode them (`%7B…%7D`) in paths\n- **Refs:** report pull requests as `#87` and pipelines by build number\n- **Markdown:** PR comments render it natively\n- **Bitbucket Data Center** uses a different API (`\u002Frest\u002Fapi\u002F1.0\u002Fprojects\u002F\u003Ckey>\u002Frepos\u002F\u003Cslug>\u002Fpull-requests\u002F\u003Cid>`). Say it isn't covered yet rather than guessing\n","# provider-bitbucket\n\nBitbucket is used as a **code host only**: PRs, diffs and Pipelines. File issues in Jira (`QA_TRACKER=jira`), which is how most Bitbucket teams work.\n\n**Settings:** `BITBUCKET_WORKSPACE`, `BITBUCKET_REPO`, and secrets `BITBUCKET_EMAIL` + `BITBUCKET_API_TOKEN` (an Atlassian API token with repository and pull-request scopes). Load them only inside the command. The base URL is `https:\u002F\u002Fapi.bitbucket.org\u002F2.0\u002Frepositories\u002F$BITBUCKET_WORKSPACE\u002F$BITBUCKET_REPO`, called `$BB` below:\n\n```bash\nset -a; . .\u002F.env; set +a\nBB=\"https:\u002F\u002Fapi.bitbucket.org\u002F2.0\u002Frepositories\u002F$BITBUCKET_WORKSPACE\u002F$BITBUCKET_REPO\"\ncurl -s -u \"$BITBUCKET_EMAIL:$BITBUCKET_API_TOKEN\" \"$BB\u002Fpullrequests\u002F87\"\n```\n\n## Operations\n\n| Operation | Request |\n|---|---|\n| `change.get` | `GET $BB\u002Fpullrequests\u002F\u003Cid>` (title, description, `source.branch.name`, links), plus `GET $BB\u002Fpullrequests\u002F\u003Cid>\u002Fdiffstat` for changed files |\n| `change.diff` | `GET $BB\u002Fpullrequests\u002F\u003Cid>\u002Fdiff` (unified diff). Filter it to the files you need |\n| `change.comment` | `POST $BB\u002Fpullrequests\u002F\u003Cid>\u002Fcomments` with `{\"content\":{\"raw\":\"\u003Cmarkdown>\"}}` |\n| find the PR for a branch | `GET $BB\u002Fpullrequests?q=source.branch.name=\"\u003Cbranch>\"&state=OPEN` (the query must be URL-encoded) |\n| `ci.get_run` | `GET $BB\u002Fpipelines\u002F\u003Cuuid-or-build-number>`, then `GET $BB\u002Fpipelines\u002F\u003Cuuid>\u002Fsteps` for each step's state |\n| `ci.job_log` | `GET $BB\u002Fpipelines\u002F\u003Cuuid>\u002Fsteps\u002F\u003Cstep-uuid>\u002Flog`. Keep the tail |\n| `ci.latest_run` | `GET $BB\u002Fpipelines?target.branch=\u003Cbranch>&sort=-created_on&pagelen=1` |\n| `ci.lint` | no API. Check `bitbucket-pipelines.yml` parses and uses only known top-level keys (`image`, `definitions`, `pipelines`, `options`, `clone`) |\n| `project.check` | `GET $BB` |\n| issue operations | not supported here. Use `QA_TRACKER=jira` (`provider-jira`) |\n| `file.attach` | for PR comments, link the Pipelines artifacts of the run, or keep the local path |\n\n## Notes\n- **UUIDs** come wrapped in braces (`{1a2b…}`). URL-encode them (`%7B…%7D`) in paths\n- **Refs:** report pull requests as `#87` and pipelines by build number\n- **Markdown:** PR comments render it natively\n- **Bitbucket Data Center** uses a different API (`\u002Frest\u002Fapi\u002F1.0\u002Fprojects\u002F\u003Ckey>\u002Frepos\u002F\u003Cslug>\u002Fpull-requests\u002F\u003Cid>`). Say it isn't covered yet rather than guessing\n",{"name":5,"description":7},"main","1d5072195baea48c4081624f3d8466179bcabd7d",".claude\u002Fskills\u002Fprovider-bitbucket",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 provider-bitbucket",{"tool":38,"command":39},"bunx","bunx skills add GhassenAZZOUZ\u002Fclaude-qa-agent --skill provider-bitbucket",{"tool":41,"command":42},"pnpm","pnpm dlx skills add GhassenAZZOUZ\u002Fclaude-qa-agent --skill provider-bitbucket","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGhassenAZZOUZ\u002Fclaude-qa-agent\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fprovider-bitbucket\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",[],[]]