[{"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",1571,"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",490,"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 02:12:02",{"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,86,93,100,126,151],{"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":85},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":85},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":85},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":36},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,27,123,124,125],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","when","you","done","reviewer","io","cli","merge","past",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":36},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[133,134,135,122,136,137,138,139,140,141,142,143,144,145,112,146,147,148,149,150],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":168,"publishedAt":36},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[157,162,165],{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":163,"categoryName":164,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":166,"categoryName":167,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000010","后端与接口",[153,169,170,171,172,173,174,147,175,113,176,177,178,179,118,180,181,182,183,184],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]