[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EN449M9ASZHTCP8MDQ1QP0":3,"skill-same:01M7EN449M9ASZHTCP8MDQ1QP0":47},{"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":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EN449M9ASZHTCP8MDQ1QP0","git-commit-helper-guide",null,"A practical guide to crafting atomic commits and clear Conventional-Commit messages — use when committing or standardizing team history.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-git-commit-helper-guide\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: git-commit-helper-guide\ndescription: A practical guide to crafting atomic commits and clear Conventional-Commit messages — use when committing or standardizing team history.\ncategory: git\n---\n\n## Overview\n\nGood commits are small, self-explanatory units of change with messages that tell\nfuture readers why the change exists. This guide covers the full craft:\nsplitting work into atomic commits, writing messages in the Conventional\nCommits style, and keeping branch history reviewable — whether you write\nmessages by hand or draft them with AI assistance.\n\n## When to use\n\n- Turning a messy working tree into clean, logical commits\n- Writing commit messages that explain rationale, not just content\n- Adopting Conventional Commits (`feat:`, `fix:`) on a team\n- Tidying a branch before opening a pull request\n- Reviewing commit quality in code review\n\n## Core concepts\n\n**Atomicity.** Each commit should contain one logical change, build cleanly,\nand be independently revertable. A commit that \"fixes the login bug\" shouldn't\nalso reformat unrelated files. Use `git add -p` to stage hunks selectively\nand split work that grew together.\n\n**Conventional Commits format.** `type(scope): subject` — e.g.\n`fix(auth): handle expired refresh tokens`. Common types: `feat`, `fix`,\n`docs`, `refactor`, `test`, `chore`, `perf`. Scopes name the affected area.\nA `BREAKING CHANGE:` footer flags incompatible changes. The format makes\nhistory searchable and changelogs automatable.\n\n**Subject line discipline.** Imperative mood (\"Add\", not \"Added\"), under ~72\ncharacters, no trailing period. It should complete the sentence \"This commit\nwill…\". Everything else goes in the body.\n\n**The body carries the why.** Diffs show what changed; bodies explain the\nreasoning: the bug or requirement, alternatives considered, risks, and links\nto issues or discussions. A body written today saves an hour of archaeology\nin six months.\n\n**Private history is malleable; public history is not.** Rebase, squash, and\nreword freely on branches only you use. Once pushed and shared, prefer\n`git revert` over rewriting — your teammates' clones depend on stable history.\n\n## Practical workflow\n\n1. **Inspect before committing:** `git status` and `git diff` — confirm the\n   staged changes are exactly one logical unit; split with `git add -p` if not.\n2. **Draft the message:** type + scope + imperative subject; body with\n   context, rationale, and issue references; breaking changes in the footer.\n3. **Example:**\n   ```text\n   feat(payments): retry failed webhooks with exponential backoff\n\n   Webhook delivery failures during the provider outage (INC-118) were\n   dropped silently. Adds a retry queue: 3 attempts, backoff 1m\u002F5m\u002F30m,\n   then dead-letter with an alert.\n\n   Chose backoff over immediate retry to avoid hammering the provider\n   during partial outages. Fixes #482.\n   ```\n4. **Tidy before sharing:** `git rebase -i main` to squash \"wip\"\u002F\"fix typo\"\n   commits, reorder logically, and strengthen weak messages.\n5. **Verify:** `git log --oneline -8` should read as a coherent story; each\n   commit message should make sense without opening the diff.\n6. **If using AI to draft messages:** always review the generated \"why\" —\n   models write plausible rationale that may not match your actual reasoning;\n   correct it before committing.\n\n## Common pitfalls\n\n- **Vague subjects** (\"update\", \"fix bug\", \"changes\") — permanent noise in\n  `git log` and `git blame`.\n- **Mega-commits** bundling unrelated changes — unreviewable and dangerous to\n  revert; split them.\n- **Body that restates the diff** — \"changed X to Y\" adds nothing; explain the\n  decision instead.\n- **Forgetting the issue link** — without a reference, the business context\n  behind a fix evaporates.\n- **Amending or rebasing shared branches** — rewrites history others depend\n  on; restrict rewriting to private branches.\n- **Inconsistent types\u002Fscopes** across the team — half the history using\n  `feat:` and half using freeform defeats the purpose; agree once, lint in CI.\n","## Overview\n\nGood commits are small, self-explanatory units of change with messages that tell\nfuture readers why the change exists. This guide covers the full craft:\nsplitting work into atomic commits, writing messages in the Conventional\nCommits style, and keeping branch history reviewable — whether you write\nmessages by hand or draft them with AI assistance.\n\n## When to use\n\n- Turning a messy working tree into clean, logical commits\n- Writing commit messages that explain rationale, not just content\n- Adopting Conventional Commits (`feat:`, `fix:`) on a team\n- Tidying a branch before opening a pull request\n- Reviewing commit quality in code review\n\n## Core concepts\n\n**Atomicity.** Each commit should contain one logical change, build cleanly,\nand be independently revertable. A commit that \"fixes the login bug\" shouldn't\nalso reformat unrelated files. Use `git add -p` to stage hunks selectively\nand split work that grew together.\n\n**Conventional Commits format.** `type(scope): subject` — e.g.\n`fix(auth): handle expired refresh tokens`. Common types: `feat`, `fix`,\n`docs`, `refactor`, `test`, `chore`, `perf`. Scopes name the affected area.\nA `BREAKING CHANGE:` footer flags incompatible changes. The format makes\nhistory searchable and changelogs automatable.\n\n**Subject line discipline.** Imperative mood (\"Add\", not \"Added\"), under ~72\ncharacters, no trailing period. It should complete the sentence \"This commit\nwill…\". Everything else goes in the body.\n\n**The body carries the why.** Diffs show what changed; bodies explain the\nreasoning: the bug or requirement, alternatives considered, risks, and links\nto issues or discussions. A body written today saves an hour of archaeology\nin six months.\n\n**Private history is malleable; public history is not.** Rebase, squash, and\nreword freely on branches only you use. Once pushed and shared, prefer\n`git revert` over rewriting — your teammates' clones depend on stable history.\n\n## Practical workflow\n\n1. **Inspect before committing:** `git status` and `git diff` — confirm the\n   staged changes are exactly one logical unit; split with `git add -p` if not.\n2. **Draft the message:** type + scope + imperative subject; body with\n   context, rationale, and issue references; breaking changes in the footer.\n3. **Example:**\n   ```text\n   feat(payments): retry failed webhooks with exponential backoff\n\n   Webhook delivery failures during the provider outage (INC-118) were\n   dropped silently. Adds a retry queue: 3 attempts, backoff 1m\u002F5m\u002F30m,\n   then dead-letter with an alert.\n\n   Chose backoff over immediate retry to avoid hammering the provider\n   during partial outages. Fixes #482.\n   ```\n4. **Tidy before sharing:** `git rebase -i main` to squash \"wip\"\u002F\"fix typo\"\n   commits, reorder logically, and strengthen weak messages.\n5. **Verify:** `git log --oneline -8` should read as a coherent story; each\n   commit message should make sense without opening the diff.\n6. **If using AI to draft messages:** always review the generated \"why\" —\n   models write plausible rationale that may not match your actual reasoning;\n   correct it before committing.\n\n## Common pitfalls\n\n- **Vague subjects** (\"update\", \"fix bug\", \"changes\") — permanent noise in\n  `git log` and `git blame`.\n- **Mega-commits** bundling unrelated changes — unreviewable and dangerous to\n  revert; split them.\n- **Body that restates the diff** — \"changed X to Y\" adds nothing; explain the\n  decision instead.\n- **Forgetting the issue link** — without a reference, the business context\n  behind a fix evaporates.\n- **Amending or rebasing shared branches** — rewrites history others depend\n  on; restrict rewriting to private branches.\n- **Inconsistent types\u002Fscopes** across the team — half the history using\n  `feat:` and half using freeform defeats the purpose; agree once, lint in CI.\n",{"name":5,"category":24,"description":7},"git","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-git-commit-helper-guide",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill git-commit-helper-guide",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill git-commit-helper-guide",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill git-commit-helper-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-git-commit-helper-guide\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"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},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\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":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\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},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\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},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\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},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\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},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]