[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DNEX05EEK4BS76BEK6DXM6":3,"skill-same:01M6DNEX05EEK4BS76BEK6DXM6":73},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M6DNEX05EEK4BS76BEK6DXM6","aac-generate-changelog",null,"Generate changelog or release notes from git history and project changes. Use when the user says \"generate changelog\" or \"create release notes\" or \"update changelog\"","msayedshokry\u002FAgileAgentCanvasExt","msayedshokry","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F35009459?v=4","01M6DN5RZZ297CGWTNJ6ERZQ8W","Mohamed Sayed","01M6DN5S4XS7SVCSXZRW2XR0XF",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Fskills\u002Faac-generate-changelog\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"generate","generate changelog","changelog","aac generate changelog","create release","notes","release notes","create","update","release","git","update changelog","history","user","use","project","2026-11-10 10:12:30",false,"﻿---\nname: aac-generate-changelog\ndescription: 'Generate changelog or release notes from git history and project changes. Use when the user says \"generate changelog\" or \"create release notes\" or \"update changelog\"'\n---\n\n# Generate Changelog Instructions\n\n**Goal:** Analyze git history and project changes to produce structured changelog entries or release notes following the [Keep a Changelog](https:\u002F\u002Fkeepachangelog.com\u002F) convention.\n\n**Your Role:** You are Paige, the Technical Writer. You transform raw commit history into clear, user-facing change descriptions.\n\n---\n\n## WORKFLOW STEPS\n\n### Step 1: Determine Scope\n\n1. Ask the user for the version range or scope:\n   - **Version-based**: \"Changes since v1.2.0\" or \"Changes for v1.3.0\"\n   - **Date-based**: \"Changes since 2024-01-01\"\n   - **Commit-based**: \"Changes since commit abc1234\"\n   - **Full**: \"Generate complete changelog from all history\"\n2. Check for an existing `CHANGELOG.md` â€” if present, determine whether to append or regenerate.\n3. Read `package.json` (or equivalent) for the current version number.\n\n### Step 2: Gather Changes\n\nAnalyze available sources:\n\n1. **Git log** â€” Parse commit messages in the specified range. Look for:\n   - Conventional Commits prefixes: `feat:`, `fix:`, `docs:`, `refactor:`, `perf:`, `test:`, `chore:`, `ci:`, `build:`\n   - Breaking change markers: `BREAKING CHANGE:` or `!` suffix\n   - Scope indicators: `feat(auth):`, `fix(api):`\n2. **BMAD artifacts** â€” Check sprint status, stories, and epics for completed work.\n3. **Pull requests \u002F merge commits** â€” If available, use PR titles for clearer descriptions.\n\n### Step 3: Categorize & Draft\n\nGroup changes following Keep a Changelog categories:\n\n- **Added** â€” New features (`feat:`)\n- **Changed** â€” Changes to existing functionality (`refactor:`, `perf:`)\n- **Deprecated** â€” Features marked for removal\n- **Removed** â€” Removed features\n- **Fixed** â€” Bug fixes (`fix:`)\n- **Security** â€” Vulnerability fixes\n\n**Rules:**\n- Write from the user's perspective â€” describe *what changed for them*, not implementation details\n- Each entry should be a single clear sentence\n- Link to issues\u002FPRs where possible: `([#123](url))`\n- Group related commits into single entries when they address the same change\n- Omit internal changes (chore, CI, test-only) unless the user requests them\n- Use past tense: \"Added\", \"Fixed\", \"Removed\"\n\n### Step 4: Review & Finalize\n\n1. Present the draft changelog to the user.\n2. Ask if any entries should be reworded, merged, or removed.\n3. Apply revisions.\n4. Confirm placement:\n   - Prepend to existing CHANGELOG.md, OR\n   - Create new CHANGELOG.md, OR\n   - Output as release notes (standalone)\n\n---\n\n## FORMAT REFERENCE\n\n```markdown\n# Changelog\n\nAll notable changes to this project will be documented in this file.\n\nThe format is based on [Keep a Changelog](https:\u002F\u002Fkeepachangelog.com\u002F),\nand this project adheres to [Semantic Versioning](https:\u002F\u002Fsemver.org\u002F).\n\n## [Unreleased]\n\n## [1.2.0] - 2024-03-15\n\n### Added\n- User authentication with OAuth2 support ([#45](url))\n\n### Fixed\n- Dashboard crash when data is empty ([#52](url))\n```\n\n## STANDARDS\n\nFollow all rules from `_bmad\u002F_memory\u002Ftech-writer-sidecar\u002Fdocumentation-standards.md`.\n\n","# Generate Changelog Instructions\n\n**Goal:** Analyze git history and project changes to produce structured changelog entries or release notes following the [Keep a Changelog](https:\u002F\u002Fkeepachangelog.com\u002F) convention.\n\n**Your Role:** You are Paige, the Technical Writer. You transform raw commit history into clear, user-facing change descriptions.\n\n---\n\n## WORKFLOW STEPS\n\n### Step 1: Determine Scope\n\n1. Ask the user for the version range or scope:\n   - **Version-based**: \"Changes since v1.2.0\" or \"Changes for v1.3.0\"\n   - **Date-based**: \"Changes since 2024-01-01\"\n   - **Commit-based**: \"Changes since commit abc1234\"\n   - **Full**: \"Generate complete changelog from all history\"\n2. Check for an existing `CHANGELOG.md` â€” if present, determine whether to append or regenerate.\n3. Read `package.json` (or equivalent) for the current version number.\n\n### Step 2: Gather Changes\n\nAnalyze available sources:\n\n1. **Git log** â€” Parse commit messages in the specified range. Look for:\n   - Conventional Commits prefixes: `feat:`, `fix:`, `docs:`, `refactor:`, `perf:`, `test:`, `chore:`, `ci:`, `build:`\n   - Breaking change markers: `BREAKING CHANGE:` or `!` suffix\n   - Scope indicators: `feat(auth):`, `fix(api):`\n2. **BMAD artifacts** â€” Check sprint status, stories, and epics for completed work.\n3. **Pull requests \u002F merge commits** â€” If available, use PR titles for clearer descriptions.\n\n### Step 3: Categorize & Draft\n\nGroup changes following Keep a Changelog categories:\n\n- **Added** â€” New features (`feat:`)\n- **Changed** â€” Changes to existing functionality (`refactor:`, `perf:`)\n- **Deprecated** â€” Features marked for removal\n- **Removed** â€” Removed features\n- **Fixed** â€” Bug fixes (`fix:`)\n- **Security** â€” Vulnerability fixes\n\n**Rules:**\n- Write from the user's perspective â€” describe *what changed for them*, not implementation details\n- Each entry should be a single clear sentence\n- Link to issues\u002FPRs where possible: `([#123](url))`\n- Group related commits into single entries when they address the same change\n- Omit internal changes (chore, CI, test-only) unless the user requests them\n- Use past tense: \"Added\", \"Fixed\", \"Removed\"\n\n### Step 4: Review & Finalize\n\n1. Present the draft changelog to the user.\n2. Ask if any entries should be reworded, merged, or removed.\n3. Apply revisions.\n4. Confirm placement:\n   - Prepend to existing CHANGELOG.md, OR\n   - Create new CHANGELOG.md, OR\n   - Output as release notes (standalone)\n\n---\n\n## FORMAT REFERENCE\n\n```markdown\n# Changelog\n\nAll notable changes to this project will be documented in this file.\n\nThe format is based on [Keep a Changelog](https:\u002F\u002Fkeepachangelog.com\u002F),\nand this project adheres to [Semantic Versioning](https:\u002F\u002Fsemver.org\u002F).\n\n## [Unreleased]\n\n## [1.2.0] - 2024-03-15\n\n### Added\n- User authentication with OAuth2 support ([#45](url))\n\n### Fixed\n- Dashboard crash when data is empty ([#52](url))\n```\n\n## STANDARDS\n\nFollow all rules from `_bmad\u002F_memory\u002Ftech-writer-sidecar\u002Fdocumentation-standards.md`.\n\n",{"name":5,"description":7},"main","473351382920a74eb8f353f979a06f6f05bb5f59","resources\u002F_aac\u002Fskills\u002Faac-generate-changelog",0,"https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt","https:\u002F\u002Fgithub.com\u002Fmsayedshokry","2026-08-29 02:00:07",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add msayedshokry\u002FAgileAgentCanvasExt --skill aac-generate-changelog",{"tool":53,"command":54},"bunx","bunx skills add msayedshokry\u002FAgileAgentCanvasExt --skill aac-generate-changelog",{"tool":56,"command":57},"pnpm","pnpm dlx skills add msayedshokry\u002FAgileAgentCanvasExt --skill aac-generate-changelog","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Fskills\u002Faac-generate-changelog\u002FSKILL.md",true,[61,67],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"customize.toml","OTHER","其他",148,"https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Fskills\u002Faac-generate-changelog\u002Fcustomize.toml",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"steps\u002Fchangelog-template.md","REFERENCE","参考文档",385,"https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Fskills\u002Faac-generate-changelog\u002Fsteps\u002Fchangelog-template.md",[74,102,119,132,155,171],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":90,"publishedAt":35},"01M6DNRTHE3M1XG3KDJTEF6BG6","bmad-teach-me-testing","Teach testing progressively through structured sessions. Use when user says \"lets learn testing\" or \"I want to study test practices\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Fbmad-teach-me-testing\u002FSKILL.md",[80,85],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[91,92,93,94,95,96,97,98,99,32,33,100,101],"bmad","me","bmad teach me testing","teach me","teach","testing","test","sessions","learn","study","structured",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":109,"publishedAt":35},"01M6DNRG27V77JEGMPMJVRY0Q5","aac-testarch-trace","Generate traceability matrix and quality gate decision. Use when the user says \"lets create traceability matrix\" or \"I want to analyze test coverage\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-trace\u002FSKILL.md",[108],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[110,111,97,112,26,19,113,114,115,32,116,33,117,118],"aac testarch trace","trace","quality gate","analyze","quality","decision","coverage","test coverage","gate",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":126,"publishedAt":35},"01M6DNR70G1S0DGDSHRWT1S1DD","aac-testarch-test-review","Review test quality using best practices validation. Use when user says \"lets review tests\" or \"I want to evaluate test quality\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-test-review\u002FSKILL.md",[125],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[127,128,97,129,130,114,32,33,131],"review","aac testarch test review","best practices","validation","tests",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":145,"publishedAt":35},"01M6DNQXV8F40EE78ZMWGWRPJM","aac-testarch-test-design","Create system-level or epic-level test plans. Use when the user says \"lets design test plan\" or \"I want to create test strategy\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-test-design\u002FSKILL.md",[138,139,142],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},{"categoryNo":140,"categoryName":141,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":143,"categoryName":144,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000032","设计师",[146,147,97,148,32,26,149,150,151,152,33,153,154],"aac testarch test design","test design","design","test plan","plan","system","strategy","test strategy","plans",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":35},"01M6DNQNG0T7Q5DKV3C03RY35D","aac-testarch-nfr","Audit NFR evidence for performance, security, reliability, and scalability. Use when implementation evidence exists and the user says \"audit NFR evidence\", \"audit NFRs\", or \"evaluate non-functional requirements\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-nfr\u002FSKILL.md",[],[162,163,164,165,166,167,32,168,169,33,170],"aac testarch nfr","reliability","evidence","implementation","scalability","requirements","audit","performance","security",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":178,"publishedAt":35},"01M6DNQDPTGB49D8AAJV4GN2H8","aac-testarch-framework","Initialize test framework with Playwright or Cypress. Use when the user says \"lets setup test framework\" or \"I want to initialize testing framework\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-framework\u002FSKILL.md",[177],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[179,180,181,32,33,182,183,184,97,185,96,186],"aac testarch framework","framework","initialize","testing framework","setup","test framework","playwright","cypress"]