[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GV8YCS5QFVMX41QHZPKFS8":3,"skill-same:01M6GV8YCS5QFVMX41QHZPKFS8":69},{"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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M6GV8YCS5QFVMX41QHZPKFS8","issue-tracking",null,"Manage tasks, epics, and bugs based on ISSUE_TRACKING environment variable. Use `env-get` to determine storage (fs or github) and tools.","dragoscirjan\u002Fopencode-config","dragoscirjan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F950596?v=4","01M6GV509X835Z595VVKDX1HFY","Dragos Cirjan","01M6GV50XSMSSD7W2M2KJXTQN6",1,"MIT","https:\u002F\u002Fgithub.com\u002Fdragoscirjan\u002Fopencode-config\u002Fblob\u002Fmain\u002Fskills\u002Fissue-tracking\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31],"tracking","issue","issue tracking","github","storage","tasks","fs","Tools","environment","use","manage","get","env","2026-11-10 10:12:30",false,"---\nname: issue-tracking\ndescription: Manage tasks, epics, and bugs based on ISSUE_TRACKING environment variable. Use `env-get` to determine storage (fs or github) and tools.\n---\n\n# Issue Tracking\n\n- Run `env-get` tool for the `ISSUE_TRACKING` variable to determine the issue tracking environment and available tools:\n  - e.g., `ISSUE_TRACKING=fs,issue-create,issue-list,issue-read` means issues are stored locally in the file system, and you must use those tools to manage them.\n  - e.g., `ISSUE_TRACKING=github,gh,cvs_github` means issues are stored on GitHub, and you should use the `gh` cli or `cvs_github` MCP tools.\n\n## Templates\n\n- **Issues:** Follow the instructions in `skills\u002Fissue-tracking\u002Fissue.md` to format your issue body.\n  - *Note:* The YAML frontmatter (id, type, parent, etc.) is automatically added by the `issue-create` tool (when using `fs`). Do NOT add it yourself when creating an issue. You may update it later if necessary.\n- **Comments:** Format your updates and comments using `skills\u002Fissue-tracking\u002Fcomment.md`.\n\n## Content & Format\n\nWhen describing features, stories, or bugs, use the **Gherkin format** as much as possible for clarity:\n\n```gherkin\nAs a [persona]\nI want to [action]\nSo that [benefit\u002Fvalue]\n\n# OR\n\nGiven [initial context\u002Fstate]\nAnd [more context]\nWhen [action occurs]\nAnd [more actions]\nThen [expected outcome]\nAnd [more outcomes]\n```\n\n## Hierarchy & Emoticons\n\nIf not created for the file system (`ISSUE_TRACKING=fs,...`), the issue title **MUST** contain as prefix the exact emoticon (e.g., `? Q3 Goals`). Do **NOT** manage or use labels.\n\n- **? Initiative** (`initiative`): Top-level business goal.\n  - **?️ Epic** (`epic`): Large project phase.\n    - **? Story** (`story`): User-facing feature.\n      - **?️ Task** (`task`): Atomic implementation step.\n      - **? Bug** (`bug`): Defect in a story.\n    - **? Bug** (`bug`): Defect in an epic.\n\n## Issue Rules\n\n- **Links over Text:** Link to local `.specs\u002F` files in comments instead of pasting large content.\n- **Hierarchy Links:** Use markdown (`#42`) to link parent\u002Fchild and dependent issues.\n- **Report Failures:** Always post execution failures as CVS comments so humans can see them.\n","# Issue Tracking\n\n- Run `env-get` tool for the `ISSUE_TRACKING` variable to determine the issue tracking environment and available tools:\n  - e.g., `ISSUE_TRACKING=fs,issue-create,issue-list,issue-read` means issues are stored locally in the file system, and you must use those tools to manage them.\n  - e.g., `ISSUE_TRACKING=github,gh,cvs_github` means issues are stored on GitHub, and you should use the `gh` cli or `cvs_github` MCP tools.\n\n## Templates\n\n- **Issues:** Follow the instructions in `skills\u002Fissue-tracking\u002Fissue.md` to format your issue body.\n  - *Note:* The YAML frontmatter (id, type, parent, etc.) is automatically added by the `issue-create` tool (when using `fs`). Do NOT add it yourself when creating an issue. You may update it later if necessary.\n- **Comments:** Format your updates and comments using `skills\u002Fissue-tracking\u002Fcomment.md`.\n\n## Content & Format\n\nWhen describing features, stories, or bugs, use the **Gherkin format** as much as possible for clarity:\n\n```gherkin\nAs a [persona]\nI want to [action]\nSo that [benefit\u002Fvalue]\n\n# OR\n\nGiven [initial context\u002Fstate]\nAnd [more context]\nWhen [action occurs]\nAnd [more actions]\nThen [expected outcome]\nAnd [more outcomes]\n```\n\n## Hierarchy & Emoticons\n\nIf not created for the file system (`ISSUE_TRACKING=fs,...`), the issue title **MUST** contain as prefix the exact emoticon (e.g., `? Q3 Goals`). Do **NOT** manage or use labels.\n\n- **? Initiative** (`initiative`): Top-level business goal.\n  - **?️ Epic** (`epic`): Large project phase.\n    - **? Story** (`story`): User-facing feature.\n      - **?️ Task** (`task`): Atomic implementation step.\n      - **? Bug** (`bug`): Defect in a story.\n    - **? Bug** (`bug`): Defect in an epic.\n\n## Issue Rules\n\n- **Links over Text:** Link to local `.specs\u002F` files in comments instead of pasting large content.\n- **Hierarchy Links:** Use markdown (`#42`) to link parent\u002Fchild and dependent issues.\n- **Report Failures:** Always post execution failures as CVS comments so humans can see them.\n",{"name":5,"description":7},"main","f14d6437b86dcd1257925a71587a253624705809","skills\u002Fissue-tracking",0,"https:\u002F\u002Fgithub.com\u002Fdragoscirjan\u002Fopencode-config","https:\u002F\u002Fgithub.com\u002Fdragoscirjan","http:\u002F\u002Flunaticthinker.me","2026-08-23 18:29:44",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add dragoscirjan\u002Fopencode-config --skill issue-tracking",{"tool":51,"command":52},"bunx","bunx skills add dragoscirjan\u002Fopencode-config --skill issue-tracking",{"tool":54,"command":55},"pnpm","pnpm dlx skills add dragoscirjan\u002Fopencode-config --skill issue-tracking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdragoscirjan\u002Fopencode-config\u002Fblob\u002Fmain\u002Fskills\u002Fissue-tracking\u002FSKILL.md",true,[59,65],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"comment.md","REFERENCE","参考文档",727,"https:\u002F\u002Fgithub.com\u002Fdragoscirjan\u002Fopencode-config\u002Fblob\u002Fmain\u002Fskills\u002Fissue-tracking\u002Fcomment.md",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"issue.md",1885,"https:\u002F\u002Fgithub.com\u002Fdragoscirjan\u002Fopencode-config\u002Fblob\u002Fmain\u002Fskills\u002Fissue-tracking\u002Fissue.md",[70,86,104,122,143,155],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":32},"01M6GVBX5M8KVG8EZP2QTYZDGB","productivity-clarify","Guidelines for clarifying ambiguous tasks. Load when the immediate user request lacks execution context.","https:\u002F\u002Fgithub.com\u002Fdragoscirjan\u002Fopencode-config\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity-clarify\u002FSKILL.md",[],[77,78,79,80,24,81,82,83,84,85],"productivity","productivity clarify","clarify","user","load","guidelines","user request","context","execution",{"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":32},"01M6GVBQX6W1C1RAZE43EQ9NEY","productivity-caveman","Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says \"caveman mode\", \"talk like caveman\", \"use caveman\", \"less tokens\", \"be brief\", or invokes \u002Fcaveman.","https:\u002F\u002Fgithub.com\u002Fdragoscirjan\u002Fopencode-config\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity-caveman\u002FSKILL.md",[],[77,93,94,95,80,28,96,97,98,99,100,101,102,103],"caveman","productivity caveman","technical","full","token","tokens","usage","mode","ultra","brief","communication",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":115,"publishedAt":32},"01M6GVBHX6SZRBE7440A5RA6X9","mcp-tools","External MCP tools reference. Load at task start.","https:\u002F\u002Fgithub.com\u002Fdragoscirjan\u002Fopencode-config\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-tools\u002FSKILL.md",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[26,116,117,118,119,120,81,121],"mcp tools","MCP","reference","start","task","at",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":132,"publishedAt":32},"01M6GVBD1AZ6NWNYAAQ9J9E71X","mcp-tools-godot","Godot MCP servers reference — editor, diagnostics, testing, docs, runtime. Load when doing Godot game dev.","https:\u002F\u002Fgithub.com\u002Fdragoscirjan\u002Fopencode-config\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-tools-godot\u002FSKILL.md",[128,131],{"categoryNo":129,"categoryName":130,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},[26,133,134,116,117,135,136,137,138,139,140,141,118,142,81],"mcp tools godot","godot","mcp servers","testing","docs","editor","diagnostics","dev","game","runtime",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":32},"01M6GVBA6DM84KYRDPP1Q83GBJ","lang-zig","Zig development standards and tooling.","https:\u002F\u002Fgithub.com\u002Fdragoscirjan\u002Fopencode-config\u002Fblob\u002Fmain\u002Fskills\u002Flang-zig\u002FSKILL.md",[],[150,151,152,153,154],"zig","lang zig","development","tooling","standards",{"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":32},"01M6GVB8PKXRMMJ4B2YPZG1350","lang-yaml","YAML standards and tooling.","https:\u002F\u002Fgithub.com\u002Fdragoscirjan\u002Fopencode-config\u002Fblob\u002Fmain\u002Fskills\u002Flang-yaml\u002FSKILL.md",[],[162,163,153,154],"yaml","lang yaml"]