[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75JQ6FT16K6XWBZHTDY2EZW":3,"skill-same:01M75JQ6FT16K6XWBZHTDY2EZW":48},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M75JQ6FT16K6XWBZHTDY2EZW","changelog",null,"How to write CHANGELOG.md entries for The Warden's Oak — scannable one-liners, grouped by kind. Use whenever you add to or edit CHANGELOG.md (every merge into dev should touch it).","WernerVdM97\u002Fdaily-pixel","WernerVdM97","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F51920192?v=4","01M75JPTS7EV5F4QH79JWF8YCE","Werner V\u002Fd Merwe","01M75JPTTSMZ29EMDP2KRMHVHC",0,"MIT","https:\u002F\u002Fgithub.com\u002FWernerVdM97\u002Fdaily-pixel\u002Fblob\u002Fdev\u002F.pi\u002Fskills\u002Fchangelog\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: changelog\ndescription: How to write CHANGELOG.md entries for The Warden's Oak — scannable one-liners, grouped by kind. Use whenever you add to or edit CHANGELOG.md (every merge into dev should touch it).\nallowed-tools: Read, Edit, Glob, Grep\npaths:\n  - CHANGELOG.md\n---\n\n# Changelog\n\n`CHANGELOG.md` entries earn their keep by being **scannable**, not exhaustive — one tight line per change, like a good commit subject. The PR, commit, and any `docs\u002Fdecisions\u002F` record hold the full story; the changelog is the index.\n\n**CHANGELOGS SHOULD BE BRIEF AND TO THE POINT.** Prefer a one- or two-sentence summary that refers to a commit for further reading, instead of whole paragraphs.\n\n1. **One bullet, one line.** Lead with a **bold subject** naming the change, then an em-dash and the gist in a sentence or two. If you need a paragraph, the detail belongs in the PR\u002Fdecision doc — link it, don't inline it.\n2. **Say what changed and why it matters, not how it's wired.** Skip the play-by-play of helpers, call sites, and internal flow. Name the new column\u002Fenv var\u002Fmethod when a reader needs it to act, not to narrate the diff.\n3. **Cut hedging and restatement.** No \"previously…\u002Finstead of…\" retelling of the old behaviour unless the contrast is the point. One clause of rationale beats six.\n4. **Group by Keep-a-Changelog kind** (`Added`\u002F`Changed`\u002F`Fixed`\u002F`Chore`\u002F`Internal`) and keep each bullet in its right group — don't bury a fix inside an Added blurb.\n5. **Anchor an edit on the release, never on the kind.** `### Fixed`, `### Added` and friends repeat once per release (24 `### Fixed` headings today), so an anchor on the kind alone is not unique and one widened onto the bullets around it goes stale the moment the release moves. Anchor on `## [Unreleased]` or the dated release heading instead.\n\n**Verbose is justified only when the reader must *act* on the detail**, not as default narration. Keep the specifics for: required Discord permissions or env vars to set; migrations and schema changes (column names, idempotency, no-op-on-existing-DB caveats); breaking changes and contract shifts; security fixes; anything with an ordering\u002Fidempotency gotcha that bites if missed. When in doubt, ask \"would a reader skimming the release have to do something because of this line?\" — if yes, spell it out; if no, one line.\n","# Changelog\n\n`CHANGELOG.md` entries earn their keep by being **scannable**, not exhaustive — one tight line per change, like a good commit subject. The PR, commit, and any `docs\u002Fdecisions\u002F` record hold the full story; the changelog is the index.\n\n**CHANGELOGS SHOULD BE BRIEF AND TO THE POINT.** Prefer a one- or two-sentence summary that refers to a commit for further reading, instead of whole paragraphs.\n\n1. **One bullet, one line.** Lead with a **bold subject** naming the change, then an em-dash and the gist in a sentence or two. If you need a paragraph, the detail belongs in the PR\u002Fdecision doc — link it, don't inline it.\n2. **Say what changed and why it matters, not how it's wired.** Skip the play-by-play of helpers, call sites, and internal flow. Name the new column\u002Fenv var\u002Fmethod when a reader needs it to act, not to narrate the diff.\n3. **Cut hedging and restatement.** No \"previously…\u002Finstead of…\" retelling of the old behaviour unless the contrast is the point. One clause of rationale beats six.\n4. **Group by Keep-a-Changelog kind** (`Added`\u002F`Changed`\u002F`Fixed`\u002F`Chore`\u002F`Internal`) and keep each bullet in its right group — don't bury a fix inside an Added blurb.\n5. **Anchor an edit on the release, never on the kind.** `### Fixed`, `### Added` and friends repeat once per release (24 `### Fixed` headings today), so an anchor on the kind alone is not unique and one widened onto the bullets around it goes stale the moment the release moves. Anchor on `## [Unreleased]` or the dated release heading instead.\n\n**Verbose is justified only when the reader must *act* on the detail**, not as default narration. Keep the specifics for: required Discord permissions or env vars to set; migrations and schema changes (column names, idempotency, no-op-on-existing-DB caveats); breaking changes and contract shifts; security fixes; anything with an ordering\u002Fidempotency gotcha that bites if missed. When in doubt, ask \"would a reader skimming the release have to do something because of this line?\" — if yes, spell it out; if no, one line.\n",{"name":5,"paths":24,"description":7,"allowed-tools":26},[25],"CHANGELOG.md","Read, Edit, Glob, Grep","dev","96f5ffb582420679625efdf337d44e9ddfcd7c97",".pi\u002Fskills\u002Fchangelog","https:\u002F\u002Fgithub.com\u002FWernerVdM97\u002Fdaily-pixel","https:\u002F\u002Fgithub.com\u002FWernerVdM97","informationalism enthusiast","2026-11-14 17:25:05",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add WernerVdM97\u002Fdaily-pixel --skill changelog",{"tool":40,"command":41},"bunx","bunx skills add WernerVdM97\u002Fdaily-pixel --skill changelog",{"tool":43,"command":44},"pnpm","pnpm dlx skills add WernerVdM97\u002Fdaily-pixel --skill changelog","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FWernerVdM97\u002Fdaily-pixel\u002Fblob\u002Fdev\u002F.pi\u002Fskills\u002Fchangelog\u002FSKILL.md",true,[],[49,55,60,65,70,75],{"skillNo":50,"name":51,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M75JS5K1AHJ25E4XCKRGG38P","decide","https:\u002F\u002Fgithub.com\u002FWernerVdM97\u002Fdaily-pixel\u002Fblob\u002Fdev\u002Fassets\u002Fprompts\u002Fdecision-prompts\u002Fv14\u002Fdecide\u002Fskill.md",[],[],{"skillNo":56,"name":51,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M75JS47KQ0Y0J7GKJGP05CJW","https:\u002F\u002Fgithub.com\u002FWernerVdM97\u002Fdaily-pixel\u002Fblob\u002Fdev\u002Fassets\u002Fprompts\u002Fdecision-prompts\u002Fv13\u002Fdecide\u002Fskill.md",[],[],{"skillNo":61,"name":51,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M75JS2SGKV3FX5F2GY769FY0","https:\u002F\u002Fgithub.com\u002FWernerVdM97\u002Fdaily-pixel\u002Fblob\u002Fdev\u002Fassets\u002Fprompts\u002Fdecision-prompts\u002Fv12\u002Fdecide\u002Fskill.md",[],[],{"skillNo":66,"name":51,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M75JS08B4RD30N35BYPP2BF8","https:\u002F\u002Fgithub.com\u002FWernerVdM97\u002Fdaily-pixel\u002Fblob\u002Fdev\u002Fassets\u002Fprompts\u002Fdecision-prompts\u002Fcurrent_source\u002Fdecide\u002Fskill.md",[],[],{"skillNo":71,"name":51,"nameZh":6,"description":6,"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},"01M75JRYYS3CASN8Q84SZEKCHE","https:\u002F\u002Fgithub.com\u002FWernerVdM97\u002Fdaily-pixel\u002Fblob\u002Fdev\u002Fassets\u002Fprompts\u002Fdecision-prompts\u002F__test-partial__\u002Fdecide\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},"01M75JRW7DRDGXRK7CDQ9HKP3D","releasing","Branch model, POC-beta versioning, and the full cut-a-release procedure for The Warden's Oak. Use when committing\u002Fbranching, merging dev→main, bumping VERSION, writing release notes, or tagging a release.","https:\u002F\u002Fgithub.com\u002FWernerVdM97\u002Fdaily-pixel\u002Fblob\u002Fdev\u002F.pi\u002Fskills\u002Freleasing\u002FSKILL.md",[],[]]