[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75W9KHZFVBZENAVJE9BHAP0":3,"skill-same:01M75W9KHZFVBZENAVJE9BHAP0":51},{"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":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":44},"01M75W9KHZFVBZENAVJE9BHAP0","commit",null,"Create well-formatted git commits for changes made during the session","stevengonsalvez\u002Fainb-toolkit","stevengonsalvez","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9320602?v=4","01M75W59QRYZYANWY3XG8CJB1P","Steven Gonsalvez","01M75W59RD5YW1RT67BDV0EAZF",1,"MIT","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fcommit\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: commit\ndescription: Create well-formatted git commits for changes made during the session\nuser-invocable: true\n---\n\n# Commit\n\nRunbook: clean up agent scratch, plan atomic commits, commit by named paths, push per branch-protection rules. Execute steps in order.\n\n## When NOT to use\n- User wants to review a PR before merge → use `\u002Freview` (GitHub PR) or `\u002Fcode-review` (working diff), not this skill.\n- User only wants a commit *message* string, no staging\u002Fcommitting → use `\u002Fcaveman-commit`.\n- No changes staged or unstaged (`git status` clean) → stop, tell user there is nothing to commit.\n\n## Step 0: Announce\nPrint verbatim:\n```\nI'll help you create git commits for the changes in this session.\n\nLet me review what was accomplished and prepare appropriate commits.\n```\n\n## Step 1: Pre-commit cleanup (MANDATORY — do before any staging)\n\n\"Agent scratch\" = any file that exists for the agent's benefit, not the repo's: debug scripts, temp notes, work-tracking markdown, goals\u002Fplans\u002Fresearch\u002Fhandover docs.\n\nRun the scan:\n```bash\ngit status\nls -la .env* env.* *.env 2>\u002Fdev\u002Fnull\nls -la test_*.* debug_*.* tmp_*.* temp_*.* 2>\u002Fdev\u002Fnull\n```\n\nApply this table to each file found:\n\n| File matches | Action |\n|---|---|\n| `.env`, `.env.*`, `*.env` NOT in `.gitignore` | Add pattern to `.gitignore`; never stage the file |\n| debug\u002Ftemp script created this session (`test_*.js`, `debug_*.txt`, `tmp_*.py`) | `rm` it |\n| markdown created this session AND not user-requested | `rm` it |\n| under `.agents\u002F{goals,plans,research,scratch,handover}\u002F` (by intent, any path) | local-only: `git rm --cached` if tracked, ensure dir in `.gitignore` |\n| `.agents\u002Fpr-signals\u002F`, `.agents\u002FMEMORY.md`, other deliberately-tracked agent infra | KEEP |\n| explicitly user-requested doc, essential README\u002FAPI doc | KEEP |\n\nAdd gitignore patterns when needed:\n```bash\nprintf '.env*\\n*.env\\nenv.*\\n' >> .gitignore   # env.* covers env.local-style names the scan surfaces\n```\n\nIf any cleanup is required, present the list and wait for a yes before deleting:\n```\nI found files to clean up before committing:\n- test_oauth.js (debug script → remove)\n- debug_notes.md (work tracking → remove)\n- .env.local (→ add to .gitignore, do not commit)\n\nClean these up before creating commits?\n```\n\nRe-run `git status` after cleanup. Expected: only real deliverables remain untracked\u002Fmodified. If agent scratch still appears → repeat the table before proceeding.\n\n## Step 2: Understand the changes\n```bash\ngit status\ngit diff\ngit diff --staged\n```\nFrom the conversation + diff, identify distinct intents (feature, fix, refactor, test, docs). One intent = one commit. Count the intents now; that count = number of commits.\n\n## Step 3: Plan commits\n\nRules:\n- One commit per single concern. If a diff mixes two intents, split it across two commits.\n- Group implementation with its own tests only if they serve the same concern; otherwise separate.\n- Subject: imperative mood, conventional-commit type, ≤50 chars. Body only when the \"why\" is not obvious from the subject.\n- Focus body on WHY, not a restatement of the diff.\n\nConventional-commit types:\n\n| Type | Use for |\n|---|---|\n| feat | new feature |\n| fix | bug fix |\n| docs | documentation only |\n| style | formatting, no logic change |\n| refactor | restructure, no behavior change |\n| perf | performance improvement |\n| test | add\u002Fupdate tests |\n| build | build system or dependencies |\n| ci | CI\u002FCD config |\n| chore | maintenance |\n\nBreaking change: append `!` after type and add a `BREAKING CHANGE:` footer line.\n\n## Step 4: Present the plan\nShow each commit with its type, summary, exact file list, and full message, then ask:\n```\nBased on the changes, I plan to create N commit(s):\n\nCommit 1 — feat: add OAuth2 authentication support\nFiles:\n- src\u002Fauth\u002Foauth.js\n- src\u002Fauth\u002FtokenStore.js\nMessage:\nfeat: add OAuth2 authentication support\n\n- Implement OAuth2 flow with refresh tokens\n- Add token storage and validation\n\nShall I proceed?\n```\nWait for confirmation before Step 5.\n\n## Step 5: Stage and commit (per commit)\n```bash\ngit add src\u002Fauth\u002Foauth.js src\u002Fauth\u002FtokenStore.js\ngit commit -m \"feat: add OAuth2 authentication support\n\n- Implement OAuth2 flow with refresh tokens\n- Add token storage and validation\"\n```\n\nHard rules:\n- NEVER `git add -A` or `git add .` — stage only the named paths for this commit. Why: bulk-add drags agent scratch into the commit.\n- NEVER add Claude\u002FAI attribution, \"Generated with\", or `Co-Authored-By`. Commit as if the user wrote it; match the repo's existing commit tone.\n- Do not stage debug code, secrets, or temp files.\n- Verify the code works before committing (run the relevant tests\u002Fbuild if not already run this session).\n\nWork in progress — if the session's implementation is incomplete, ask the user which they want before committing:\n1. Commit the completed parts with a clear message.\n2. Create a WIP commit to save progress.\n3. Wait until the feature is complete.\n\nVerify after each commit:\n```bash\ngit log --oneline -n 3\ngit status\n```\n\n## Step 6: Push\n\nDetermine branch and protection:\n```bash\nBRANCH=$(git branch --show-current)\ngit fetch origin\ngit log origin\u002F$BRANCH..HEAD --oneline   # commits that will be pushed\n```\n\nProtected branch = `main`, `master`, or `release\u002F*`.\n\n| Situation | Action |\n|---|---|\n| Feature branch, not on remote | `git push -u origin $BRANCH` (auto) |\n| Feature branch, already tracking | `git push` (auto) |\n| Protected branch | Ask user to confirm (see prompt below); push only on yes |\n| Local behind remote \u002F push rejected | `git pull --rebase` then `git push` |\n| Force push would be needed | STOP — ask explicit permission regardless of branch |\n\nProtected-branch confirmation prompt:\n```\nYou have commits ready to push to $BRANCH (protected).\nConfirm: tests passed, code reviewed, ready to deploy? (yes\u002Fno)\n```\n\nAlways print the commits before pushing:\n```bash\necho \"Pushing to origin\u002F$BRANCH:\"\ngit log origin\u002F$BRANCH..HEAD --oneline\n```\n\nRejection handling — expected outcome and branch:\n```bash\ngit fetch origin\ngit pull --rebase && git push\n```\nIf push still fails after rebase → it is branch protection or permissions, not a sync issue. Do NOT retry the push. Report the failure and offer `gh pr create` instead.\n\nAfter a successful feature-branch push, tell the user they can open a PR with `gh pr create`.\n\n## Quick reference\n```bash\ngit status                                   # what changed\ngit diff                                      # unstaged changes\ngit add src\u002Ffeature.js tests\u002Ffeature.test.js  # stage named paths only\ngit commit -m \"feat: implement new feature\"\ngit log --oneline -10                         # recent commits\ngit commit --amend                            # fix the last commit\ngit reset HEAD file.js                        # unstage\n```\n","# Commit\n\nRunbook: clean up agent scratch, plan atomic commits, commit by named paths, push per branch-protection rules. Execute steps in order.\n\n## When NOT to use\n- User wants to review a PR before merge → use `\u002Freview` (GitHub PR) or `\u002Fcode-review` (working diff), not this skill.\n- User only wants a commit *message* string, no staging\u002Fcommitting → use `\u002Fcaveman-commit`.\n- No changes staged or unstaged (`git status` clean) → stop, tell user there is nothing to commit.\n\n## Step 0: Announce\nPrint verbatim:\n```\nI'll help you create git commits for the changes in this session.\n\nLet me review what was accomplished and prepare appropriate commits.\n```\n\n## Step 1: Pre-commit cleanup (MANDATORY — do before any staging)\n\n\"Agent scratch\" = any file that exists for the agent's benefit, not the repo's: debug scripts, temp notes, work-tracking markdown, goals\u002Fplans\u002Fresearch\u002Fhandover docs.\n\nRun the scan:\n```bash\ngit status\nls -la .env* env.* *.env 2>\u002Fdev\u002Fnull\nls -la test_*.* debug_*.* tmp_*.* temp_*.* 2>\u002Fdev\u002Fnull\n```\n\nApply this table to each file found:\n\n| File matches | Action |\n|---|---|\n| `.env`, `.env.*`, `*.env` NOT in `.gitignore` | Add pattern to `.gitignore`; never stage the file |\n| debug\u002Ftemp script created this session (`test_*.js`, `debug_*.txt`, `tmp_*.py`) | `rm` it |\n| markdown created this session AND not user-requested | `rm` it |\n| under `.agents\u002F{goals,plans,research,scratch,handover}\u002F` (by intent, any path) | local-only: `git rm --cached` if tracked, ensure dir in `.gitignore` |\n| `.agents\u002Fpr-signals\u002F`, `.agents\u002FMEMORY.md`, other deliberately-tracked agent infra | KEEP |\n| explicitly user-requested doc, essential README\u002FAPI doc | KEEP |\n\nAdd gitignore patterns when needed:\n```bash\nprintf '.env*\\n*.env\\nenv.*\\n' >> .gitignore   # env.* covers env.local-style names the scan surfaces\n```\n\nIf any cleanup is required, present the list and wait for a yes before deleting:\n```\nI found files to clean up before committing:\n- test_oauth.js (debug script → remove)\n- debug_notes.md (work tracking → remove)\n- .env.local (→ add to .gitignore, do not commit)\n\nClean these up before creating commits?\n```\n\nRe-run `git status` after cleanup. Expected: only real deliverables remain untracked\u002Fmodified. If agent scratch still appears → repeat the table before proceeding.\n\n## Step 2: Understand the changes\n```bash\ngit status\ngit diff\ngit diff --staged\n```\nFrom the conversation + diff, identify distinct intents (feature, fix, refactor, test, docs). One intent = one commit. Count the intents now; that count = number of commits.\n\n## Step 3: Plan commits\n\nRules:\n- One commit per single concern. If a diff mixes two intents, split it across two commits.\n- Group implementation with its own tests only if they serve the same concern; otherwise separate.\n- Subject: imperative mood, conventional-commit type, ≤50 chars. Body only when the \"why\" is not obvious from the subject.\n- Focus body on WHY, not a restatement of the diff.\n\nConventional-commit types:\n\n| Type | Use for |\n|---|---|\n| feat | new feature |\n| fix | bug fix |\n| docs | documentation only |\n| style | formatting, no logic change |\n| refactor | restructure, no behavior change |\n| perf | performance improvement |\n| test | add\u002Fupdate tests |\n| build | build system or dependencies |\n| ci | CI\u002FCD config |\n| chore | maintenance |\n\nBreaking change: append `!` after type and add a `BREAKING CHANGE:` footer line.\n\n## Step 4: Present the plan\nShow each commit with its type, summary, exact file list, and full message, then ask:\n```\nBased on the changes, I plan to create N commit(s):\n\nCommit 1 — feat: add OAuth2 authentication support\nFiles:\n- src\u002Fauth\u002Foauth.js\n- src\u002Fauth\u002FtokenStore.js\nMessage:\nfeat: add OAuth2 authentication support\n\n- Implement OAuth2 flow with refresh tokens\n- Add token storage and validation\n\nShall I proceed?\n```\nWait for confirmation before Step 5.\n\n## Step 5: Stage and commit (per commit)\n```bash\ngit add src\u002Fauth\u002Foauth.js src\u002Fauth\u002FtokenStore.js\ngit commit -m \"feat: add OAuth2 authentication support\n\n- Implement OAuth2 flow with refresh tokens\n- Add token storage and validation\"\n```\n\nHard rules:\n- NEVER `git add -A` or `git add .` — stage only the named paths for this commit. Why: bulk-add drags agent scratch into the commit.\n- NEVER add Claude\u002FAI attribution, \"Generated with\", or `Co-Authored-By`. Commit as if the user wrote it; match the repo's existing commit tone.\n- Do not stage debug code, secrets, or temp files.\n- Verify the code works before committing (run the relevant tests\u002Fbuild if not already run this session).\n\nWork in progress — if the session's implementation is incomplete, ask the user which they want before committing:\n1. Commit the completed parts with a clear message.\n2. Create a WIP commit to save progress.\n3. Wait until the feature is complete.\n\nVerify after each commit:\n```bash\ngit log --oneline -n 3\ngit status\n```\n\n## Step 6: Push\n\nDetermine branch and protection:\n```bash\nBRANCH=$(git branch --show-current)\ngit fetch origin\ngit log origin\u002F$BRANCH..HEAD --oneline   # commits that will be pushed\n```\n\nProtected branch = `main`, `master`, or `release\u002F*`.\n\n| Situation | Action |\n|---|---|\n| Feature branch, not on remote | `git push -u origin $BRANCH` (auto) |\n| Feature branch, already tracking | `git push` (auto) |\n| Protected branch | Ask user to confirm (see prompt below); push only on yes |\n| Local behind remote \u002F push rejected | `git pull --rebase` then `git push` |\n| Force push would be needed | STOP — ask explicit permission regardless of branch |\n\nProtected-branch confirmation prompt:\n```\nYou have commits ready to push to $BRANCH (protected).\nConfirm: tests passed, code reviewed, ready to deploy? (yes\u002Fno)\n```\n\nAlways print the commits before pushing:\n```bash\necho \"Pushing to origin\u002F$BRANCH:\"\ngit log origin\u002F$BRANCH..HEAD --oneline\n```\n\nRejection handling — expected outcome and branch:\n```bash\ngit fetch origin\ngit pull --rebase && git push\n```\nIf push still fails after rebase → it is branch protection or permissions, not a sync issue. Do NOT retry the push. Report the failure and offer `gh pr create` instead.\n\nAfter a successful feature-branch push, tell the user they can open a PR with `gh pr create`.\n\n## Quick reference\n```bash\ngit status                                   # what changed\ngit diff                                      # unstaged changes\ngit add src\u002Ffeature.js tests\u002Ffeature.test.js  # stage named paths only\ngit commit -m \"feat: implement new feature\"\ngit log --oneline -10                         # recent commits\ngit commit --amend                            # fix the last commit\ngit reset HEAD file.js                        # unstage\n```\n",{"name":5,"description":7,"user-invocable":24},true,"main","9cf32d1e636db09530158af14ba301bfa5d401e9","skills\u002Fcommit","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez","stevengonsalvez.com","2026-11-12 00:50:59",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add stevengonsalvez\u002Fainb-toolkit --skill commit",{"tool":38,"command":39},"bunx","bunx skills add stevengonsalvez\u002Fainb-toolkit --skill commit",{"tool":41,"command":42},"pnpm","pnpm dlx skills add stevengonsalvez\u002Fainb-toolkit --skill commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fcommit\u002FSKILL.md",[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"assets\u002Fcodereview-checklist.md","ASSET","资产文件",3080,"https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fcommit\u002Fassets\u002Fcodereview-checklist.md",[52,59,66,72,79,86],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M75WK9B8DKVJBJJ4CX2QMJMX","well-formed","Fixture skill that satisfies every mechanical rule, used to prove the conformance check passes a clean tree instead of failing everything.","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fagentskills\u002Fclean\u002Fwell-formed\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M75WK6ZGDXJJN8879K49QEYG","underscore-tools","Fixture skill that spells the tool allowlist key with an underscore instead of the hyphen the spec requires.","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fagentskills\u002Fbroken\u002Funderscore-tools\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"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":69,"categories":70,"keywords":71,"publishedAt":19},"01M75WK524MVT2H9E27ZCEA3HR","no-frontmatter","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fagentskills\u002Fbroken\u002Fno-frontmatter\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M75WJWZBMKR8R60PG3T3MCCC","long-description","Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling. Fixture skill with a deliberately oversized description used to prove the conformance check rejects anything past the 1024 character ceiling.","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fagentskills\u002Fbroken\u002Flong-description\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M75WJVRH3J22WKED7E5D01S8","some-other-name","Fixture skill whose frontmatter name does not match its parent directory name.","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fagentskills\u002Fbroken\u002Fdir-mismatch\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M75WJTC7H5FRP6S129VBSMZC","bad_Name","Fixture skill whose name uses an underscore and a capital letter, so it violates the agentskills.io name pattern.","https:\u002F\u002Fgithub.com\u002Fstevengonsalvez\u002Fainb-toolkit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fagentskills\u002Fbroken\u002Fbad_Name\u002FSKILL.md",[],[]]