[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M753V3P90DJ66W50MW1RFFHG":3,"skill-same:01M753V3P90DJ66W50MW1RFFHG":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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M753V3P90DJ66W50MW1RFFHG","git-commit",null,"Use when staging changes and creating a git commit — derive a conventional-commit message from the diff and run the commit safely. Review before staging (never blind `git add .`), write multi-paragraph bodies via `-F`\u002Fheredoc (never chained `-m`), keep unwanted trailers out, and check the branch first. Covers the full local flow through verify and optional amend; stops before push — hand off to \u002Frelease for tagging and publishing.","jabworks\u002Fagentic-toolkit","jabworks","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F159094119?v=4","01M753P4JBZBTT7WN1PJBPZJZP","JAB Works","01M753P4K5KDGEWGXWT811BZET",2,"MIT","https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fgit-commit\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: git-commit\ndescription: Use when staging changes and creating a git commit — derive a conventional-commit message from the diff and run the commit safely. Review before staging (never blind `git add .`), write multi-paragraph bodies via `-F`\u002Fheredoc (never chained `-m`), keep unwanted trailers out, and check the branch first. Covers the full local flow through verify and optional amend; stops before push — hand off to \u002Frelease for tagging and publishing.\n---\n\n# git-commit\n\nCraft a conventional-commit message from the actual diff and run the commit **safely**. The message format matters, but the real value is *how* the git commands run — the four guardrails below exist because these are where commits go wrong.\n\n## When to use\n\n- The user asks to commit, \"save this\", or \"make a commit\".\n- You've finished a unit of work and changes are ready to record locally.\n- A messy working tree needs splitting into clean, logical commits.\n\nNot for: pushing, opening PRs, rebasing, cherry-picking. For choosing *which* git operation fits a situation, see the **git-operations** skill.\n\n## Flow\n\n```\n1. Inspect     git status  +  git diff        (see everything before touching the index)\n2. Branch chk  git branch --show-current       (on main\u002Fdefault? → guardrail 4)\n3. Stage       git add \u003Cexplicit pathspecs>    (never -A \u002F . — guardrail 1)\n4. Compose     type(scope): subject + body     (derive from the diff, confirm)\n5. Commit      git commit -F \u003Cmsgfile>          (multiline-safe — guardrail 2)\n6. Verify      git show --stat  \u002F  git log -1\n7. Optional    amend \u002F fixup on unpushed local commits only\n```\n\n## Guardrails\n\nThese are non-negotiable. Each is a \"never \u002F always\" pair with the exact command.\n\n### 1. Never blind-stage\n\n**Never** `git add .`, `git add -A`, or `git add -u`. They sweep in unrelated edits, stray debug files, and secrets.\n\n**Always** review first, then stage explicit pathspecs:\n\n```bash\ngit status               # what's changed and what's untracked\ngit diff                 # unstaged changes, in detail\ngit diff --staged        # anything already staged\ngit add path\u002Fto\u002Fa path\u002Fto\u002Fb   # only the paths this commit is about\n```\n\nUntracked files are surfaced to the user, never auto-added. If unsure whether a file belongs, ask.\n\n### 2. Never chain `-m` for bodies\n\n**Never** build a body\u002Ffooter from repeated `-m` flags (`-m subject -m body -m footer`) — it mangles blank lines and wrapping.\n\n**Always** write the full message to a file and commit with `-F`:\n\n```bash\n# compose the message (subject, blank line, body, blank line, footer)\ncat > \"$(git rev-parse --git-dir)\u002FCOMMIT_EDIT.tmp\" \u003C\u003C'EOF'\ntype(scope): short imperative subject\n\nBody paragraph explaining what changed and why. Wrap at ~72 cols.\n\nRefs: #123\nEOF\ngit commit -F \"$(git rev-parse --git-dir)\u002FCOMMIT_EDIT.tmp\"\nrm -f \"$(git rev-parse --git-dir)\u002FCOMMIT_EDIT.tmp\"\n```\n\nA single-line subject with no body may use `git commit -m \"type(scope): subject\"` — the ban is only on chaining `-m` for multi-part messages.\n\n### 3. Never inject trailers\n\n**Never** add `Co-Authored-By:`, tool attribution, or any trailer the user didn't ask for. Guard the footer block — only `Refs:`, `Fixes:`, `BREAKING CHANGE:`, or trailers the user explicitly requested belong there.\n\n### 4. Check the branch first\n\n**Always** confirm the branch before committing:\n\n```bash\ngit branch --show-current\n```\n\nIf it's `main`, `master`, or the default branch, **stop** and offer to branch before committing:\n\n```bash\ngit switch -c \u003Cdescriptive-branch-name>   # NOT: git checkout -b\n```\n\nProceed on the protected branch only if the user explicitly confirms.\n\n## Composing the message\n\nConventional-commit shape: `type(scope): subject`. See `references\u002Fcommit-types.md` for the type\u002Fscope cheat-sheet and copy-paste templates.\n\n- **Subject:** imperative mood, ≤ ~50 chars, no trailing period.\n- **Body:** the *why*, not a restatement of the diff. Optional for trivial changes.\n- **Footer:** issue refs \u002F `BREAKING CHANGE:` only.\n\n## Interaction model — derive, then confirm\n\nRead the staged diff, derive the `type`, `scope`, and message, and **present it for confirmation** before committing:\n\n- The diff usually reveals intent — lead with a concrete proposed message, don't interrogate.\n- **Fall back to asking** when the diff spans unrelated concerns (that's a signal to split — see below) or when intent is genuinely ambiguous.\n\n## Splitting a mixed working tree\n\nWhen changes cover unrelated concerns, make several logical commits instead of one:\n\n```bash\ngit add \u003Cpaths for concern A> && git commit -F \u003Cmsg A>\ngit add \u003Cpaths for concern B> && git commit -F \u003Cmsg B>\n# same-file, different concerns → stage by hunk:\ngit add -p path\u002Fto\u002Ffile\n```\n\nEach commit should stand on its own and pass review independently.\n\n## ⚙ Adjust these (defaults)\n\nThe commands above are generic. This toolkit's owner uses these defaults — swap them for your own:\n\n- **Signoff:** add `-s` to every commit (`git commit -s -F …`) for a `Signed-off-by` trailer.\n- **No co-author trailers** — this is guardrail 3, kept even when adjusting.\n\nIf you don't use signoff, drop `-s`; everything else stays.\n\n## See also\n\n- `release` — after commits land: machinery detection, dry-run plan, then tag → push → GitHub release.\n- `git-operations` — undoing, discarding, parking, and recovery.\n","# git-commit\n\nCraft a conventional-commit message from the actual diff and run the commit **safely**. The message format matters, but the real value is *how* the git commands run — the four guardrails below exist because these are where commits go wrong.\n\n## When to use\n\n- The user asks to commit, \"save this\", or \"make a commit\".\n- You've finished a unit of work and changes are ready to record locally.\n- A messy working tree needs splitting into clean, logical commits.\n\nNot for: pushing, opening PRs, rebasing, cherry-picking. For choosing *which* git operation fits a situation, see the **git-operations** skill.\n\n## Flow\n\n```\n1. Inspect     git status  +  git diff        (see everything before touching the index)\n2. Branch chk  git branch --show-current       (on main\u002Fdefault? → guardrail 4)\n3. Stage       git add \u003Cexplicit pathspecs>    (never -A \u002F . — guardrail 1)\n4. Compose     type(scope): subject + body     (derive from the diff, confirm)\n5. Commit      git commit -F \u003Cmsgfile>          (multiline-safe — guardrail 2)\n6. Verify      git show --stat  \u002F  git log -1\n7. Optional    amend \u002F fixup on unpushed local commits only\n```\n\n## Guardrails\n\nThese are non-negotiable. Each is a \"never \u002F always\" pair with the exact command.\n\n### 1. Never blind-stage\n\n**Never** `git add .`, `git add -A`, or `git add -u`. They sweep in unrelated edits, stray debug files, and secrets.\n\n**Always** review first, then stage explicit pathspecs:\n\n```bash\ngit status               # what's changed and what's untracked\ngit diff                 # unstaged changes, in detail\ngit diff --staged        # anything already staged\ngit add path\u002Fto\u002Fa path\u002Fto\u002Fb   # only the paths this commit is about\n```\n\nUntracked files are surfaced to the user, never auto-added. If unsure whether a file belongs, ask.\n\n### 2. Never chain `-m` for bodies\n\n**Never** build a body\u002Ffooter from repeated `-m` flags (`-m subject -m body -m footer`) — it mangles blank lines and wrapping.\n\n**Always** write the full message to a file and commit with `-F`:\n\n```bash\n# compose the message (subject, blank line, body, blank line, footer)\ncat > \"$(git rev-parse --git-dir)\u002FCOMMIT_EDIT.tmp\" \u003C\u003C'EOF'\ntype(scope): short imperative subject\n\nBody paragraph explaining what changed and why. Wrap at ~72 cols.\n\nRefs: #123\nEOF\ngit commit -F \"$(git rev-parse --git-dir)\u002FCOMMIT_EDIT.tmp\"\nrm -f \"$(git rev-parse --git-dir)\u002FCOMMIT_EDIT.tmp\"\n```\n\nA single-line subject with no body may use `git commit -m \"type(scope): subject\"` — the ban is only on chaining `-m` for multi-part messages.\n\n### 3. Never inject trailers\n\n**Never** add `Co-Authored-By:`, tool attribution, or any trailer the user didn't ask for. Guard the footer block — only `Refs:`, `Fixes:`, `BREAKING CHANGE:`, or trailers the user explicitly requested belong there.\n\n### 4. Check the branch first\n\n**Always** confirm the branch before committing:\n\n```bash\ngit branch --show-current\n```\n\nIf it's `main`, `master`, or the default branch, **stop** and offer to branch before committing:\n\n```bash\ngit switch -c \u003Cdescriptive-branch-name>   # NOT: git checkout -b\n```\n\nProceed on the protected branch only if the user explicitly confirms.\n\n## Composing the message\n\nConventional-commit shape: `type(scope): subject`. See `references\u002Fcommit-types.md` for the type\u002Fscope cheat-sheet and copy-paste templates.\n\n- **Subject:** imperative mood, ≤ ~50 chars, no trailing period.\n- **Body:** the *why*, not a restatement of the diff. Optional for trivial changes.\n- **Footer:** issue refs \u002F `BREAKING CHANGE:` only.\n\n## Interaction model — derive, then confirm\n\nRead the staged diff, derive the `type`, `scope`, and message, and **present it for confirmation** before committing:\n\n- The diff usually reveals intent — lead with a concrete proposed message, don't interrogate.\n- **Fall back to asking** when the diff spans unrelated concerns (that's a signal to split — see below) or when intent is genuinely ambiguous.\n\n## Splitting a mixed working tree\n\nWhen changes cover unrelated concerns, make several logical commits instead of one:\n\n```bash\ngit add \u003Cpaths for concern A> && git commit -F \u003Cmsg A>\ngit add \u003Cpaths for concern B> && git commit -F \u003Cmsg B>\n# same-file, different concerns → stage by hunk:\ngit add -p path\u002Fto\u002Ffile\n```\n\nEach commit should stand on its own and pass review independently.\n\n## ⚙ Adjust these (defaults)\n\nThe commands above are generic. This toolkit's owner uses these defaults — swap them for your own:\n\n- **Signoff:** add `-s` to every commit (`git commit -s -F …`) for a `Signed-off-by` trailer.\n- **No co-author trailers** — this is guardrail 3, kept even when adjusting.\n\nIf you don't use signoff, drop `-s`; everything else stays.\n\n## See also\n\n- `release` — after commits land: machinery detection, dry-run plan, then tag → push → GitHub release.\n- `git-operations` — undoing, discarding, parking, and recovery.\n",{"name":5,"description":7},"main","5277649b071c1c0cdf4f15eee861b1608fc1bbcb","skills\u002Fgit-commit",0,"https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit","https:\u002F\u002Fgithub.com\u002Fjabworks","2026-11-03 15:03:51",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add jabworks\u002Fagentic-toolkit --skill git-commit",{"tool":37,"command":38},"bunx","bunx skills add jabworks\u002Fagentic-toolkit --skill git-commit",{"tool":40,"command":41},"pnpm","pnpm dlx skills add jabworks\u002Fagentic-toolkit --skill git-commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fgit-commit\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fcommit-types.md","REFERENCE","参考文档",2376,"https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fgit-commit\u002Freferences\u002Fcommit-types.md",[52,58,64,71,78,85],{"skillNo":53,"name":54,"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":55,"categories":56,"keywords":57,"publishedAt":19},"01M7540BPNTFZH7V41P5E2S692","orphan","https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fcomposition\u002Fbad\u002Fskills\u002Forphan\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"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":61,"categories":62,"keywords":63,"publishedAt":19},"01M7540AG2KFTQ8DJMNV6806MV","no-blurb","https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fcomposition\u002Fbad\u002Fskills\u002Fno-blurb\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M75404N306PY1JFPQ0GGNTYB","workflow","Routes any dev task into the right execution tier (Small\u002FMedium\u002FLarge) and carries condux's operating rules — proportional effort, lazy skill loading, soft gates, implement-yourself-by-default.","https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M753ZZ6TTA06GRJAG679BQ2H","usage-trace","Checks and manages durable, local usage capture — ingest, health status, and the opt-in limit snapshot — for Claude Code and Codex. Capture itself runs automatically at session start.","https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fusage-trace\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M753ZSKJSF8WFS7AXR2N65SE","toolkit-skill-standards","Use when writing or reviewing a SKILL.md for jabworks\u002Fagentic-toolkit — frontmatter budgets, the trigger contract (\"Use when…\" description or when_to_use field), progressive disclosure into references\u002F, and keeping a new description out of existing skills' trigger space. Triggers include \"review this skill description\", \"write the frontmatter\", \"does this collide with an existing skill\", \"where should this content live\". Not for scaffold\u002Fsync mechanics; use toolkit-foundry.","https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Ftoolkit-skill-standards\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M753ZKX3KTVYWX15A9A0WZN0","toolkit-research-frontier","Use when planning improvement work on jabworks\u002Fagentic-toolkit itself — open problems (trigger-collision automation, YAML-strict frontmatter checks, docs-catalog enforcement), existing assets, the next three concrete steps, and the four-front library-health campaign with commands and success criteria. Triggers include \"let's improve our toolkit\", \"let's improve this repo\", \"what should we improve next\", \"toolkit roadmap\", \"open problems\", \"run the health campaign\".","https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Ftoolkit-research-frontier\u002FSKILL.md",[],[]]