[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MM0AHHANT6H6YC8XY3DMK7":3,"skill-same:01M6MM0AHHANT6H6YC8XY3DMK7":77},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":66},"01M6MM0AHHANT6H6YC8XY3DMK7","explain-diff",null,"Use when the user asks to explain, understand, or describe a code change: a branch, pull request, commit, diff, or patch, such as 'explain what branch X does' or 'what does this PR change', even when bro is also active or the diff is pasted inline. Also use it when the user did not understand a reply or a concept, or asks to explain it better or to give a real example; at the end of planned work, after its checks and review; and to write or update a pull request description.","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\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Fexplain-diff\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"explain","explain diff","diff","limits","grep","write","read","trade","change","verification","code","visual","Bash","effects","true","trade-offs","scope","2026-11-10 10:12:30",false,"---\nname: explain-diff\ndescription: \"Use when the user asks to explain, understand, or describe a code change: a branch, pull request, commit, diff, or patch, such as 'explain what branch X does' or 'what does this PR change', even when bro is also active or the diff is pasted inline. Also use it when the user did not understand a reply or a concept, or asks to explain it better or to give a real example; at the end of planned work, after its checks and review; and to write or update a pull request description.\"\nargument-hint: \"[--visual] [scope]\"\nuser-invocable: true\nallowed-tools: Glob, Grep, Read, Bash, Write, AskUserQuestion, Artifact, Skill\n---\n\n# Explain diff\n\nPeople often no longer read the code that agents write.\nThis explanation is how a person learns what was built, how it works, and why, well enough to own it.\nWrite for someone who knows nothing about the project or the task: first invoke `development-skills:bro` for this output.\n\n## Gather the facts\n\nUse the scope the user names: a branch, range, pull request, commit, or patch. Default to the work just finished.\nRead the request, the plan and chronicle, the final diff, the check results, and the review verdict.\nCheck the behavior you describe in the code, and in real data and logs when they settle a claim.\nCall a claim you could not check unchecked, and say what is missing.\nChange no repository file.\n\n## Write the explanation\n\nWrite these parts in this order, and skip a part that has nothing to say:\n\n1. **What changed:** the result for the people or systems that use it compared with before, and the problem it solves, in two or three sentences.\n2. **Concepts:** each functional, business, or technical idea the solution rests on, such as an idempotency key or a dead-letter queue. Explain it in plain words, then say where this change uses it.\n3. **Flow:** follow one real case from input to result, with real values from the data, tests, or logs. Show what is read, stored, sent, or shown at each step.\n4. **Edge cases and errors:** what happens with missing or duplicate data, a timeout, or a failing dependency, and what a user or operator sees.\n5. **Choices and limits:** the alternatives the work rejected and why, the trade-offs, and what stays unchecked.\n\nExplain each term the first time it appears, including common technical ones such as hash, lock, or transaction.\nUse the names a person sees or operates: endpoints, tables, queues, settings, screens, log messages.\nLeave out internal files, functions, classes, variables, and code settings unless the user asks for them.\nDraw a small text diagram when the flow branches.\nFor planned work, keep it to about one screen. For a small change, write a few lines.\nAt the end of planned work, give the explanation and the questions in their own message, before the next step such as `align-docs`.\n\n## Explain a reply or a concept\n\nWhen the user did not understand a reply or a concept, explain that point only.\nUse the parts that fit and a real case from this project.\nKeep every fact of the earlier reply, and ask no understanding questions unless the user asks for them.\n\n## Check understanding\n\nAfter planned work, ask two or three questions about the most important concepts: behavior, flow, or a technical choice.\nThe explanation alone must be enough to answer them, without opening the code.\nAsk them in one call to the question tool.\nEach question is a concrete scenario with three plausible answers: one correct, and two that a reasonable person could believe.\nShuffle the three answers and mark none as recommended. Add a fourth option last, \"I don't know, explain\", in the user's language.\nThe free text field stays open for another answer.\n\n- Good: \"A client sends the same order again after a timeout. How many orders are in the database?\"\n- Bad: \"Which function handles the retry?\"\n\n## Recap the answers\n\nAfter the user answers, write a recap in chat. For each question, show the question, the user's answer, and \"correct\", \"wrong\", or \"skipped\".\n\"I don't know, explain\" counts as skipped. For a wrong or skipped answer, explain the correct answer with a different example.\nA wrong answer can mean two things: the user lacks a concept, or the user wanted the system to behave that way.\nFor each wrong answer, say which one the answer suggests, and why.\nWhen the user wanted a different behavior, check whether the code or the requirement is wrong before you correct the user.\n\nThen ask with the question tool how to continue, and wait for the answer before the next step:\n\n- All answers correct: continue (recommended), more questions, or more explanation.\n- Some answers wrong: review the work on those points, more questions or explanation, or continue. Recommend the option that matches what the wrong answers suggest.\n\nTo review the work, settle the new requirement with the user, then change the work, repeat its checks and review, and explain the changed part again.\n\n## Visual mode\n\nWith `--visual`, or when the user asks for it, also build a page the user can step through: read [visual mode](references\u002Fvisual-mode.md).\nWhen the flow has states, ordering, or branches that are hard to follow in text, offer the page in one line.\n\n## Pull request description\n\nUse the same parts for a reviewer who knows nothing about the project or the task: read [pull request](references\u002Fpull-request.md).\n","# Explain diff\n\nPeople often no longer read the code that agents write.\nThis explanation is how a person learns what was built, how it works, and why, well enough to own it.\nWrite for someone who knows nothing about the project or the task: first invoke `development-skills:bro` for this output.\n\n## Gather the facts\n\nUse the scope the user names: a branch, range, pull request, commit, or patch. Default to the work just finished.\nRead the request, the plan and chronicle, the final diff, the check results, and the review verdict.\nCheck the behavior you describe in the code, and in real data and logs when they settle a claim.\nCall a claim you could not check unchecked, and say what is missing.\nChange no repository file.\n\n## Write the explanation\n\nWrite these parts in this order, and skip a part that has nothing to say:\n\n1. **What changed:** the result for the people or systems that use it compared with before, and the problem it solves, in two or three sentences.\n2. **Concepts:** each functional, business, or technical idea the solution rests on, such as an idempotency key or a dead-letter queue. Explain it in plain words, then say where this change uses it.\n3. **Flow:** follow one real case from input to result, with real values from the data, tests, or logs. Show what is read, stored, sent, or shown at each step.\n4. **Edge cases and errors:** what happens with missing or duplicate data, a timeout, or a failing dependency, and what a user or operator sees.\n5. **Choices and limits:** the alternatives the work rejected and why, the trade-offs, and what stays unchecked.\n\nExplain each term the first time it appears, including common technical ones such as hash, lock, or transaction.\nUse the names a person sees or operates: endpoints, tables, queues, settings, screens, log messages.\nLeave out internal files, functions, classes, variables, and code settings unless the user asks for them.\nDraw a small text diagram when the flow branches.\nFor planned work, keep it to about one screen. For a small change, write a few lines.\nAt the end of planned work, give the explanation and the questions in their own message, before the next step such as `align-docs`.\n\n## Explain a reply or a concept\n\nWhen the user did not understand a reply or a concept, explain that point only.\nUse the parts that fit and a real case from this project.\nKeep every fact of the earlier reply, and ask no understanding questions unless the user asks for them.\n\n## Check understanding\n\nAfter planned work, ask two or three questions about the most important concepts: behavior, flow, or a technical choice.\nThe explanation alone must be enough to answer them, without opening the code.\nAsk them in one call to the question tool.\nEach question is a concrete scenario with three plausible answers: one correct, and two that a reasonable person could believe.\nShuffle the three answers and mark none as recommended. Add a fourth option last, \"I don't know, explain\", in the user's language.\nThe free text field stays open for another answer.\n\n- Good: \"A client sends the same order again after a timeout. How many orders are in the database?\"\n- Bad: \"Which function handles the retry?\"\n\n## Recap the answers\n\nAfter the user answers, write a recap in chat. For each question, show the question, the user's answer, and \"correct\", \"wrong\", or \"skipped\".\n\"I don't know, explain\" counts as skipped. For a wrong or skipped answer, explain the correct answer with a different example.\nA wrong answer can mean two things: the user lacks a concept, or the user wanted the system to behave that way.\nFor each wrong answer, say which one the answer suggests, and why.\nWhen the user wanted a different behavior, check whether the code or the requirement is wrong before you correct the user.\n\nThen ask with the question tool how to continue, and wait for the answer before the next step:\n\n- All answers correct: continue (recommended), more questions, or more explanation.\n- Some answers wrong: review the work on those points, more questions or explanation, or continue. Recommend the option that matches what the wrong answers suggest.\n\nTo review the work, settle the new requirement with the user, then change the work, repeat its checks and review, and explain the changed part again.\n\n## Visual mode\n\nWith `--visual`, or when the user asks for it, also build a page the user can step through: read [visual mode](references\u002Fvisual-mode.md).\nWhen the flow has states, ordering, or branches that are hard to follow in text, offer the page in one line.\n\n## Pull request description\n\nUse the same parts for a reviewer who knows nothing about the project or the task: read [pull request](references\u002Fpull-request.md).\n",{"name":5,"description":7,"allowed-tools":41,"argument-hint":42,"user-invocable":43},"Glob, Grep, Read, Bash, Write, AskUserQuestion, Artifact, Skill","[--visual] [scope]",true,"main","2a6d24be2ed571c5ff2319c506b60741bbcb1cb0","plugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Fexplain-diff",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":55,"prompt":65,"zipAvailable":43},[56,59,62],{"tool":57,"command":58},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill explain-diff",{"tool":60,"command":61},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill explain-diff",{"tool":63,"command":64},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill explain-diff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Fexplain-diff\u002FSKILL.md",[67,73],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fpull-request.md","REFERENCE","参考文档",2669,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Fexplain-diff\u002Freferences\u002Fpull-request.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fvisual-mode.md",1301,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Fexplain-diff\u002Freferences\u002Fvisual-mode.md",[78,88,96,104,112,120],{"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":82,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":87},"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":87},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":87},"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":87},"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":87},"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":87},"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",[],[]]