[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JWSFQHGP5BG6Q8TMVZQ3JE":3,"skill-same:01M6JWSFQHGP5BG6Q8TMVZQ3JE":82},{"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":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6JWSFQHGP5BG6Q8TMVZQ3JE","dev-commit-writer",null,"Write a commit message from a requested Git diff when the user asks for message generation. Does not review, stage, or commit. Requests such as 帮我 commit require the commit workflow, including review when required; asking for a message does not require an explicit skip-review declaration.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJason-chen-coder\u002Fdev-skills\u002Fskills\u002Fdev-commit-writer\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"commit","dev commit writer","dev","writer","when","review","for","commit workflow","requests","as","generation","stage","message","diff","user","write","commit message","git","workflow","2026-11-10 10:12:30",false,"---\nname: dev-commit-writer\ndescription: Write a commit message from a requested Git diff when the user asks for message generation. Does not review, stage, or commit. Requests such as 帮我 commit require the commit workflow, including review when required; asking for a message does not require an explicit skip-review declaration.\n---\n\n# Dev Commit Writer\n\nProduce an accurate, concise commit message in the repository's style. This is a read-only writing task, not a quality verdict or authorization to run `git commit`.\n\n## Load baseline\n\nRead [references\u002Fdev-baseline.md](references\u002Fdev-baseline.md) before execution. Resolve paths relative to this skill directory.\n\n## Read the intended change\n\n- Identify the actual repository root and inspect status, staged diff, unstaged diff, and recent commit subjects\u002Fbodies.\n- Honor explicit `--staged` \u002F `--cached`, `--path=\u003Cglob>`, named files, and exclusions. Without an explicit scope, use the staged diff when present; otherwise use changes attributable to the task. State the chosen scope briefly if mixed changes could cause confusion.\n- Include untracked files only when they belong to the requested change and their content has been inspected. Never silently fold unrelated unstaged work into a message for the index.\n- If there is no change to describe, say so. A user-provided diff is also a valid source, but do not pretend to have inspected a local repository when only that text is available.\n\n## Write the message\n\nFollow repository instructions and dominant recent history for language, prefixes, scope, and body style. If no convention can be established, use a short descriptive subject; Conventional Commits is an acceptable fallback when appropriate. Aim for a subject within 72 characters unless repository rules specify otherwise.\n\nDescribe the concrete behavior or reason for the change. Add a body only to explain a non-obvious motivation, compatibility impact, or related change that the subject cannot cover. Do not invent issue IDs, verification results, breaking-change labels, or review approval.\n\nWhen the diff contains independent changes, provide suggested separate messages or one accurate combined message if that grouping was requested. Do not force a question just because two wordings are possible. Ask only if a material factual ambiguity prevents an accurate message, and provide the supported portion first.\n\nUse artifact references only when task context or inspected content establishes the association and repository convention supports the footer. If `.claude\u002Fartifacts\u002F{designs,plans,fixes}\u002F` exists, it is optional context; omit unrelated or uncertain references without blocking message generation. The presence of one artifact or a similar slug is not sufficient evidence.\n\n## Output and boundaries\n\nReturn the paste-ready message in a code block, with a short scope note only when needed. Do not add a review checklist or claim the code is ready. Preserve the working tree and index: no file edits, `git add`, `git commit`, or `git stash`.\n\nIf the user's request is to perform a commit, continue through the authorized commit workflow rather than misrouting it into message-only mode. Use `dev-code-review` when available and required, or equivalent review; message generation itself does not require asking the user to waive review.\n\n## Multi-Agent Note\n\nMessage generation normally needs no separate agent. The main agent can use inspected diff and history directly; in a larger task, preserve the reviewed commit scope. See `docs\u002Fmulti-agent-policy.md` when this repository is available; standalone use needs no external skill or policy file.\n","# Dev Commit Writer\n\nProduce an accurate, concise commit message in the repository's style. This is a read-only writing task, not a quality verdict or authorization to run `git commit`.\n\n## Load baseline\n\nRead [references\u002Fdev-baseline.md](references\u002Fdev-baseline.md) before execution. Resolve paths relative to this skill directory.\n\n## Read the intended change\n\n- Identify the actual repository root and inspect status, staged diff, unstaged diff, and recent commit subjects\u002Fbodies.\n- Honor explicit `--staged` \u002F `--cached`, `--path=\u003Cglob>`, named files, and exclusions. Without an explicit scope, use the staged diff when present; otherwise use changes attributable to the task. State the chosen scope briefly if mixed changes could cause confusion.\n- Include untracked files only when they belong to the requested change and their content has been inspected. Never silently fold unrelated unstaged work into a message for the index.\n- If there is no change to describe, say so. A user-provided diff is also a valid source, but do not pretend to have inspected a local repository when only that text is available.\n\n## Write the message\n\nFollow repository instructions and dominant recent history for language, prefixes, scope, and body style. If no convention can be established, use a short descriptive subject; Conventional Commits is an acceptable fallback when appropriate. Aim for a subject within 72 characters unless repository rules specify otherwise.\n\nDescribe the concrete behavior or reason for the change. Add a body only to explain a non-obvious motivation, compatibility impact, or related change that the subject cannot cover. Do not invent issue IDs, verification results, breaking-change labels, or review approval.\n\nWhen the diff contains independent changes, provide suggested separate messages or one accurate combined message if that grouping was requested. Do not force a question just because two wordings are possible. Ask only if a material factual ambiguity prevents an accurate message, and provide the supported portion first.\n\nUse artifact references only when task context or inspected content establishes the association and repository convention supports the footer. If `.claude\u002Fartifacts\u002F{designs,plans,fixes}\u002F` exists, it is optional context; omit unrelated or uncertain references without blocking message generation. The presence of one artifact or a similar slug is not sufficient evidence.\n\n## Output and boundaries\n\nReturn the paste-ready message in a code block, with a short scope note only when needed. Do not add a review checklist or claim the code is ready. Preserve the working tree and index: no file edits, `git add`, `git commit`, or `git stash`.\n\nIf the user's request is to perform a commit, continue through the authorized commit workflow rather than misrouting it into message-only mode. Use `dev-code-review` when available and required, or equivalent review; message generation itself does not require asking the user to waive review.\n\n## Multi-Agent Note\n\nMessage generation normally needs no separate agent. The main agent can use inspected diff and history directly; in a larger task, preserve the reviewed commit scope. See `docs\u002Fmulti-agent-policy.md` when this repository is available; standalone use needs no external skill or policy file.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FJason-chen-coder\u002Fdev-skills\u002Fskills\u002Fdev-commit-writer",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill dev-commit-writer",{"tool":64,"command":65},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill dev-commit-writer",{"tool":67,"command":68},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill dev-commit-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJason-chen-coder\u002Fdev-skills\u002Fskills\u002Fdev-commit-writer\u002FSKILL.md",true,[72,78],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"examples.md","REFERENCE","参考文档",1364,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJason-chen-coder\u002Fdev-skills\u002Fskills\u002Fdev-commit-writer\u002Fexamples.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fdev-baseline.md",3571,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJason-chen-coder\u002Fdev-skills\u002Fskills\u002Fdev-commit-writer\u002Freferences\u002Fdev-baseline.md",[83,93,101,109,117,125],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":92},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":92},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":92},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":92},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":92},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":92},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]