[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E88QGQDCDEDASFW5FDASFY":3,"skill-same:01M7E88QGQDCDEDASFW5FDASFY":60},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":14,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":53},"01M7E88QGQDCDEDASFW5FDASFY","refresh",null,"Update the branch's own changelog entries to match its current net change; commits only with --commit","tony\u002Fskills","tony","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F26336?v=4","01M72E5RNJ7SQV8F9KBM5RKRMN","Tony Narlock","01M7E7MBN5C6YZ4JJJ5Y82KBJG",0,"MIT","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fchangelog\u002Fskills\u002Frefresh\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: refresh\ndescription: Update the branch's own changelog entries to match its current net change; commits only with --commit\nallowed-tools: [\"Bash\", \"Read\", \"Grep\", \"Glob\", \"Edit\", \"AskUserQuestion\"]\nargument-hint: \"[--commit] [optional additional context about the changes]\"\ndisable-model-invocation: true\n---\n\n# Refresh Changelog Entries\n\nBring the changelog entries this branch introduced back in sync with what the\nbranch does now. With `--commit`, the correction lands as a new commit on top;\notherwise the edit stays uncommitted for the user to commit. History is never\nrewritten; `\u002Fchangelog:rewrite-aggressively` does that.\n\nScope: edit only changelog content the branch added. Entries from the base\nbranch, whether earlier releases or other work's unreleased entries, are\nread-only. A correction that needs a line the branch did not add: ask, or without a\nquestion tool leave it and note the limitation.\n\nA request for a final's section is the exception in `branch-scope.md`: find\nthe changelog file and check it is clean as Phase 1 does, write the section\nper `..\u002F..\u002Freferences\u002Fgraduation.md` in place of the rest of Phases 1 to 3,\nthen present and apply it under Phase 4's approval gate, without its scope\nguard.\n\nAdditional context from user: $ARGUMENTS\n\nRead these first:\n\n- `..\u002F..\u002Freferences\u002Fbranch-scope.md`: a branch is not a release, base branch,\n  changelog file lookup, whole-branch perspective.\n- `..\u002F..\u002Freferences\u002Fentry-rules.md`: categorizing, format, voice, exclusions.\n- `..\u002F..\u002Freferences\u002Fcommit-message.md`: used in Phase 4.\n\nWrite entries, commit messages, and user-facing replies per\n`..\u002F..\u002Freferences\u002Fprose-rules.md`.\n\n## Phase 1: Establish scope\n\n1. Detect the base and find the changelog file per `branch-scope.md`. No\n   changelog changes on this branch and no changelog file: suggest\n   `\u002Fchangelog:changelog` and stop.\n2. Extract the branch's changelog footprint. The added lines are the\n   branch-owned entries, the only region this skill may edit:\n\n   ```console\n   $ git diff origin\u002F\u003Cbase>...HEAD -- \u003Cchangelog-file>\n   ```\n\n3. List the branch commits that touch the file (with no `origin` remote,\n   substitute the local base name for `origin\u002F\u003Cbase>` in these commands):\n\n   ```console\n   $ git log origin\u002F\u003Cbase>..HEAD --oneline -- \u003Cchangelog-file>\n   ```\n\n   None: say so and offer the `\u002Fchangelog:changelog` procedure instead.\n\n4. Check the changelog is clean per `commit-message.md`; when it is not, edit\n   only and say why.\n\n## Phase 2: Recompute what the entries should say\n\nApply `branch-scope.md` and `entry-rules.md`: read conventions, categorize, and\ngenerate the entries the branch should have from its current net change\n(`git log origin\u002F\u003Cbase>..HEAD` and `git diff origin\u002F\u003Cbase>...HEAD`, three-dot,\nso base commits the fetch pulled in stay out). For the PR number, run\n`gh pr view --json number --jq .number`; on failure write `(#???)`. Never copy\na number from a dropped or stale entry. Check for prerelease sections of a\nfinal not cut yet, per `branch-scope.md`.\n\n## Phase 3: Diff documented vs. actual\n\nCompare the branch-owned entries against the recomputed ones.\n\n- **Accurate**: leave byte-for-byte untouched, including phrasing you would\n  have written differently. Refresh fixes drift, not style.\n- **Stale**: the entry describes something the branch no longer does, or\n  misstates scope. Rewrite it in place, matching the file's style.\n- **Missing**: a user-visible change with no entry. Insert it in the correct\n  section of the unreleased block, following the section-order rules.\n- **Orphaned**: the entry's change left the branch. Remove the entry.\n- **Out of reach**: the fix would touch content the branch did not add (the\n  branch's entry merged into a pre-existing bullet, or a section heading\n  shared with base entries must change). Ask via `AskUserQuestion` first; if\n  declined, or without a question tool, leave it and note the limitation.\n\n## Phase 4: Present, edit, commit\n\nApproval gate. Do not edit or commit without approval. Approval comes from,\nin order:\n\n- `--commit` in `$ARGUMENTS`: approves the edit and the commit.\n- An invoking message that asks to refresh, update, or fix the entries:\n  approves the edit only.\n- `AskUserQuestion`, when the host has it and neither of the above applies.\n- Otherwise, present the proposal and stop; never wait for a reply.\n\n1. Present the summary line\n   (`Branch: \u003Cname> | Base: \u003Cbase> | Changelog commits: \u003Ccount>`), the proposed\n   old to new markdown for each touched entry, the statement that everything\n   else in the file is untouched, the voice check and `Target` line from\n   `entry-rules.md`, and `Notes` per `entry-rules.md`, such as an out-of-reach\n   correction left undone.\n   Refer to commits by subject in prose, never by bare SHA. Close with the\n   question, or when stopping, one line: nothing was edited; re-run with\n   \"refresh the entries\" to edit only, or with `--commit` to apply and commit.\n\n   When every entry is accurate, send the no-change shape instead: the\n   summary line, one result sentence, and `Notes` only for out-of-reach items\n   left undone. No Old\u002FNew, voice check, `Target` line, or re-run line.\n\n   ```text\n   Branch: feat\u002Fcache-evict | Base: main | Changelog commits: 2\n\n   The branch's entries already match; nothing to change.\n\n   Notes:\n   - The \"Cache\" heading is shared with base entries; renaming it is left undone and needs your approval.\n   ```\n\n   Omit `Notes` when nothing was left undone. Each Notes bullet names what\n   was left undone and that it needs the user's approval. The no-change reply\n   ends after `Notes`.\n\n   Reply in this shape, as plain text outside any code fence, with plain bullets, no bold (never `- **Label:** ...`), and no local paths:\n\n   ```text\n   Branch: feat\u002Fcache-evict | Base: main | Changelog commits: 2\n\n   Old:\n   - Add `Cache.evict()` (#212)\n\n   New:\n   - Add `Cache.evict()` to drop a cached key (#212)\n\n   Everything else in CHANGES.md is untouched.\n\n   Voice check:\n   - Add `Cache.evict()` to drop a cached key: can I take a new affordance?\n\n   Target: CHANGES.md, Unreleased, Features, after the \"### Features\" heading. No version assigned, no release cut.\n\n   Notes:\n   - The \"Cache\" heading is shared with base entries; renaming it needs your say-so.\n   ```\n\n2. On approval, apply with Edit, confined to the branch's footprint plus\n   approved insertions in the unreleased block.\n3. Show the modified region. Then check the scope guard: run\n   `git diff origin\u002F\u003Cbase>...HEAD -- \u003Cchangelog-file>` for the committed\n   footprint and `git diff -- \u003Cchangelog-file>` for the edit; the edit must\n   touch no line outside the Phase 1 footprint and the approved insertions.\n4. The reply opens with the summary line. A committed reply adds\n   `Committed as \u003Csubject>.` after the `Target` line. With `--commit` in\n   `$ARGUMENTS`, commit the edit as one new commit on top,\n   per `commit-message.md`: no `Co-Authored-By`, no \"Generated with\" or other\n   tool trailer, no emoji. Otherwise leave it uncommitted and show a\n   ready-to-use commit message.\n\nNever rebase, amend, or force-push.\n","# Refresh Changelog Entries\n\nBring the changelog entries this branch introduced back in sync with what the\nbranch does now. With `--commit`, the correction lands as a new commit on top;\notherwise the edit stays uncommitted for the user to commit. History is never\nrewritten; `\u002Fchangelog:rewrite-aggressively` does that.\n\nScope: edit only changelog content the branch added. Entries from the base\nbranch, whether earlier releases or other work's unreleased entries, are\nread-only. A correction that needs a line the branch did not add: ask, or without a\nquestion tool leave it and note the limitation.\n\nA request for a final's section is the exception in `branch-scope.md`: find\nthe changelog file and check it is clean as Phase 1 does, write the section\nper `..\u002F..\u002Freferences\u002Fgraduation.md` in place of the rest of Phases 1 to 3,\nthen present and apply it under Phase 4's approval gate, without its scope\nguard.\n\nAdditional context from user: $ARGUMENTS\n\nRead these first:\n\n- `..\u002F..\u002Freferences\u002Fbranch-scope.md`: a branch is not a release, base branch,\n  changelog file lookup, whole-branch perspective.\n- `..\u002F..\u002Freferences\u002Fentry-rules.md`: categorizing, format, voice, exclusions.\n- `..\u002F..\u002Freferences\u002Fcommit-message.md`: used in Phase 4.\n\nWrite entries, commit messages, and user-facing replies per\n`..\u002F..\u002Freferences\u002Fprose-rules.md`.\n\n## Phase 1: Establish scope\n\n1. Detect the base and find the changelog file per `branch-scope.md`. No\n   changelog changes on this branch and no changelog file: suggest\n   `\u002Fchangelog:changelog` and stop.\n2. Extract the branch's changelog footprint. The added lines are the\n   branch-owned entries, the only region this skill may edit:\n\n   ```console\n   $ git diff origin\u002F\u003Cbase>...HEAD -- \u003Cchangelog-file>\n   ```\n\n3. List the branch commits that touch the file (with no `origin` remote,\n   substitute the local base name for `origin\u002F\u003Cbase>` in these commands):\n\n   ```console\n   $ git log origin\u002F\u003Cbase>..HEAD --oneline -- \u003Cchangelog-file>\n   ```\n\n   None: say so and offer the `\u002Fchangelog:changelog` procedure instead.\n\n4. Check the changelog is clean per `commit-message.md`; when it is not, edit\n   only and say why.\n\n## Phase 2: Recompute what the entries should say\n\nApply `branch-scope.md` and `entry-rules.md`: read conventions, categorize, and\ngenerate the entries the branch should have from its current net change\n(`git log origin\u002F\u003Cbase>..HEAD` and `git diff origin\u002F\u003Cbase>...HEAD`, three-dot,\nso base commits the fetch pulled in stay out). For the PR number, run\n`gh pr view --json number --jq .number`; on failure write `(#???)`. Never copy\na number from a dropped or stale entry. Check for prerelease sections of a\nfinal not cut yet, per `branch-scope.md`.\n\n## Phase 3: Diff documented vs. actual\n\nCompare the branch-owned entries against the recomputed ones.\n\n- **Accurate**: leave byte-for-byte untouched, including phrasing you would\n  have written differently. Refresh fixes drift, not style.\n- **Stale**: the entry describes something the branch no longer does, or\n  misstates scope. Rewrite it in place, matching the file's style.\n- **Missing**: a user-visible change with no entry. Insert it in the correct\n  section of the unreleased block, following the section-order rules.\n- **Orphaned**: the entry's change left the branch. Remove the entry.\n- **Out of reach**: the fix would touch content the branch did not add (the\n  branch's entry merged into a pre-existing bullet, or a section heading\n  shared with base entries must change). Ask via `AskUserQuestion` first; if\n  declined, or without a question tool, leave it and note the limitation.\n\n## Phase 4: Present, edit, commit\n\nApproval gate. Do not edit or commit without approval. Approval comes from,\nin order:\n\n- `--commit` in `$ARGUMENTS`: approves the edit and the commit.\n- An invoking message that asks to refresh, update, or fix the entries:\n  approves the edit only.\n- `AskUserQuestion`, when the host has it and neither of the above applies.\n- Otherwise, present the proposal and stop; never wait for a reply.\n\n1. Present the summary line\n   (`Branch: \u003Cname> | Base: \u003Cbase> | Changelog commits: \u003Ccount>`), the proposed\n   old to new markdown for each touched entry, the statement that everything\n   else in the file is untouched, the voice check and `Target` line from\n   `entry-rules.md`, and `Notes` per `entry-rules.md`, such as an out-of-reach\n   correction left undone.\n   Refer to commits by subject in prose, never by bare SHA. Close with the\n   question, or when stopping, one line: nothing was edited; re-run with\n   \"refresh the entries\" to edit only, or with `--commit` to apply and commit.\n\n   When every entry is accurate, send the no-change shape instead: the\n   summary line, one result sentence, and `Notes` only for out-of-reach items\n   left undone. No Old\u002FNew, voice check, `Target` line, or re-run line.\n\n   ```text\n   Branch: feat\u002Fcache-evict | Base: main | Changelog commits: 2\n\n   The branch's entries already match; nothing to change.\n\n   Notes:\n   - The \"Cache\" heading is shared with base entries; renaming it is left undone and needs your approval.\n   ```\n\n   Omit `Notes` when nothing was left undone. Each Notes bullet names what\n   was left undone and that it needs the user's approval. The no-change reply\n   ends after `Notes`.\n\n   Reply in this shape, as plain text outside any code fence, with plain bullets, no bold (never `- **Label:** ...`), and no local paths:\n\n   ```text\n   Branch: feat\u002Fcache-evict | Base: main | Changelog commits: 2\n\n   Old:\n   - Add `Cache.evict()` (#212)\n\n   New:\n   - Add `Cache.evict()` to drop a cached key (#212)\n\n   Everything else in CHANGES.md is untouched.\n\n   Voice check:\n   - Add `Cache.evict()` to drop a cached key: can I take a new affordance?\n\n   Target: CHANGES.md, Unreleased, Features, after the \"### Features\" heading. No version assigned, no release cut.\n\n   Notes:\n   - The \"Cache\" heading is shared with base entries; renaming it needs your say-so.\n   ```\n\n2. On approval, apply with Edit, confined to the branch's footprint plus\n   approved insertions in the unreleased block.\n3. Show the modified region. Then check the scope guard: run\n   `git diff origin\u002F\u003Cbase>...HEAD -- \u003Cchangelog-file>` for the committed\n   footprint and `git diff -- \u003Cchangelog-file>` for the edit; the edit must\n   touch no line outside the Phase 1 footprint and the approved insertions.\n4. The reply opens with the summary line. A committed reply adds\n   `Committed as \u003Csubject>.` after the `Target` line. With `--commit` in\n   `$ARGUMENTS`, commit the edit as one new commit on top,\n   per `commit-message.md`: no `Co-Authored-By`, no \"Generated with\" or other\n   tool trailer, no emoji. Otherwise leave it uncommitted and show a\n   ready-to-use commit message.\n\nNever rebase, amend, or force-push.\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":31,"disable-model-invocation":32},[25,26,27,28,29,30],"Bash","Read","Grep","Glob","Edit","AskUserQuestion","[--commit] [optional additional context about the changes]",true,"main","5fbeb3b47beedea13813be7b7023f736a8d97a65","plugins\u002Fchangelog\u002Fskills\u002Frefresh","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills","https:\u002F\u002Fgithub.com\u002Ftony","https:\u002F\u002Ftony.sh","lighthouse keeper","2026-11-08 17:57:34",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":32},[43,46,49],{"tool":44,"command":45},"npx","npx skills add tony\u002Fskills --skill refresh",{"tool":47,"command":48},"bunx","bunx skills add tony\u002Fskills --skill refresh",{"tool":50,"command":51},"pnpm","pnpm dlx skills add tony\u002Fskills --skill refresh","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fchangelog\u002Fskills\u002Frefresh\u002FSKILL.md",[54],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"agents\u002Fopenai.yaml","REFERENCE","参考文档",299,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fchangelog\u002Fskills\u002Frefresh\u002Fagents\u002Fopenai.yaml",[61,68,75,82,89,96],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7E8NCSHXV2JPW4J61R0TQS7","serene-bliss","Use when asked to make a CLI --help, docs page, error message, or tooling UX more serene or calmer for developer experience; returns text, no edits.","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Fserene-bliss\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7E8N87MAVJD8RRQKQB1ZPS6","review","Weave code review: run independent adversarial reviews in parallel, then synthesize findings","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7E8N402XG4ZBFNACQ413163","refine","Use when asked to refine a draft, iterate on code until cleaner, or polish a README through repeated critique and improvement.","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Frefine\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7E8N01KB86A7136P00GVKJW","prompt","Weave prompt: compare independent adversarial implementations, then adopt the single best one","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Fprompt\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7E8MW7YJW2PCMDW3G9RTGNK","plan","Weave planning: compare independent adversarial plans, then synthesize the best one","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Fplan\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":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7E8MSBYXNCV4ZYWDS4PFJXK","fix-review","Fix weave review findings: validate, add test coverage, fix, and commit each as atomic changes","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Ffix-review\u002FSKILL.md",[],[]]