[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NRCM5D62FAY1P8721TNAQT":3,"skill-same:01M6NRCM5D62FAY1P8721TNAQT":64},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M6NRCM5D62FAY1P8721TNAQT","create-github-issue",null,"Create GitHub issues using GitHub CLI with support for templates, labels, assignees, milestones, and draft issues. Use when the user asks to create a GitHub issue, file a bug report, submit a feature request, or open an issue in a GitHub repository.","KaiavN\u002Fanvilcode","KaiavN","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F189643559?v=4","01M6NRB6Q4GDVQ35BJREN410AT","Kaiav Nihalani","01M6NRB6VFZ4266E5SFAQH44FM",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FKaiavN\u002Fanvilcode\u002Fblob\u002Fmain\u002F.anvil\u002Fskills\u002Fcreate-github-issue\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"github","issue","github issue","create","create github issue","issues","file","open","use","support","cli","draft","feature","submit","github cli","with","for","labels","milestones","request","2026-11-10 10:12:30",false,"---\nname: create-github-issue\ndescription: Create GitHub issues using GitHub CLI with support for templates, labels, assignees, milestones, and draft issues. Use when the user asks to create a GitHub issue, file a bug report, submit a feature request, or open an issue in a GitHub repository.\n---\n\n# Create GitHub Issue\n\nCreate comprehensive GitHub issues using `gh issue create` by dynamically discovering and adhering to the repository's official issue templates.\n\n## Workflow\n\n### 1. Discover and Select Template\n\n**CRITICAL**: You must use the repository's official templates. Do not assume the structure.\n\n1.  **List available templates**:\n    ```bash\n    ls .github\u002FISSUE_TEMPLATE\u002F\n    ```\n2.  **Select the most appropriate template** based on the issue type (e.g., `bug_report.yml`, `feature_request.yml`).\n3.  **Read the selected template** to understand its required fields, structure, and any title prefixes or default labels.\n    ```bash\n    cat .github\u002FISSUE_TEMPLATE\u002F\u003Cselected_template>.yml\n    ```\n\n### 2. Gather Context\n\nGather relevant information to fulfill the template requirements:\n\n```bash\n# Check current git status for context\ngit status\n\n# View recent commits if related to codebase changes\ngit log --oneline -10\n\n# Check if related issues exist\ngh issue list --search \"keyword\" --limit 10\n```\n\n### 3. Generate Markdown Body\n\n**MANDATORY**: Structure the issue body exactly as defined in the selected YAML template without exception.\n\n1.  **Map YAML fields to Markdown**: Convert each field in the template (typically found under `body:`) into a Markdown section.\n2.  **Use Headers**: Use the `label` or `id` from the YAML field as an H2 header (e.g., `## Bug Description`).\n3.  **Respect Validation**: Ensure all fields marked as `required: true` in the YAML are populated with meaningful content.\n4.  **Format Correctly**: Use code blocks (e.g., ` ```shell `, ` ```yaml `) for logs and configurations as suggested by the template's `render` attribute.\n\n### 4. Choose Labels\n\nSelect labels by inspecting `.github\u002Flabels.json`.\n\n- **Primary Label**: Always include a `type:` label that matches the issue type.\n- **Additional Labels**: Add relevant `state:`, `work:`, or `priority:` labels if they exist in the configuration.\n- **Constraint**: **Only use labels defined in `.github\u002Flabels.json`.**\n\n### 5. Create Title\n\nFollow the template's `title` field if it provides a prefix (e.g., `\"[Bug]: \"`).\n\n- **Be concise**: Keep under 70 characters.\n- **Use imperative mood**: \"Fix authentication timeout\" instead of \"Authentication is timing out\".\n- **Start with action verb**: Fix, Add, Improve, Update, Refactor.\n\n### 6. Execute Issue Creation\n\n**Step 1: Write body to temp file**\nUse the `write` tool to create `.anvil\u002FANVIL_ISSUE_BODY.md` with the structured Markdown content.\n\n**Step 2: Create issue**\n```bash\ngh issue create \\\n  --title \"[Prefix]: Descriptive Title\" \\\n  --body-file .anvil\u002FANVIL_ISSUE_BODY.md \\\n  --label \"type: \u003Ctype>, work: \u003Ccomplexity>\"\n```\n\n**Optional flags**:\n- `--assignee \"username\"`\n- `--milestone \"name\"`\n- `--draft` (For proposals or research)\n\n### 7. Finalize\n\nProvide the user with the generated issue URL and a brief summary of the created issue.\n\n## Guidelines\n\n- **No Exceptions**: You must follow the discovered template's structure exactly. If a template asks for \"Steps to Reproduce\", you must provide them.\n- **Dynamic Discovery**: Always read the files in `.github\u002FISSUE_TEMPLATE\u002F` and `.github\u002Flabels.json` first. Never rely on hardcoded knowledge of templates or labels as they change frequently.\n- **Cleanliness**: Ensure no placeholder text (like \"Describe the bug...\") remains in the final body.\n- **Contextual Awareness**: If the user provides logs or code snippets, ensure they are placed in the correct sections of the template.\n\n## Notes\n\n- **Single Source of Truth**: The files in `.github\u002F` are the authoritative reference for issue structure and categorization.\n- **Tooling**: Use `gh` CLI directly. It is pre-authenticated and ready for use.\n- **Automation**: Do not ask for confirmation before creating the issue if the user's intent is clear.","# Create GitHub Issue\n\nCreate comprehensive GitHub issues using `gh issue create` by dynamically discovering and adhering to the repository's official issue templates.\n\n## Workflow\n\n### 1. Discover and Select Template\n\n**CRITICAL**: You must use the repository's official templates. Do not assume the structure.\n\n1.  **List available templates**:\n    ```bash\n    ls .github\u002FISSUE_TEMPLATE\u002F\n    ```\n2.  **Select the most appropriate template** based on the issue type (e.g., `bug_report.yml`, `feature_request.yml`).\n3.  **Read the selected template** to understand its required fields, structure, and any title prefixes or default labels.\n    ```bash\n    cat .github\u002FISSUE_TEMPLATE\u002F\u003Cselected_template>.yml\n    ```\n\n### 2. Gather Context\n\nGather relevant information to fulfill the template requirements:\n\n```bash\n# Check current git status for context\ngit status\n\n# View recent commits if related to codebase changes\ngit log --oneline -10\n\n# Check if related issues exist\ngh issue list --search \"keyword\" --limit 10\n```\n\n### 3. Generate Markdown Body\n\n**MANDATORY**: Structure the issue body exactly as defined in the selected YAML template without exception.\n\n1.  **Map YAML fields to Markdown**: Convert each field in the template (typically found under `body:`) into a Markdown section.\n2.  **Use Headers**: Use the `label` or `id` from the YAML field as an H2 header (e.g., `## Bug Description`).\n3.  **Respect Validation**: Ensure all fields marked as `required: true` in the YAML are populated with meaningful content.\n4.  **Format Correctly**: Use code blocks (e.g., ` ```shell `, ` ```yaml `) for logs and configurations as suggested by the template's `render` attribute.\n\n### 4. Choose Labels\n\nSelect labels by inspecting `.github\u002Flabels.json`.\n\n- **Primary Label**: Always include a `type:` label that matches the issue type.\n- **Additional Labels**: Add relevant `state:`, `work:`, or `priority:` labels if they exist in the configuration.\n- **Constraint**: **Only use labels defined in `.github\u002Flabels.json`.**\n\n### 5. Create Title\n\nFollow the template's `title` field if it provides a prefix (e.g., `\"[Bug]: \"`).\n\n- **Be concise**: Keep under 70 characters.\n- **Use imperative mood**: \"Fix authentication timeout\" instead of \"Authentication is timing out\".\n- **Start with action verb**: Fix, Add, Improve, Update, Refactor.\n\n### 6. Execute Issue Creation\n\n**Step 1: Write body to temp file**\nUse the `write` tool to create `.anvil\u002FANVIL_ISSUE_BODY.md` with the structured Markdown content.\n\n**Step 2: Create issue**\n```bash\ngh issue create \\\n  --title \"[Prefix]: Descriptive Title\" \\\n  --body-file .anvil\u002FANVIL_ISSUE_BODY.md \\\n  --label \"type: \u003Ctype>, work: \u003Ccomplexity>\"\n```\n\n**Optional flags**:\n- `--assignee \"username\"`\n- `--milestone \"name\"`\n- `--draft` (For proposals or research)\n\n### 7. Finalize\n\nProvide the user with the generated issue URL and a brief summary of the created issue.\n\n## Guidelines\n\n- **No Exceptions**: You must follow the discovered template's structure exactly. If a template asks for \"Steps to Reproduce\", you must provide them.\n- **Dynamic Discovery**: Always read the files in `.github\u002FISSUE_TEMPLATE\u002F` and `.github\u002Flabels.json` first. Never rely on hardcoded knowledge of templates or labels as they change frequently.\n- **Cleanliness**: Ensure no placeholder text (like \"Describe the bug...\") remains in the final body.\n- **Contextual Awareness**: If the user provides logs or code snippets, ensure they are placed in the correct sections of the template.\n\n## Notes\n\n- **Single Source of Truth**: The files in `.github\u002F` are the authoritative reference for issue structure and categorization.\n- **Tooling**: Use `gh` CLI directly. It is pre-authenticated and ready for use.\n- **Automation**: Do not ask for confirmation before creating the issue if the user's intent is clear.",{"name":5,"description":7},"main","c0fb0c138f22dc6ccb9d6ded2bbe4f4a0ad55871",".anvil\u002Fskills\u002Fcreate-github-issue","https:\u002F\u002Fgithub.com\u002FKaiavN\u002Fanvilcode","https:\u002F\u002Fgithub.com\u002FKaiavN","2026-07-07 13:07:52",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add KaiavN\u002Fanvilcode --skill create-github-issue",{"tool":56,"command":57},"bunx","bunx skills add KaiavN\u002Fanvilcode --skill create-github-issue",{"tool":59,"command":60},"pnpm","pnpm dlx skills add KaiavN\u002Fanvilcode --skill create-github-issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKaiavN\u002Fanvilcode\u002Fblob\u002Fmain\u002F.anvil\u002Fskills\u002Fcreate-github-issue\u002FSKILL.md",true,[],[65,86,107,132,146,156],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":39},"01M6NRGQ4SK8GXS1F3V80J6W0C","github-pr-description","Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.","https:\u002F\u002Fgithub.com\u002FKaiavN\u002Fanvilcode\u002Fblob\u002Fmain\u002Fcrates\u002Fanvil_repo\u002Fsrc\u002Fskills\u002Fgithub-pr-description\u002FSKILL.md",[],[72,19,73,74,75,76,77,38,78,79,33,29,80,81,82,83,22,84,32,85],"pr","pr description","github pr description","github pr","how","pull","review","why","git","commit","make","history","how to","generate",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":39},"01M6NRGH99KKAAGB4329D61HGE","execute-plan","Execute structured task plans with status tracking. Use when the user provides a plan file path in the format `plans\u002F{current-date}-{task-name}-{version}.md` or explicitly asks you to execute a plan file.","https:\u002F\u002Fgithub.com\u002FKaiavN\u002Fanvilcode\u002Fblob\u002Fmain\u002Fcrates\u002Fanvil_repo\u002Fsrc\u002Fskills\u002Fexecute-plan\u002FSKILL.md",[],[93,94,95,96,97,98,99,27,100,101,102,103,104,34,105,106,25],"plan","execute","execute plan","path","format","tracking","user","version","task","structured","plans","name","you","status",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":118,"publishedAt":39},"01M6NRFYV1V0C8WN3MRA1M7QYT","create-skill","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends your capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002FKaiavN\u002Fanvilcode\u002Fblob\u002Fmain\u002Fcrates\u002Fanvil_repo\u002Fsrc\u002Fskills\u002Fcreate-skill\u002FSKILL.md",[113],{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[22,119,120,121,122,35,34,123,124,125,126,127,128,129,130,131],"create skill","users","specialized","Existing","existing skill","new skill","guide","integrations","tool","knowledge","capabilities","update","workflows",{"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":142,"publishedAt":39},"01M6NRF8MS1B57QAF3ZEMMAFK2","test-skill","A test skill with resources","https:\u002F\u002Fgithub.com\u002FKaiavN\u002Fanvilcode\u002Fblob\u002Fmain\u002Fcrates\u002Fanvil_repo\u002Fsrc\u002Ffixtures\u002Fskills_with_resources\u002Ftest-skill\u002FSKILL.md",[138,141],{"categoryNo":139,"categoryName":140,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},[143,144,145,34],"Test Skill","test","resources",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":153,"publishedAt":39},"01M6NRF44X1012P1HQH33Q8FCR","minimal-skill","A minimal skill with no resources","https:\u002F\u002Fgithub.com\u002FKaiavN\u002Fanvilcode\u002Fblob\u002Fmain\u002Fcrates\u002Fanvil_repo\u002Fsrc\u002Ffixtures\u002Fskills_with_resources\u002Fminimal-skill\u002FSKILL.md",[152],{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},[154,155,34,145],"minimal","minimal skill",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":39},"01M6NREZDXR7YVWQJG6YSJXZGD","write-release-notes","Generate engaging, high-energy release notes for a given version tag. Fetches the release from GitHub, retrieves every linked PR's title and description, then synthesizes all changes into a polished, user-facing release note with an enthusiastic tone. Use when the user asks to write, generate, or create release notes for a version (e.g. \"write release notes for v1.32.0\", \"generate release notes for the latest release\", \"create changelog for v2.0\").","https:\u002F\u002Fgithub.com\u002FKaiavN\u002Fanvilcode\u002Fblob\u002Fmain\u002F.anvil\u002Fskills\u002Fwrite-release-notes\u002FSKILL.md",[],[163,164,165,166,167,168,169,170,171,35,172,34,173,100,27,174,22,72,175,19],"write release notes","release notes","notes","release","write","high-energy","title","energy","changes","v1","tone","changelog","create release"]