[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CS6AKEBEVVF764GP2H5HHH":3,"skill-same:01M7CS6AKEBEVVF764GP2H5HHH":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},"01M7CS6AKEBEVVF764GP2H5HHH","addressing-review-feedback",null,"How to work a task returned with review, QA or UAT findings. Use when a task is in need_revision or PR review comments are in your context.","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\u002Fmobile-developer\u002Fskills\u002Faddressing-review-feedback\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: addressing-review-feedback\ncategory: workflow\ndescription: How to work a task returned with review, QA or UAT findings. Use when a task is in need_revision or PR review comments are in your context.\nsource: obra\u002Fsuperpowers (MIT), adapted\n---\n# Addressing Review Feedback\n\n## Overview\n\nA `need_revision` task is somebody else's evidence that something is wrong, not a request to improvise. Treat it the way you would a bug report: verify, fix at the root, prove it with a test, and answer every point — silence on one is how a task bounces a second time for something you could have agreed or disagreed with up front.\n\n## The Process\n\n1. **Read everything before touching code.** Every numbered point on the task, plus the PR review comments when the round happened there (`list_task_comments`, `get_task_pull_request` with `include_diff: false` when you don't need the diff itself). If a point is unclear, re-read the code it's about before acting on a guess. Points can be related — a root cause can explain two of them at once.\n2. **Verify each claim** against the code and, where you can, the running product — a reviewer can be wrong about where a line lives or what a function does. Classify each point: **fix** (the claim holds), **disagree** (with evidence — a file:line or a run that shows the current behavior is correct), or **needs a human decision** (a product call neither of you can settle from the code).\n3. **Fix in order: blocking → simple → complex.** Blocking = crash, security hole, or an acceptance criterion left unmet. Each fix gets its own guard test that fails before the fix and passes after (root-cause-debugging) — a fix with no failing-first test is not verified, it's hoped.\n4. **Push back technically, never performatively.** A point you disagree with gets a reasoned answer with evidence, not silent compliance and not silent skipping. Reply in the PR thread (`comment_on_pull_request` with `reply_to_comment_id`) when it came from a review comment — a new top-level comment leaves the reviewer's thread looking unanswered; otherwise `add_task_comment` for a task-comment point. No \"You're absolutely right,\" no thanks, no preamble — state the finding.\n5. **A YAGNI check** when a reviewer asks you to \"implement it properly\" or \"handle the general case\": `grep_code` for actual callers first. Build the general version only if more than one caller needs it; otherwise say so and keep the fix scoped to what broke.\n6. **Closing message: a point map.** One line per numbered point — point → root cause → fix (file:line) → guard test, or point → why you disagree, with evidence. The architect's review of your revision reads this map against the diff; a revision with no map is a second bounce waiting to happen.\n\n## Red Flags\n\n- A partial fix — three of four points addressed and the fourth left unmentioned.\n- A fix with no guard test that failed first.\n- Weakening or deleting the test that caught the problem instead of fixing the code.\n- Silently agreeing with a wrong claim because arguing felt slower — a wrong \"fix\" based on a wrong claim bounces again, further down the line.\n- A closing message that says \"addressed all feedback\" without the per-point map.\n","# Addressing Review Feedback\n\n## Overview\n\nA `need_revision` task is somebody else's evidence that something is wrong, not a request to improvise. Treat it the way you would a bug report: verify, fix at the root, prove it with a test, and answer every point — silence on one is how a task bounces a second time for something you could have agreed or disagreed with up front.\n\n## The Process\n\n1. **Read everything before touching code.** Every numbered point on the task, plus the PR review comments when the round happened there (`list_task_comments`, `get_task_pull_request` with `include_diff: false` when you don't need the diff itself). If a point is unclear, re-read the code it's about before acting on a guess. Points can be related — a root cause can explain two of them at once.\n2. **Verify each claim** against the code and, where you can, the running product — a reviewer can be wrong about where a line lives or what a function does. Classify each point: **fix** (the claim holds), **disagree** (with evidence — a file:line or a run that shows the current behavior is correct), or **needs a human decision** (a product call neither of you can settle from the code).\n3. **Fix in order: blocking → simple → complex.** Blocking = crash, security hole, or an acceptance criterion left unmet. Each fix gets its own guard test that fails before the fix and passes after (root-cause-debugging) — a fix with no failing-first test is not verified, it's hoped.\n4. **Push back technically, never performatively.** A point you disagree with gets a reasoned answer with evidence, not silent compliance and not silent skipping. Reply in the PR thread (`comment_on_pull_request` with `reply_to_comment_id`) when it came from a review comment — a new top-level comment leaves the reviewer's thread looking unanswered; otherwise `add_task_comment` for a task-comment point. No \"You're absolutely right,\" no thanks, no preamble — state the finding.\n5. **A YAGNI check** when a reviewer asks you to \"implement it properly\" or \"handle the general case\": `grep_code` for actual callers first. Build the general version only if more than one caller needs it; otherwise say so and keep the fix scoped to what broke.\n6. **Closing message: a point map.** One line per numbered point — point → root cause → fix (file:line) → guard test, or point → why you disagree, with evidence. The architect's review of your revision reads this map against the diff; a revision with no map is a second bounce waiting to happen.\n\n## Red Flags\n\n- A partial fix — three of four points addressed and the fourth left unmentioned.\n- A fix with no guard test that failed first.\n- Weakening or deleting the test that caught the problem instead of fixing the code.\n- Silently agreeing with a wrong claim because arguing felt slower — a wrong \"fix\" based on a wrong claim bounces again, further down the line.\n- A closing message that says \"addressed all feedback\" without the per-point map.\n",{"name":5,"source":24,"category":25,"description":7},"obra\u002Fsuperpowers (MIT), adapted","workflow","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fmobile-developer\u002Fskills\u002Faddressing-review-feedback",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 addressing-review-feedback",{"tool":41,"command":42},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill addressing-review-feedback",{"tool":44,"command":45},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill addressing-review-feedback","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fmobile-developer\u002Fskills\u002Faddressing-review-feedback\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",[],[]]