[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSEZXP2AB74MY3VTPAVQMH":3,"skill-same:01M7CSEZXP2AB74MY3VTPAVQMH":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CSEZXP2AB74MY3VTPAVQMH","retest-after-revision",null,"Use when the task came back to QA after need_revision - what to re-run, what may carry over, and how to keep old passes from approving new code","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\u002Fretest-after-revision\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: retest-after-revision\ncategory: qa\ndescription: Use when the task came back to QA after need_revision - what to re-run, what may carry over, and how to keep old passes from approving new code\nsource: obra\u002Fsuperpowers (MIT), adapted\n---\n# Retest After Revision\n\nA resubmitted task carries history: earlier `passed` test cases (matched by title) and criterion approvals marked `approved (as of SHA, changed since: files)`. Neither is free evidence for this round — a stale pass is exactly what lets a fixed bug reappear unnoticed, or a different bug ship under an old verdict.\n\n## Procedure\n\n1. `list_test_cases` and the criteria lines — read every \"changed since\" note; it names the files touched since the last approval.\n2. `get_task_pull_request` for the changed-file list (this is the named re-test-scope exception, not a code-reading shortcut for the verdict).\n3. **Re-run first** every case that failed last round, using its original reproduction. Bug fixed → prove it by testing the original symptom, not a nearby path.\n4. **Re-run** every case linked to a criterion whose changed-files list touches shared surface: styles\u002Ftokens\u002Ftheme, layout\u002Frouter, API client, auth\u002Fsession, migrations\u002Fschema, env\u002Fconfig, package manifests\u002Flockfile, i18n catalogues. This is what \"plausibly affects\" means in practice — a concrete file-category list, not a feeling.\n5. Run the regression smoke set (regression-checklist).\n6. Re-send every re-run case with its new result and evidence, prefixed by the new short SHA. A case you deliberately did not re-run keeps its old result only if its criterion line already says \"nothing changed since\", or its own notes record why the diff cannot reach it — say which, don't just skip silently.\n7. New behaviour the fix introduced gets new cases, same as any other round.\n\n## Red Flags\n\n- Approving a criterion whose line says \"changed since\" without a fresh run this round.\n- Re-running only the case that failed last time when the fix touched a shared file (styles, auth, migrations, …) that many other cases depend on.\n- Trusting the developer's \"fixed it\" without re-running the original failing reproduction.\n","# Retest After Revision\n\nA resubmitted task carries history: earlier `passed` test cases (matched by title) and criterion approvals marked `approved (as of SHA, changed since: files)`. Neither is free evidence for this round — a stale pass is exactly what lets a fixed bug reappear unnoticed, or a different bug ship under an old verdict.\n\n## Procedure\n\n1. `list_test_cases` and the criteria lines — read every \"changed since\" note; it names the files touched since the last approval.\n2. `get_task_pull_request` for the changed-file list (this is the named re-test-scope exception, not a code-reading shortcut for the verdict).\n3. **Re-run first** every case that failed last round, using its original reproduction. Bug fixed → prove it by testing the original symptom, not a nearby path.\n4. **Re-run** every case linked to a criterion whose changed-files list touches shared surface: styles\u002Ftokens\u002Ftheme, layout\u002Frouter, API client, auth\u002Fsession, migrations\u002Fschema, env\u002Fconfig, package manifests\u002Flockfile, i18n catalogues. This is what \"plausibly affects\" means in practice — a concrete file-category list, not a feeling.\n5. Run the regression smoke set (regression-checklist).\n6. Re-send every re-run case with its new result and evidence, prefixed by the new short SHA. A case you deliberately did not re-run keeps its old result only if its criterion line already says \"nothing changed since\", or its own notes record why the diff cannot reach it — say which, don't just skip silently.\n7. New behaviour the fix introduced gets new cases, same as any other round.\n\n## Red Flags\n\n- Approving a criterion whose line says \"changed since\" without a fresh run this round.\n- Re-running only the case that failed last time when the fix touched a shared file (styles, auth, migrations, …) that many other cases depend on.\n- Trusting the developer's \"fixed it\" without re-running the original failing reproduction.\n",{"name":5,"source":24,"category":25,"description":7},"obra\u002Fsuperpowers (MIT), adapted","qa","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fqa-agent\u002Fskills\u002Fretest-after-revision",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":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill retest-after-revision",{"tool":41,"command":42},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill retest-after-revision",{"tool":44,"command":45},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill retest-after-revision","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fqa-agent\u002Fskills\u002Fretest-after-revision\u002FSKILL.md",true,[],[50,56,63,70,77,84],{"skillNo":51,"name":52,"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":53,"categories":54,"keywords":55,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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",[],[]]