[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MCYHXYFTGDMFEN5TBBZ581":3,"skill-same:01M6MCYHXYFTGDMFEN5TBBZ581":59},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M6MCYHXYFTGDMFEN5TBBZ581","changelog",null,"Record shipped work in the monthly changelog (append-only). Use when something ships or when asked \"what changed\", \"add to changelog\", \"release notes\", or \"what shipped this month\".","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\u002FMedAdemBHA\u002Fdocflow\u002Fskills\u002Fchangelog\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29],"notes","release notes","release","work","append","use","only","record","monthly","add","when","2026-11-10 10:12:30",false,"---\nname: changelog\ndescription: 'Record shipped work in the monthly changelog (append-only). Use when something ships or when asked \"what changed\", \"add to changelog\", \"release notes\", or \"what shipped this month\".'\n---\n\n# changelog\n\nThe memory of the knowledge base. Every month gets one file; history is **append-only**. This is what the SessionStart hook surfaces so the agent starts each session knowing recent work. Pairs with [`author`](..\u002Fauthor\u002FSKILL.md) and [`router`](..\u002Frouter\u002FSKILL.md).\n\n> Golden rule: **never delete or rewrite shipped history.** Reversals get a *new* entry, not an edit.\n\n## Writing style (enforce)\nDirect, tech + business. No filler. Outcome first.\n- Each entry = a small table (Outcome \u002F Delivered \u002F Business impact \u002F Commits). No narrative paragraphs.\n- Summary = 4 bullets max: release type, biggest business change, biggest technical change, prod risk\u002Faction.\n- Concrete only: feature names, paths, hashes, numbers. Cut adjectives.\n\n---\n\n## 1 — One file per month\n\n`changelog\u002F(mmm-yy).md` — lowercase 3-letter month + 2-digit year: `(apr-26).md`, `(may-26).md`.\n`changelog\u002FREADME.md` is the index: a table of `| Month | Highlights |`, newest first.\n\nLink to a month file (parens need angle brackets): `[may-26](\u003C(may-26).md>)`.\n\n---\n\n## 2 — Anatomy of a month file\n\n```markdown\n# Month YEAR — \u003Crelease \u002F period title>\n\n> Window: `\u003Cbase>` (`hash`, date) → `\u003Chead>` (`hash`, date). Scope: `N` commits.\n\n## Summary\n- Release type: patch | feature | architectural\n- Biggest business change: \u003Cone line>\n- Biggest technical change: \u003Cone line>\n- Risk \u002F action for prod: \u003Cone line>\n\n## What Changed\n\n### 1. \u003CFeature \u002F theme>\n| | |\n|---|---|\n| Outcome | \u003Cone line> |\n| Delivered | \u003Cbullet; bullet> |\n| Business impact | \u003Cone line> |\n| Commits | `\u003Chash>` \u003Cdesc>; `\u003Chash>` \u003Cdesc> |\n\n### 2. \u003Cnext theme>\n```\n\nA reader skimming the `Outcome` rows alone should understand the release.\n\n---\n\n## 3 — The shipping flow (where changelog fits)\n\nThe roadmap (`plans\u002Fupcoming\u002F`) and the changelog are two ends of one pipe:\n\n```\nplans\u002Fupcoming\u002F{critical,now,next,later}.md   ── ships ──►   changelog\u002F(mmm-yy).md\n        (what's coming)                                        (what landed)\n```\n\nWhen something ships:\n1. **Move** the line out of the `plans\u002Fupcoming\u002F*` horizon — don't let shipped work linger there (it kills the roadmap's signal).\n2. **Add \u002F update** the entry in the current `changelog\u002F(mmm-yy).md`.\n3. **Cross-link**: the feature plan's `## What shipped` table references the changelog month; the ADR\u002Fspec stay linked from the plan.\n4. If a known bug got fixed, move it from `reviews\u002Fbugs\u002Fopen.md` to `reviews\u002Fbugs\u002Ffixed.md` with the commit ref.\n\n`plans\u002Fupcoming\u002FREADME.md` keeps a short \"Recently shipped\" pointer list to the last few months — **pointers only, no restating**.\n\n---\n\n## 4 — Generating an entry from git\n\nTo build a month\u002Frelease entry, diff the two refs and group commits by theme:\n\n```bash\n# commits in head not yet in base, newest first\ngit log --no-merges --pretty='%h %ad %s' --date=short BASE..HEAD\n# count for the scope line\ngit rev-list --count --no-merges BASE..HEAD\n```\n\nThen: cluster commits into 3–8 themes → write a `### N. Theme` block each → fill outcome \u002F delivered \u002F why \u002F commits → write the Executive Summary last (it summarizes the blocks).\n\n---\n\n## 5 — Why append-only matters\n\nThe changelog is the project's long-term memory. An agent (or a new teammate) that reads the newest one or two month files gets the recent trajectory: what was built, why it mattered, which commits. Editing or pruning old months erases that trail. Superseded decisions are recorded as *new* lines that reference the old — the history of the change is itself information.\n","# changelog\n\nThe memory of the knowledge base. Every month gets one file; history is **append-only**. This is what the SessionStart hook surfaces so the agent starts each session knowing recent work. Pairs with [`author`](..\u002Fauthor\u002FSKILL.md) and [`router`](..\u002Frouter\u002FSKILL.md).\n\n> Golden rule: **never delete or rewrite shipped history.** Reversals get a *new* entry, not an edit.\n\n## Writing style (enforce)\nDirect, tech + business. No filler. Outcome first.\n- Each entry = a small table (Outcome \u002F Delivered \u002F Business impact \u002F Commits). No narrative paragraphs.\n- Summary = 4 bullets max: release type, biggest business change, biggest technical change, prod risk\u002Faction.\n- Concrete only: feature names, paths, hashes, numbers. Cut adjectives.\n\n---\n\n## 1 — One file per month\n\n`changelog\u002F(mmm-yy).md` — lowercase 3-letter month + 2-digit year: `(apr-26).md`, `(may-26).md`.\n`changelog\u002FREADME.md` is the index: a table of `| Month | Highlights |`, newest first.\n\nLink to a month file (parens need angle brackets): `[may-26](\u003C(may-26).md>)`.\n\n---\n\n## 2 — Anatomy of a month file\n\n```markdown\n# Month YEAR — \u003Crelease \u002F period title>\n\n> Window: `\u003Cbase>` (`hash`, date) → `\u003Chead>` (`hash`, date). Scope: `N` commits.\n\n## Summary\n- Release type: patch | feature | architectural\n- Biggest business change: \u003Cone line>\n- Biggest technical change: \u003Cone line>\n- Risk \u002F action for prod: \u003Cone line>\n\n## What Changed\n\n### 1. \u003CFeature \u002F theme>\n| | |\n|---|---|\n| Outcome | \u003Cone line> |\n| Delivered | \u003Cbullet; bullet> |\n| Business impact | \u003Cone line> |\n| Commits | `\u003Chash>` \u003Cdesc>; `\u003Chash>` \u003Cdesc> |\n\n### 2. \u003Cnext theme>\n```\n\nA reader skimming the `Outcome` rows alone should understand the release.\n\n---\n\n## 3 — The shipping flow (where changelog fits)\n\nThe roadmap (`plans\u002Fupcoming\u002F`) and the changelog are two ends of one pipe:\n\n```\nplans\u002Fupcoming\u002F{critical,now,next,later}.md   ── ships ──►   changelog\u002F(mmm-yy).md\n        (what's coming)                                        (what landed)\n```\n\nWhen something ships:\n1. **Move** the line out of the `plans\u002Fupcoming\u002F*` horizon — don't let shipped work linger there (it kills the roadmap's signal).\n2. **Add \u002F update** the entry in the current `changelog\u002F(mmm-yy).md`.\n3. **Cross-link**: the feature plan's `## What shipped` table references the changelog month; the ADR\u002Fspec stay linked from the plan.\n4. If a known bug got fixed, move it from `reviews\u002Fbugs\u002Fopen.md` to `reviews\u002Fbugs\u002Ffixed.md` with the commit ref.\n\n`plans\u002Fupcoming\u002FREADME.md` keeps a short \"Recently shipped\" pointer list to the last few months — **pointers only, no restating**.\n\n---\n\n## 4 — Generating an entry from git\n\nTo build a month\u002Frelease entry, diff the two refs and group commits by theme:\n\n```bash\n# commits in head not yet in base, newest first\ngit log --no-merges --pretty='%h %ad %s' --date=short BASE..HEAD\n# count for the scope line\ngit rev-list --count --no-merges BASE..HEAD\n```\n\nThen: cluster commits into 3–8 themes → write a `### N. Theme` block each → fill outcome \u002F delivered \u002F why \u002F commits → write the Executive Summary last (it summarizes the blocks).\n\n---\n\n## 5 — Why append-only matters\n\nThe changelog is the project's long-term memory. An agent (or a new teammate) that reads the newest one or two month files gets the recent trajectory: what was built, why it mattered, which commits. Editing or pruning old months erases that trail. Superseded decisions are recorded as *new* lines that reference the old — the history of the change is itself information.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FMedAdemBHA\u002Fdocflow\u002Fskills\u002Fchangelog",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":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill changelog",{"tool":51,"command":52},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill changelog",{"tool":54,"command":55},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill changelog","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FMedAdemBHA\u002Fdocflow\u002Fskills\u002Fchangelog\u002FSKILL.md",true,[],[60,70,78,86,94,102],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":65,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":69},"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":74,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":69},"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":69},"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":69},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":69},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":69},"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",[],[]]