[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CX1SPHJB5PHW3W2Q97R5E7":3,"skill-same:01M6CX1SPHJB5PHW3W2Q97R5E7":72},{"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":23,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":65},"01M6CX1SPHJB5PHW3W2Q97R5E7","dot-ai-changelog-fragment",null,"Create changelog fragment for release notes. Invoke during \u002Fprd-done workflow during the first push to the PR.","vfarcic\u002Fdot-ai-headlamp","vfarcic","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5716227?v=4","01M6C41XBA7GK0NJG2D4GV11SC","Viktor Farcic","01M6CX1QQ81N9D052KA5HJE8YS",3,"MIT","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-changelog-fragment\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"changelog","dot","dot ai changelog fragment","dot ai","workflow","notes","pr","release notes","create","release","push","prd","first","done","2026-11-10 10:12:30",false,"---\nname: dot-ai-changelog-fragment\ndescription: Create changelog fragment for release notes. Invoke during \u002Fprd-done workflow during the first push to the PR.\nuser-invocable: true\n---\n\n# Create Changelog Fragment\n\nCreate a towncrier changelog fragment for release notes when completing PRD work. This should be included in the PR so the fragment is reviewed along with the code changes.\n\n## Workflow\n\n### Step 1: Identify the PRD\n\nIf not already known from context, ask: \"Which PRD should I create release notes for?\"\n\nLook for:\n- PRD mentioned in recent conversation\n- PRD referenced in current branch name (e.g., `feature\u002Fprd-320-*`)\n- PRD file path provided by user\n\n### Step 2: Read the PRD Thoroughly\n\nRead the entire PRD file to extract:\n- **Problem Statement**: What user pain point was solved, why it mattered\n- **Solution Overview**: What the feature does, how it works\n- **User Impact**: Specific benefits, what users can now do\n- **Key Capabilities**: Individual features, options, or modes added\n- **Technical Details**: Configuration options, environment variables, commands\n- **Documentation Updates**: Which docs were added or updated (check Milestones section)\n\n### Step 3: Determine Fragment Type\n\nRead `pyproject.toml` to see the available fragment types. Each `[[tool.towncrier.type]]` section has:\n- A comment above it describing when to use that type\n- A `directory` field (the type identifier used in the filename, e.g., `feature` for `.feature.md`)\n\nChoose the type that best matches the PRD based on those descriptions.\n\n### Step 4: Write the Fragment\n\nCreate file: `changelog.d\u002F[issue-id].[type].md`\n\n**IMPORTANT: Use flat structure, NOT subdirectories!**\n- ✅ Correct: `changelog.d\u002F329.feature.md`\n- ❌ Wrong: `changelog.d\u002Ffeature\u002F329.md`\n\n**Naming convention:**\n- `issue-id`: GitHub issue number from PRD (e.g., `320`)\n- `type`: Type identifier from step 3 (e.g., `feature`, `bugfix`, `misc`)\n\n**Content format:**\n```markdown\n## [Feature Title]\n\n[Opening sentence: What this feature is and the problem it solves]\n\n[Key capabilities paragraph: Specific things users can now do, with concrete examples]\n\n[Configuration\u002Fusage paragraph if applicable: How to enable or use the feature]\n\n[Documentation link if docs were updated]\n```\n\n**Documentation links:**\nIf the PRD includes documentation updates, link to the relevant page on devopstoolkit.ai. The URL pattern is:\n- `https:\u002F\u002Fdevopstoolkit.ai\u002Fdocs\u002F{project}\u002F{path}`\n- Where `{project}` is: `mcp` (dot-ai), `controller` (dot-ai-controller), `ui` (dot-ai-ui), or `stack` (dot-ai-stack)\n- And `{path}` maps from the docs folder (e.g., `docs\u002Fguides\u002Fmcp-recommendation-guide.md` → `guides\u002Fmcp-recommendation-guide`)\n\n**Example: `changelog.d\u002F142.feature.md`**\n```markdown\n## Multi-Cluster Management\n\nManage multiple Kubernetes clusters from a single dot-ai instance. Previously, each cluster required its own dot-ai deployment, making it difficult to compare configurations or apply consistent patterns across environments.\n\nThe `query` tool now accepts a `--cluster` flag to target specific clusters, and results indicate which cluster each resource belongs to. The `recommend` tool can generate manifests targeting different clusters with environment-specific customizations. Cross-cluster searches let you find resources across all connected clusters simultaneously—useful for tracking down where a particular workload is deployed. Cluster health aggregation shows a unified view of all clusters in the `version` output.\n\nConfigure additional clusters by adding kubeconfig contexts to `ADDITIONAL_KUBECONFIGS` (comma-separated paths). Each context becomes available as a cluster target. The default cluster remains the current kubeconfig context when no `--cluster` flag is specified.\n\nSee the [Multi-Cluster Setup Guide](https:\u002F\u002Fdevopstoolkit.ai\u002Fdocs\u002Fmcp\u002Fsetup\u002Fmulti-cluster-setup) for configuration details and examples.\n```\n\n### Step 5: Confirm Creation\n\nShow the user:\n1. The fragment file path created\n2. The content written\n3. Reminder to commit and push with the PR\n\n## Guidelines\n\n- **User-focused**: Describe what users gain, not implementation details\n- **Specific**: Include concrete examples of what each capability does\n- **Complete**: Cover all major features added, not just the headline\n- **Present tense**: \"Tools now return...\" not \"Added support for...\"\n- **No diary style**: \"Multi-Cluster Management\" not \"Added multi-cluster support\"\n- **Include configuration**: Mention environment variables, commands, or setup steps\n- **Link to docs**: If PRD updated documentation, link to the specific page on devopstoolkit.ai\n\n","# Create Changelog Fragment\n\nCreate a towncrier changelog fragment for release notes when completing PRD work. This should be included in the PR so the fragment is reviewed along with the code changes.\n\n## Workflow\n\n### Step 1: Identify the PRD\n\nIf not already known from context, ask: \"Which PRD should I create release notes for?\"\n\nLook for:\n- PRD mentioned in recent conversation\n- PRD referenced in current branch name (e.g., `feature\u002Fprd-320-*`)\n- PRD file path provided by user\n\n### Step 2: Read the PRD Thoroughly\n\nRead the entire PRD file to extract:\n- **Problem Statement**: What user pain point was solved, why it mattered\n- **Solution Overview**: What the feature does, how it works\n- **User Impact**: Specific benefits, what users can now do\n- **Key Capabilities**: Individual features, options, or modes added\n- **Technical Details**: Configuration options, environment variables, commands\n- **Documentation Updates**: Which docs were added or updated (check Milestones section)\n\n### Step 3: Determine Fragment Type\n\nRead `pyproject.toml` to see the available fragment types. Each `[[tool.towncrier.type]]` section has:\n- A comment above it describing when to use that type\n- A `directory` field (the type identifier used in the filename, e.g., `feature` for `.feature.md`)\n\nChoose the type that best matches the PRD based on those descriptions.\n\n### Step 4: Write the Fragment\n\nCreate file: `changelog.d\u002F[issue-id].[type].md`\n\n**IMPORTANT: Use flat structure, NOT subdirectories!**\n- ✅ Correct: `changelog.d\u002F329.feature.md`\n- ❌ Wrong: `changelog.d\u002Ffeature\u002F329.md`\n\n**Naming convention:**\n- `issue-id`: GitHub issue number from PRD (e.g., `320`)\n- `type`: Type identifier from step 3 (e.g., `feature`, `bugfix`, `misc`)\n\n**Content format:**\n```markdown\n## [Feature Title]\n\n[Opening sentence: What this feature is and the problem it solves]\n\n[Key capabilities paragraph: Specific things users can now do, with concrete examples]\n\n[Configuration\u002Fusage paragraph if applicable: How to enable or use the feature]\n\n[Documentation link if docs were updated]\n```\n\n**Documentation links:**\nIf the PRD includes documentation updates, link to the relevant page on devopstoolkit.ai. The URL pattern is:\n- `https:\u002F\u002Fdevopstoolkit.ai\u002Fdocs\u002F{project}\u002F{path}`\n- Where `{project}` is: `mcp` (dot-ai), `controller` (dot-ai-controller), `ui` (dot-ai-ui), or `stack` (dot-ai-stack)\n- And `{path}` maps from the docs folder (e.g., `docs\u002Fguides\u002Fmcp-recommendation-guide.md` → `guides\u002Fmcp-recommendation-guide`)\n\n**Example: `changelog.d\u002F142.feature.md`**\n```markdown\n## Multi-Cluster Management\n\nManage multiple Kubernetes clusters from a single dot-ai instance. Previously, each cluster required its own dot-ai deployment, making it difficult to compare configurations or apply consistent patterns across environments.\n\nThe `query` tool now accepts a `--cluster` flag to target specific clusters, and results indicate which cluster each resource belongs to. The `recommend` tool can generate manifests targeting different clusters with environment-specific customizations. Cross-cluster searches let you find resources across all connected clusters simultaneously—useful for tracking down where a particular workload is deployed. Cluster health aggregation shows a unified view of all clusters in the `version` output.\n\nConfigure additional clusters by adding kubeconfig contexts to `ADDITIONAL_KUBECONFIGS` (comma-separated paths). Each context becomes available as a cluster target. The default cluster remains the current kubeconfig context when no `--cluster` flag is specified.\n\nSee the [Multi-Cluster Setup Guide](https:\u002F\u002Fdevopstoolkit.ai\u002Fdocs\u002Fmcp\u002Fsetup\u002Fmulti-cluster-setup) for configuration details and examples.\n```\n\n### Step 5: Confirm Creation\n\nShow the user:\n1. The fragment file path created\n2. The content written\n3. Reminder to commit and push with the PR\n\n## Guidelines\n\n- **User-focused**: Describe what users gain, not implementation details\n- **Specific**: Include concrete examples of what each capability does\n- **Complete**: Cover all major features added, not just the headline\n- **Present tense**: \"Tools now return...\" not \"Added support for...\"\n- **No diary style**: \"Multi-Cluster Management\" not \"Added multi-cluster support\"\n- **Include configuration**: Mention environment variables, commands, or setup steps\n- **Link to docs**: If PRD updated documentation, link to the specific page on devopstoolkit.ai\n\n",{"name":5,"description":7,"user-invocable":43},true,"main","6faa9f452f568fc9aa9b1c17ee728de11b760cb7",".claude\u002Fskills\u002Fdot-ai-changelog-fragment",1,"https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp","https:\u002F\u002Fgithub.com\u002Fvfarcic","https:\u002F\u002Fyoutube.com\u002Fc\u002Fdevopstoolkit","Developer Advocate @Upbound","2026-06-19 10:10:13",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":43},[55,58,61],{"tool":56,"command":57},"npx","npx skills add vfarcic\u002Fdot-ai-headlamp --skill dot-ai-changelog-fragment",{"tool":59,"command":60},"bunx","bunx skills add vfarcic\u002Fdot-ai-headlamp --skill dot-ai-changelog-fragment",{"tool":62,"command":63},"pnpm","pnpm dlx skills add vfarcic\u002Fdot-ai-headlamp --skill dot-ai-changelog-fragment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-changelog-fragment\u002FSKILL.md",[66],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"scripts\u002Fgenebass_gene_burden.py","SCRIPT","脚本",9739,"https:\u002F\u002Fgithub.com\u002Filderaj\u002Fagent-plugin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex--life-science-research\u002Fskills\u002Fgenebass-gene-burden-skill\u002Fscripts\u002Fgenebass_gene_burden.py",[73,98,116,131,145,155],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":38},"01M6CX45JYT898C3M792AXA5HS","dot-ai","Kubernetes cluster operations via dot-ai CLI - natural language cluster queries, AI-powered deployment recommendations, issue troubleshooting and remediation, Day 2 operations (scale, update, rollback, delete), resources, namespaces, events, logs, organizational knowledge base (ingest, search, query), organizational patterns\u002Fpolicies\u002Fcapabilities management, project scaffolding and repo audit, and session history and visualization. Run `dot-ai --help` for commands.","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai\u002FSKILL.md",[],[25,27,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97],"visualization","delete","repo","deployment","kubernetes","capabilities","search","logs","knowledge","history","project","session","ingest","queries","natural language","query","scaffolding","knowledge base",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":38},"01M6CX42HR85829TGFQ95E7283","dot-ai-write-docs","Write documentation with real, validated examples. Executes commands through the user to capture actual output. Use for any new documentation or major doc updates.","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-write-docs\u002FSKILL.md",[],[25,105,27,106,107,108,109,110,111,112,113,114,115],"docs","write","dot ai write docs","write documentation","commands","use","documentation","examples","doc","capture","user",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":123,"publishedAt":38},"01M6CX4023QEXSVV5C22GG68XW","dot-ai-worktree-prd","Create a git worktree for PRD work with a descriptive branch name. Infers PRD from context or asks user.","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-worktree-prd\u002FSKILL.md",[122],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[35,124,25,125,27,32,126,127,128,129,130,115],"worktree","dot ai worktree prd","git","git worktree","work","branch","context",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":38},"01M6CX3YETQD0A9BPXXQABX0MW","dot-ai-version","Get comprehensive system health and diagnostics","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-version\u002FSKILL.md",[],[27,138,25,139,140,141,142,143,144],"dot ai version","version","diagnostics","health","system","system health","get",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":38},"01M6CX3X07RSJTPNSFEQRX9ACY","dot-ai-users","Manage users (create, list, delete)","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-users\u002FSKILL.md",[],[27,152,25,32,81,153,154],"dot ai users","list","manage",{"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":38},"01M6CX3T6YE6PVSBJGP2WSXM9J","dot-ai-tag-release","Create a release tag based on accumulated changelog fragments. Run when ready to cut a release.","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-tag-release\u002FSKILL.md",[],[27,162,25,33,32,163,24,164],"dot ai tag release","run","ready"]