[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMGG61XDJE021SH3DMTRCC":3,"skill-same:01M7EMGG61XDJE021SH3DMTRCC":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EMGG61XDJE021SH3DMTRCC","ams-changelog-pro",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-changelog-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: changelog-pro\ndescription: Maintain changelogs users actually read: Keep-a-Changelog format, automation, and release-note craft. Use when writing changelogs or automating release notes.\ncategory: development\n---\n\n# Changelog Pro\n\n## Overview\n\nA changelog is **the human-readable story of what changed and why it matters** — distinct from git\nhistory (for developers) and marketing (for prospects). Done well, it builds trust: users can see\nwhat's new, what's fixed, and what might break them. This skill covers the Keep-a-Changelog\ndiscipline, writing entries users care about, and automating generation without producing robotic\nnoise.\n\nThe through-line: changelogs are for humans — write what changed from the *user's* perspective, in\nlanguage they'll understand.\n\n## When to use\n\n- Writing changelog entries for a release.\n- Setting up changelog conventions (Keep-a-Changelog, changesets).\n- Automating release notes from commits or PRs.\n- Reviewing changelogs for clarity and completeness.\n- Deciding what belongs in a changelog vs git history.\n\n## Core concepts\n\n- **Keep-a-Changelog format.** `CHANGELOG.md` with `## [Unreleased]` at top, version sections with\n  dates, and categorized entries: Added \u002F Changed \u002F Deprecated \u002F Removed \u002F Fixed \u002F Security.\n  Reverse-chronological, one file, human-written summaries — the de facto standard for a reason.\n- **User perspective, always.** \"Fixed: checkout no longer double-charges on retry\" — not\n  \"refactored payment idempotency layer.\" Users care about behavior change, not implementation.\n  Write the *impact*, link the detail (PR\u002Fissue) for the curious.\n- **Breaking changes, loudly.** A dedicated, unmissable section at the top of the release:\n  what breaks, who it affects, and exactly how to migrate (before\u002Fafter code). Breaking changes\n  buried in \"Changed\" erode trust permanently.\n- **The Unreleased section.** Every PR that changes behavior adds an entry under `## [Unreleased]`\n  *in the same PR*. Release time = rename the section + date. No archaeology, no forgotten entries.\n- **Automation with judgment.** Generate drafts from conventional commits or PR titles, but\n  *curate* before publishing — raw commit logs are noise (\"fix typo\", \"wip\"). Changesets\n  (per-PR change descriptions) produce the best automated changelogs because humans write the\n  entries at change time.\n- **Version links and dates.** `[1.2.0] - 2026-09-26` with link definitions to diffs\u002Ftags at the\n  bottom. Dates matter (users correlate with their issues); diff links serve the deeply curious.\n\n## Practical workflow\n\n1. **Adopt the format.** `CHANGELOG.md` at repo root, Keep-a-Changelog structure, `## [Unreleased]`\n   section live from day one. Add \"changelog entry\" to the PR template checklist.\n2. **Write entries per PR.** In the same PR as the change: one bullet under Unreleased, categorized,\n   user-perspective language, PR\u002Fissue link. Small habit, huge payoff.\n3. **Curate at release.** Read the Unreleased section as a user: reorder by importance, merge\n   related bullets, elevate breaking changes to the top with migration guides, cut internal noise.\n4. **Publish consistently.** Changelog updated in the release commit; release notes (GitHub\n   releases) mirror or link it; announce breaking changes through every channel users watch.\n5. **Automate the draft.** Conventional commits → generated draft, or changesets → compiled notes;\n   human curates. Never ship raw generated logs as the changelog.\n6. **Maintain the discipline.** Review changelog entries in PR review like code; reject \"various\n   fixes\" entries; keep the format consistent across releases.\n\nExample entries:\n\n```markdown\n## [Unreleased]\n\n## [2.4.0] - 2026-09-26\n\n### ⚠️ Breaking changes\n- **API:** `POST \u002Forders` now requires `idempotency_key` (was optional).\n  Migration: generate a UUID per order attempt client-side; see #1234.\n  Affects: all API consumers creating orders.\n\n### Added\n- Checkout now supports saved payment methods (#1230)\n- Webhook event `refund.processed` for refund status tracking (#1228)\n\n### Fixed\n- Double charges when \"Place order\" was tapped twice quickly (#1224)\n- Order list pagination skipping items when new orders arrived (#1219)\n\n### Security\n- Rate limiting added to password-reset endpoint (abuse prevention) (#1221)\n```\n\n## Common pitfalls\n\n- **Git log as changelog.** Dumping commit messages (\"fix stuff\", \"wip\", \"address review\n  feedback\") — noise that teaches users to never read it. Curate for humans.\n- **Developer perspective.** \"Refactored auth middleware\" means nothing to users. Translate to\n  impact: \"Sign-in is now 40% faster\" or omit if truly internal.\n- **Missing breaking changes.** Or burying them. Breaking changes are the highest-value changelog\n  content — prominent, with migration paths. Users plan upgrades around them.\n- **Stale or missing Unreleased.** Entries written at release time from memory — incomplete and\n  wrong. Per-PR entries under Unreleased, enforced by checklist\u002Freview.\n- **\"Various bug fixes.\"** The entry that says nothing. Each fix gets its specific bullet, or the\n  changelog isn't doing its job.\n- **No dates or versions.** Undated sections, missing version links — users can't correlate\n  releases with their experience. Date every release; link every version.\n- **Changelog vs release notes confusion.** The changelog is the durable record (in the repo);\n  release notes are the announcement (can link it). Keep the changelog canonical; don't maintain\n  two divergent sources.\n","# Changelog Pro\n\n## Overview\n\nA changelog is **the human-readable story of what changed and why it matters** — distinct from git\nhistory (for developers) and marketing (for prospects). Done well, it builds trust: users can see\nwhat's new, what's fixed, and what might break them. This skill covers the Keep-a-Changelog\ndiscipline, writing entries users care about, and automating generation without producing robotic\nnoise.\n\nThe through-line: changelogs are for humans — write what changed from the *user's* perspective, in\nlanguage they'll understand.\n\n## When to use\n\n- Writing changelog entries for a release.\n- Setting up changelog conventions (Keep-a-Changelog, changesets).\n- Automating release notes from commits or PRs.\n- Reviewing changelogs for clarity and completeness.\n- Deciding what belongs in a changelog vs git history.\n\n## Core concepts\n\n- **Keep-a-Changelog format.** `CHANGELOG.md` with `## [Unreleased]` at top, version sections with\n  dates, and categorized entries: Added \u002F Changed \u002F Deprecated \u002F Removed \u002F Fixed \u002F Security.\n  Reverse-chronological, one file, human-written summaries — the de facto standard for a reason.\n- **User perspective, always.** \"Fixed: checkout no longer double-charges on retry\" — not\n  \"refactored payment idempotency layer.\" Users care about behavior change, not implementation.\n  Write the *impact*, link the detail (PR\u002Fissue) for the curious.\n- **Breaking changes, loudly.** A dedicated, unmissable section at the top of the release:\n  what breaks, who it affects, and exactly how to migrate (before\u002Fafter code). Breaking changes\n  buried in \"Changed\" erode trust permanently.\n- **The Unreleased section.** Every PR that changes behavior adds an entry under `## [Unreleased]`\n  *in the same PR*. Release time = rename the section + date. No archaeology, no forgotten entries.\n- **Automation with judgment.** Generate drafts from conventional commits or PR titles, but\n  *curate* before publishing — raw commit logs are noise (\"fix typo\", \"wip\"). Changesets\n  (per-PR change descriptions) produce the best automated changelogs because humans write the\n  entries at change time.\n- **Version links and dates.** `[1.2.0] - 2026-09-26` with link definitions to diffs\u002Ftags at the\n  bottom. Dates matter (users correlate with their issues); diff links serve the deeply curious.\n\n## Practical workflow\n\n1. **Adopt the format.** `CHANGELOG.md` at repo root, Keep-a-Changelog structure, `## [Unreleased]`\n   section live from day one. Add \"changelog entry\" to the PR template checklist.\n2. **Write entries per PR.** In the same PR as the change: one bullet under Unreleased, categorized,\n   user-perspective language, PR\u002Fissue link. Small habit, huge payoff.\n3. **Curate at release.** Read the Unreleased section as a user: reorder by importance, merge\n   related bullets, elevate breaking changes to the top with migration guides, cut internal noise.\n4. **Publish consistently.** Changelog updated in the release commit; release notes (GitHub\n   releases) mirror or link it; announce breaking changes through every channel users watch.\n5. **Automate the draft.** Conventional commits → generated draft, or changesets → compiled notes;\n   human curates. Never ship raw generated logs as the changelog.\n6. **Maintain the discipline.** Review changelog entries in PR review like code; reject \"various\n   fixes\" entries; keep the format consistent across releases.\n\nExample entries:\n\n```markdown\n## [Unreleased]\n\n## [2.4.0] - 2026-09-26\n\n### ⚠️ Breaking changes\n- **API:** `POST \u002Forders` now requires `idempotency_key` (was optional).\n  Migration: generate a UUID per order attempt client-side; see #1234.\n  Affects: all API consumers creating orders.\n\n### Added\n- Checkout now supports saved payment methods (#1230)\n- Webhook event `refund.processed` for refund status tracking (#1228)\n\n### Fixed\n- Double charges when \"Place order\" was tapped twice quickly (#1224)\n- Order list pagination skipping items when new orders arrived (#1219)\n\n### Security\n- Rate limiting added to password-reset endpoint (abuse prevention) (#1221)\n```\n\n## Common pitfalls\n\n- **Git log as changelog.** Dumping commit messages (\"fix stuff\", \"wip\", \"address review\n  feedback\") — noise that teaches users to never read it. Curate for humans.\n- **Developer perspective.** \"Refactored auth middleware\" means nothing to users. Translate to\n  impact: \"Sign-in is now 40% faster\" or omit if truly internal.\n- **Missing breaking changes.** Or burying them. Breaking changes are the highest-value changelog\n  content — prominent, with migration paths. Users plan upgrades around them.\n- **Stale or missing Unreleased.** Entries written at release time from memory — incomplete and\n  wrong. Per-PR entries under Unreleased, enforced by checklist\u002Freview.\n- **\"Various bug fixes.\"** The entry that says nothing. Each fix gets its specific bullet, or the\n  changelog isn't doing its job.\n- **No dates or versions.** Undated sections, missing version links — users can't correlate\n  releases with their experience. Date every release; link every version.\n- **Changelog vs release notes confusion.** The changelog is the durable record (in the repo);\n  release notes are the announcement (can link it). Keep the changelog canonical; don't maintain\n  two divergent sources.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-changelog-pro",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-changelog-pro",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-changelog-pro",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-changelog-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-changelog-pro\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]