[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CS32B7V09V8YFJF2KMY0T7":3,"skill-same:01M7CS32B7V09V8YFJF2KMY0T7":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},"01M7CS32B7V09V8YFJF2KMY0T7","incremental-commits",null,"Commit boundaries and messages on a task branch. Use when deciding where to cut a commit or how to word one while implementing.","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\u002Fgame-developer\u002Fskills\u002Fincremental-commits\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: incremental-commits\ncategory: workflow\ndescription: Commit boundaries and messages on a task branch. Use when deciding where to cut a commit or how to word one while implementing.\nsource: obra\u002Fsuperpowers (MIT), adapted\n---\n# Incremental Commits\n\n## Overview\n\nWork in bite-sized steps, not one large change. Small commits keep each step reversible and make revisions cheap to localize.\n\n## The Process\n\n1. Before coding, turn the task into a short ordered list of steps. Each step is ONE action worth 2–5 minutes:\n   - \"Write the failing test\" — a step\n   - \"Run it and watch it fail\" — a step\n   - \"Write minimal code to pass\" — a step\n   - \"Run the tests, all green\" — a step\n   - \"Commit\" — a step\n2. Commit locally after each green step on your task branch: `run_terminal` with `git add -A && git commit -m \"\u003Ctype>: \u003Cimperative summary>\"`. Do not push, and do not call `commit_task_changes` mid-run — the system commits and pushes your run's final state and opens the pull request at hand-off; a mid-run commit of your own is never the one that ships.\n3. Each commit is one logical change: the test and the code that satisfies it belong together; unrelated changes never share a commit.\n4. Commit message: imperative summary line; explain WHY in the body when it is not obvious from the diff.\n\n## Rules of Thumb\n\n- Never accumulate a large uncommitted change — if the diff is hard to describe in one sentence, you missed a commit point.\n- A step should end with an independently verifiable state (test green, build passing).\n- Setup\u002Fscaffolding folds into the step whose deliverable needs it; don't commit empty skeletons.\n- If a step balloons mid-way, stop, commit what is green, and re-slice the rest.\n\n## Quick Reference\n\n| Situation | Commit boundary |\n|-----------|-----------------|\n| Test + code that satisfies it | One commit together |\n| Two unrelated behaviors | Two commits |\n| Refactor + behavior change | Separate commits (refactor first, while green) |\n| Setup\u002Fscaffolding | Folded into the step that needs it — no empty-skeleton commits |\n| Formatting-only change | Its own commit, never mixed with logic |\n\n## Worked Example\n\nTask: add a `priority` field to task creation. A good branch history:\n\n```\nfeat: add priority column migration\ntest: expect create to persist priority\nfeat: persist priority in create handler\ntest: default priority to \"medium\" when omitted\nfeat: default omitted priority to medium\n```\n\nFive focused commits. When QA later reports \"omitted priority crashes,\" the fix and the guard test land on top as commit six — nobody re-reads the migration. Compare to one `feat: add priority` blob, where the same fix forces a reviewer back through the entire change.\n\n## Why\n\n- **Each green commit is a checkpoint, not a review unit.** PRs here are squash-merged and the reviewer reads the whole PR diff at once, not your individual commits — so commit granularity is for YOU: `git reset --hard` to the last green commit when a step goes wrong instead of untangling a half-finished working tree.\n- When a revision comes back, small commits localize what to change even though the reviewer never saw them individually.\n- If an approach fails, you lose one step, not the whole task.\n\n## Red Flags\n\n- The diff is hard to describe in one sentence → you missed a commit point.\n- `git status` shows changes across five unrelated areas → you batched.\n- You are about to commit with message \"wip\" or \"fixes\" → the step wasn't a clean logical unit.\n- You are about to push or call `commit_task_changes` mid-run → that is the system's job at hand-off, not yours mid-task.\n","# Incremental Commits\n\n## Overview\n\nWork in bite-sized steps, not one large change. Small commits keep each step reversible and make revisions cheap to localize.\n\n## The Process\n\n1. Before coding, turn the task into a short ordered list of steps. Each step is ONE action worth 2–5 minutes:\n   - \"Write the failing test\" — a step\n   - \"Run it and watch it fail\" — a step\n   - \"Write minimal code to pass\" — a step\n   - \"Run the tests, all green\" — a step\n   - \"Commit\" — a step\n2. Commit locally after each green step on your task branch: `run_terminal` with `git add -A && git commit -m \"\u003Ctype>: \u003Cimperative summary>\"`. Do not push, and do not call `commit_task_changes` mid-run — the system commits and pushes your run's final state and opens the pull request at hand-off; a mid-run commit of your own is never the one that ships.\n3. Each commit is one logical change: the test and the code that satisfies it belong together; unrelated changes never share a commit.\n4. Commit message: imperative summary line; explain WHY in the body when it is not obvious from the diff.\n\n## Rules of Thumb\n\n- Never accumulate a large uncommitted change — if the diff is hard to describe in one sentence, you missed a commit point.\n- A step should end with an independently verifiable state (test green, build passing).\n- Setup\u002Fscaffolding folds into the step whose deliverable needs it; don't commit empty skeletons.\n- If a step balloons mid-way, stop, commit what is green, and re-slice the rest.\n\n## Quick Reference\n\n| Situation | Commit boundary |\n|-----------|-----------------|\n| Test + code that satisfies it | One commit together |\n| Two unrelated behaviors | Two commits |\n| Refactor + behavior change | Separate commits (refactor first, while green) |\n| Setup\u002Fscaffolding | Folded into the step that needs it — no empty-skeleton commits |\n| Formatting-only change | Its own commit, never mixed with logic |\n\n## Worked Example\n\nTask: add a `priority` field to task creation. A good branch history:\n\n```\nfeat: add priority column migration\ntest: expect create to persist priority\nfeat: persist priority in create handler\ntest: default priority to \"medium\" when omitted\nfeat: default omitted priority to medium\n```\n\nFive focused commits. When QA later reports \"omitted priority crashes,\" the fix and the guard test land on top as commit six — nobody re-reads the migration. Compare to one `feat: add priority` blob, where the same fix forces a reviewer back through the entire change.\n\n## Why\n\n- **Each green commit is a checkpoint, not a review unit.** PRs here are squash-merged and the reviewer reads the whole PR diff at once, not your individual commits — so commit granularity is for YOU: `git reset --hard` to the last green commit when a step goes wrong instead of untangling a half-finished working tree.\n- When a revision comes back, small commits localize what to change even though the reviewer never saw them individually.\n- If an approach fails, you lose one step, not the whole task.\n\n## Red Flags\n\n- The diff is hard to describe in one sentence → you missed a commit point.\n- `git status` shows changes across five unrelated areas → you batched.\n- You are about to commit with message \"wip\" or \"fixes\" → the step wasn't a clean logical unit.\n- You are about to push or call `commit_task_changes` mid-run → that is the system's job at hand-off, not yours mid-task.\n",{"name":5,"source":24,"category":25,"description":7},"obra\u002Fsuperpowers (MIT), adapted","workflow","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fgame-developer\u002Fskills\u002Fincremental-commits",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 incremental-commits",{"tool":41,"command":42},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill incremental-commits",{"tool":44,"command":45},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill incremental-commits","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fgame-developer\u002Fskills\u002Fincremental-commits\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",[],[]]