[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSD8K2GN0QZB0S8M8YMZMB":3,"skill-same:01M7CSD8K2GN0QZB0S8M8YMZMB":48},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CSD8K2GN0QZB0S8M8YMZMB","automation-pipeline-integration",null,"Wire the automation test project into the repository's own pipeline so every task must pass the suite before it can leave QA","makifbaysal\u002Ftasktrooper","makifbaysal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25031940?v=4","01M7CRG3ZCSYZSSEVDMW3DEYC8","Mehmet Akif Baysal","01M7CRG401FJ8YAXH5ER730XYV",122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fqa-agent\u002Fskills\u002Fautomation-pipeline-integration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: automation-pipeline-integration\ncategory: testing\ndescription: Wire the automation test project into the repository's own pipeline so every task must pass the suite before it can leave QA\nenabled: false\n---\n# Automation Pipeline Integration\n\n## Overview\n\nAn automation suite that only runs when someone remembers it is decoration. The suite must run in the **repository's own pipeline** — the one this platform triggers automatically when a task moves to `ready_for_qa` — so a task cannot pass QA while the suite is red. Each repository runs its own tests in its own pipeline; there is no shared cross-project test job.\n\n## How the platform runs it\n\nWhen a task reaches `ready_for_qa`, the QA pipeline runs the repo's build and test stages: the repository's `test_command` override if set, otherwise language auto-detect. A red pipeline sends the task back to `need_revision` automatically with the failed stage's log; a green pipeline releases the task to QA dispatch. Check results with `get_pipeline_status`; re-trigger manually via the task's pipelines endpoint after a fix.\n\n## Wiring the suite in\n\n1. **One entrypoint command.** Give the automation project a single script that provisions everything and exits non-zero on any failure — e.g. `scripts\u002Fe2e.sh`: start disposable dependencies (Testcontainers\u002Fcompose), boot the app from the current branch build, start WireMock stubs, run the suite, tear down.\n2. **Make the pipeline call it.** Set the repository's `test_command` to run unit tests AND the automation entrypoint (`go test .\u002F... && .\u002Fqa-automation\u002Fscripts\u002Fe2e.sh`, or the package.json script that does both). If the repo's CI (GitHub Actions etc.) is the source of truth for deploys, add the same entrypoint there too — same command locally, in the QA pipeline, and in CI, so green means the same thing everywhere.\n3. **Keep it self-contained.** The pipeline environment provides no shared DB and no external network guarantees: the suite brings its own database container (test-database-seeding) and stubs (test-doubles-wiremock). If the environment has no container runtime, the entrypoint must fail loudly with a clear message — never silently skip tests and report green; raise the infra gap on the task instead.\n4. **Keep it fast and deterministic.** Budget the suite (minutes, not an hour); parallel-safe, order-independent tests; no sleeps, no shared state. Flaky tests get fixed or quarantined with a task — a suite people rerun until green enforces nothing.\n\n## Coverage reporters are mandatory\n\nThe platform parses the test job's log for a total coverage percentage and surfaces it on the pipeline and job — but only if the suite prints one in a format it recognizes. A suite with no coverage reporter enabled leaves that number blank, silently, and nobody is told the pipeline stopped proving anything about coverage. Every automation\u002Funit suite wired into `test_command` must enable one:\n\n- **Go:** `go test -cover .\u002F...` (prints a `coverage: NN.N% of statements` line per package), or `go tool cover -func=coverage.out` after a `-coverprofile=coverage.out` run (prints the `total: (statements) NN.N%` summary line).\n- **JS\u002FTS (Jest\u002FVitest):** run with `--coverage` so the run ends with an istanbul text summary (`Lines : NN.N%` or the `All files | ... | NN.N |` table) in the job's stdout — not only an HTML\u002Flcov file the log never shows.\n- **Python (pytest):** `pytest --cov` with the default terminal report, which prints a `TOTAL ... NN%` line.\n\nThe report must land in the job's console output (stdout\u002Fstderr), because that is the only thing the platform's log-based parser can read — a coverage artifact written only to disk (`coverage.out`, `lcov.info`, `htmlcov\u002F`) and never printed is invisible to it.\n\n## The QA contract per task\n\n- After the manual pass, this task's scenarios are added to the suite (e2e-automation-project).\n- The suite — including the new tests — is green: run it yourself and\u002For confirm the pipeline (`get_pipeline_status`) after your changes land.\n- Only then does the task move to `human_uat`, with the suite result quoted in the evidence comment.\n\nNew scenarios accumulate: every finished task widens the regression net that all future tasks must pass.\n\n## Red Flags\n\n- The automation project exists but no pipeline or CI job executes it.\n- `test_command` runs unit tests only, and the e2e suite is \"run manually sometimes\".\n- The entrypoint skips the suite when dependencies are missing and still exits 0.\n- Tests pass locally but the pipeline lacks the runtime\u002Fconfig to run them — fix the pipeline, don't drop the tests.\n- The suite runs but prints no coverage total (no `-cover`\u002F`--coverage`\u002F`--cov` flag), so the pipeline's coverage badge never appears even though tests genuinely ran.\n","# Automation Pipeline Integration\n\n## Overview\n\nAn automation suite that only runs when someone remembers it is decoration. The suite must run in the **repository's own pipeline** — the one this platform triggers automatically when a task moves to `ready_for_qa` — so a task cannot pass QA while the suite is red. Each repository runs its own tests in its own pipeline; there is no shared cross-project test job.\n\n## How the platform runs it\n\nWhen a task reaches `ready_for_qa`, the QA pipeline runs the repo's build and test stages: the repository's `test_command` override if set, otherwise language auto-detect. A red pipeline sends the task back to `need_revision` automatically with the failed stage's log; a green pipeline releases the task to QA dispatch. Check results with `get_pipeline_status`; re-trigger manually via the task's pipelines endpoint after a fix.\n\n## Wiring the suite in\n\n1. **One entrypoint command.** Give the automation project a single script that provisions everything and exits non-zero on any failure — e.g. `scripts\u002Fe2e.sh`: start disposable dependencies (Testcontainers\u002Fcompose), boot the app from the current branch build, start WireMock stubs, run the suite, tear down.\n2. **Make the pipeline call it.** Set the repository's `test_command` to run unit tests AND the automation entrypoint (`go test .\u002F... && .\u002Fqa-automation\u002Fscripts\u002Fe2e.sh`, or the package.json script that does both). If the repo's CI (GitHub Actions etc.) is the source of truth for deploys, add the same entrypoint there too — same command locally, in the QA pipeline, and in CI, so green means the same thing everywhere.\n3. **Keep it self-contained.** The pipeline environment provides no shared DB and no external network guarantees: the suite brings its own database container (test-database-seeding) and stubs (test-doubles-wiremock). If the environment has no container runtime, the entrypoint must fail loudly with a clear message — never silently skip tests and report green; raise the infra gap on the task instead.\n4. **Keep it fast and deterministic.** Budget the suite (minutes, not an hour); parallel-safe, order-independent tests; no sleeps, no shared state. Flaky tests get fixed or quarantined with a task — a suite people rerun until green enforces nothing.\n\n## Coverage reporters are mandatory\n\nThe platform parses the test job's log for a total coverage percentage and surfaces it on the pipeline and job — but only if the suite prints one in a format it recognizes. A suite with no coverage reporter enabled leaves that number blank, silently, and nobody is told the pipeline stopped proving anything about coverage. Every automation\u002Funit suite wired into `test_command` must enable one:\n\n- **Go:** `go test -cover .\u002F...` (prints a `coverage: NN.N% of statements` line per package), or `go tool cover -func=coverage.out` after a `-coverprofile=coverage.out` run (prints the `total: (statements) NN.N%` summary line).\n- **JS\u002FTS (Jest\u002FVitest):** run with `--coverage` so the run ends with an istanbul text summary (`Lines : NN.N%` or the `All files | ... | NN.N |` table) in the job's stdout — not only an HTML\u002Flcov file the log never shows.\n- **Python (pytest):** `pytest --cov` with the default terminal report, which prints a `TOTAL ... NN%` line.\n\nThe report must land in the job's console output (stdout\u002Fstderr), because that is the only thing the platform's log-based parser can read — a coverage artifact written only to disk (`coverage.out`, `lcov.info`, `htmlcov\u002F`) and never printed is invisible to it.\n\n## The QA contract per task\n\n- After the manual pass, this task's scenarios are added to the suite (e2e-automation-project).\n- The suite — including the new tests — is green: run it yourself and\u002For confirm the pipeline (`get_pipeline_status`) after your changes land.\n- Only then does the task move to `human_uat`, with the suite result quoted in the evidence comment.\n\nNew scenarios accumulate: every finished task widens the regression net that all future tasks must pass.\n\n## Red Flags\n\n- The automation project exists but no pipeline or CI job executes it.\n- `test_command` runs unit tests only, and the e2e suite is \"run manually sometimes\".\n- The entrypoint skips the suite when dependencies are missing and still exits 0.\n- Tests pass locally but the pipeline lacks the runtime\u002Fconfig to run them — fix the pipeline, don't drop the tests.\n- The suite runs but prints no coverage total (no `-cover`\u002F`--coverage`\u002F`--cov` flag), so the pipeline's coverage badge never appears even though tests genuinely ran.\n",{"name":5,"enabled":20,"category":24,"description":7},"testing","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fqa-agent\u002Fskills\u002Fautomation-pipeline-integration",18,"https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper","https:\u002F\u002Ftasktrooper.ai","https:\u002F\u002Fgithub.com\u002Fmakifbaysal","Senior Software Developer","2026-11-15 04:50:29",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill automation-pipeline-integration",{"tool":40,"command":41},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill automation-pipeline-integration",{"tool":43,"command":44},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill automation-pipeline-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fqa-agent\u002Fskills\u002Fautomation-pipeline-integration\u002FSKILL.md",true,[],[49,55,62,69,76,83],{"skillNo":50,"name":51,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7CSVAQG91ETHQ0HBNZDG5FR","ux-copy","Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fux-copy\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CSV6H0J38659NDXHJQ8396","screen-mockup-html","Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fscreen-mockup-html\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CSV3JFRF3BM3XK52M7YEYR","performance-awareness","How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fperformance-awareness\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CSTZDH00YRF5SCT7BRT9QD","design-variants","Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-variants\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CSTV6P3SM3PAE28DB0RF77","design-system-authoring","Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-system-authoring\u002FSKILL.md",[],[]]