[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M758DPCB7RR09YFZF594V9RB":3,"skill-same:01M758DPCB7RR09YFZF594V9RB":50},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M758DPCB7RR09YFZF594V9RB","issue-creation",null,"Issue creation workflow for Agent Teams Lite following the issue-first enforcement system. Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature.","davidcoachdev\u002Fdcfiles","davidcoachdev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F69812733?v=4","01M758C4BR16TAV1N47W319E9V","David H. Caycedo Blum.","01M758C4CCZA2ZYGA0BGMXCDRH",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fkilo\u002Fskills\u002Fissue-creation\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: issue-creation\ndescription: >\n  Issue creation workflow for Agent Teams Lite following the issue-first enforcement system.\n  Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature.\nlicense: Apache-2.0\nmetadata:\n  author: gentleman-programming\n  version: \"1.0\"\n---\n\n## When to Use\n\nUse this skill when:\n- Creating a GitHub issue (bug report or feature request)\n- Helping a contributor file an issue\n- Triaging or approving issues as a maintainer\n\n---\n\n## Critical Rules\n\n1. **Blank issues are disabled** — MUST use a template (bug report or feature request)\n2. **Every issue gets `status:needs-review` automatically** on creation\n3. **A maintainer MUST add `status:approved`** before any PR can be opened\n4. **Questions go to [Discussions](https:\u002F\u002Fgithub.com\u002FGentleman-Programming\u002Fagent-teams-lite\u002Fdiscussions)**, not issues\n\n---\n\n## Workflow\n\n```\n1. Search existing issues for duplicates\n2. Choose the correct template (Bug Report or Feature Request)\n3. Fill in ALL required fields\n4. Check pre-flight checkboxes\n5. Submit → issue gets status:needs-review automatically\n6. Wait for maintainer to add status:approved\n7. Only then open a PR linking this issue\n```\n\n---\n\n## Issue Templates\n\n### Bug Report\n\nTemplate: `.github\u002FISSUE_TEMPLATE\u002Fbug_report.yml`\nAuto-labels: `bug`, `status:needs-review`\n\n#### Required Fields\n\n| Field | Description |\n|-------|-------------|\n| **Pre-flight Checks** | Checkboxes: no duplicate + understands approval workflow |\n| **Bug Description** | Clear description of the bug |\n| **Steps to Reproduce** | Numbered steps to reproduce |\n| **Expected Behavior** | What should have happened |\n| **Actual Behavior** | What happened instead (include errors\u002Flogs) |\n| **Operating System** | Dropdown: macOS, Linux variants, Windows, WSL |\n| **Agent \u002F Client** | Dropdown: Claude Code, OpenCode, Gemini CLI, Cursor, Windsurf, Codex, Other |\n| **Shell** | Dropdown: bash, zsh, fish, Other |\n\n#### Optional Fields\n\n| Field | Description |\n|-------|-------------|\n| **Relevant Logs** | Log output (auto-formatted as code block) |\n| **Additional Context** | Screenshots, workarounds, extra info |\n\n#### Example — Bug Report via CLI\n\n```bash\ngh issue create --template \"bug_report.yml\" \\\n  --title \"fix(scripts): setup.sh fails on zsh with glob error\" \\\n  --body \"\n### Pre-flight Checks\n- [x] I have searched existing issues and this is not a duplicate\n- [x] I understand this issue needs status:approved before a PR can be opened\n\n### Bug Description\nRunning setup.sh on zsh throws a glob error when no matching files exist.\n\n### Steps to Reproduce\n1. Clone the repo\n2. Run \\`.\u002Fscripts\u002Fsetup.sh\\` in zsh\n3. See error: \\`zsh: no matches found: skills\u002F*\\`\n\n### Expected Behavior\nThe script should handle missing glob matches gracefully.\n\n### Actual Behavior\nScript crashes with glob error.\n\n### Operating System\nmacOS\n\n### Agent \u002F Client\nClaude Code\n\n### Shell\nzsh\n\n### Relevant Logs\n\\`\\`\\`\nzsh: no matches found: skills\u002F*\n\\`\\`\\`\n\"\n```\n\n---\n\n### Feature Request\n\nTemplate: `.github\u002FISSUE_TEMPLATE\u002Ffeature_request.yml`\nAuto-labels: `enhancement`, `status:needs-review`\n\n#### Required Fields\n\n| Field | Description |\n|-------|-------------|\n| **Pre-flight Checks** | Checkboxes: no duplicate + understands approval workflow |\n| **Problem Description** | The pain point this feature solves |\n| **Proposed Solution** | How it should work from the user's perspective |\n| **Affected Area** | Dropdown: Scripts, Skills, Examples, Documentation, CI\u002FWorkflows, Other |\n\n#### Optional Fields\n\n| Field | Description |\n|-------|-------------|\n| **Alternatives Considered** | Other approaches or workarounds |\n| **Additional Context** | Mockups, examples, references |\n\n#### Example — Feature Request via CLI\n\n```bash\ngh issue create --template \"feature_request.yml\" \\\n  --title \"feat(scripts): add Codex support to setup.sh\" \\\n  --body \"\n### Pre-flight Checks\n- [x] I have searched existing issues and this is not a duplicate\n- [x] I understand this issue needs status:approved before a PR can be opened\n\n### Problem Description\nThe setup script only configures Claude Code, Gemini CLI, and OpenCode. Codex users have to manually copy skills.\n\n### Proposed Solution\nAdd a Codex option to setup.sh that links skills to the .codex\u002F directory.\n\nExample:\n\\`\\`\\`bash\n.\u002Fscripts\u002Fsetup.sh --agent codex\n\\`\\`\\`\n\n### Affected Area\nScripts (setup, installation)\n\n### Alternatives Considered\nManually symlinking, but that defeats the purpose of the setup script.\n\"\n```\n\n---\n\n## Label System\n\n### Applied Automatically on Issue Creation\n\n| Template | Labels added |\n|----------|-------------|\n| Bug Report | `bug`, `status:needs-review` |\n| Feature Request | `enhancement`, `status:needs-review` |\n\n### Applied by Maintainers\n\n| Label | When to apply |\n|-------|--------------|\n| `status:approved` | Issue accepted for implementation — PRs can now be opened |\n| `priority:high` | Critical bug or urgent feature |\n| `priority:medium` | Important but not blocking |\n| `priority:low` | Nice to have |\n\n---\n\n## Maintainer Approval Workflow\n\n```\n1. New issue arrives with status:needs-review\n2. Review the issue — is it valid, clear, and in scope?\n3. If YES → add status:approved label\n4. If NO → comment with reason, close if needed\n5. Contributor can now open a PR linking this issue\n```\n\n---\n\n## Decision Tree\n\n```\nIs it a bug?                    → Use Bug Report template\nIs it a new feature\u002Fimprovement? → Use Feature Request template\nIs it a question?               → Use Discussions, NOT issues\nIs it a duplicate?              → Link to existing issue, close\n```\n\n---\n\n## Commands\n\n```bash\n# Search existing issues before creating\ngh issue list --search \"keyword\"\n\n# Create bug report\ngh issue create --template \"bug_report.yml\" --title \"fix(scope): description\"\n\n# Create feature request\ngh issue create --template \"feature_request.yml\" --title \"feat(scope): description\"\n\n# Maintainer: approve an issue\ngh issue edit \u003Cnumber> --add-label \"status:approved\"\n\n# Maintainer: add priority\ngh issue edit \u003Cnumber> --add-label \"priority:high\"\n```\n","## When to Use\n\nUse this skill when:\n- Creating a GitHub issue (bug report or feature request)\n- Helping a contributor file an issue\n- Triaging or approving issues as a maintainer\n\n---\n\n## Critical Rules\n\n1. **Blank issues are disabled** — MUST use a template (bug report or feature request)\n2. **Every issue gets `status:needs-review` automatically** on creation\n3. **A maintainer MUST add `status:approved`** before any PR can be opened\n4. **Questions go to [Discussions](https:\u002F\u002Fgithub.com\u002FGentleman-Programming\u002Fagent-teams-lite\u002Fdiscussions)**, not issues\n\n---\n\n## Workflow\n\n```\n1. Search existing issues for duplicates\n2. Choose the correct template (Bug Report or Feature Request)\n3. Fill in ALL required fields\n4. Check pre-flight checkboxes\n5. Submit → issue gets status:needs-review automatically\n6. Wait for maintainer to add status:approved\n7. Only then open a PR linking this issue\n```\n\n---\n\n## Issue Templates\n\n### Bug Report\n\nTemplate: `.github\u002FISSUE_TEMPLATE\u002Fbug_report.yml`\nAuto-labels: `bug`, `status:needs-review`\n\n#### Required Fields\n\n| Field | Description |\n|-------|-------------|\n| **Pre-flight Checks** | Checkboxes: no duplicate + understands approval workflow |\n| **Bug Description** | Clear description of the bug |\n| **Steps to Reproduce** | Numbered steps to reproduce |\n| **Expected Behavior** | What should have happened |\n| **Actual Behavior** | What happened instead (include errors\u002Flogs) |\n| **Operating System** | Dropdown: macOS, Linux variants, Windows, WSL |\n| **Agent \u002F Client** | Dropdown: Claude Code, OpenCode, Gemini CLI, Cursor, Windsurf, Codex, Other |\n| **Shell** | Dropdown: bash, zsh, fish, Other |\n\n#### Optional Fields\n\n| Field | Description |\n|-------|-------------|\n| **Relevant Logs** | Log output (auto-formatted as code block) |\n| **Additional Context** | Screenshots, workarounds, extra info |\n\n#### Example — Bug Report via CLI\n\n```bash\ngh issue create --template \"bug_report.yml\" \\\n  --title \"fix(scripts): setup.sh fails on zsh with glob error\" \\\n  --body \"\n### Pre-flight Checks\n- [x] I have searched existing issues and this is not a duplicate\n- [x] I understand this issue needs status:approved before a PR can be opened\n\n### Bug Description\nRunning setup.sh on zsh throws a glob error when no matching files exist.\n\n### Steps to Reproduce\n1. Clone the repo\n2. Run \\`.\u002Fscripts\u002Fsetup.sh\\` in zsh\n3. See error: \\`zsh: no matches found: skills\u002F*\\`\n\n### Expected Behavior\nThe script should handle missing glob matches gracefully.\n\n### Actual Behavior\nScript crashes with glob error.\n\n### Operating System\nmacOS\n\n### Agent \u002F Client\nClaude Code\n\n### Shell\nzsh\n\n### Relevant Logs\n\\`\\`\\`\nzsh: no matches found: skills\u002F*\n\\`\\`\\`\n\"\n```\n\n---\n\n### Feature Request\n\nTemplate: `.github\u002FISSUE_TEMPLATE\u002Ffeature_request.yml`\nAuto-labels: `enhancement`, `status:needs-review`\n\n#### Required Fields\n\n| Field | Description |\n|-------|-------------|\n| **Pre-flight Checks** | Checkboxes: no duplicate + understands approval workflow |\n| **Problem Description** | The pain point this feature solves |\n| **Proposed Solution** | How it should work from the user's perspective |\n| **Affected Area** | Dropdown: Scripts, Skills, Examples, Documentation, CI\u002FWorkflows, Other |\n\n#### Optional Fields\n\n| Field | Description |\n|-------|-------------|\n| **Alternatives Considered** | Other approaches or workarounds |\n| **Additional Context** | Mockups, examples, references |\n\n#### Example — Feature Request via CLI\n\n```bash\ngh issue create --template \"feature_request.yml\" \\\n  --title \"feat(scripts): add Codex support to setup.sh\" \\\n  --body \"\n### Pre-flight Checks\n- [x] I have searched existing issues and this is not a duplicate\n- [x] I understand this issue needs status:approved before a PR can be opened\n\n### Problem Description\nThe setup script only configures Claude Code, Gemini CLI, and OpenCode. Codex users have to manually copy skills.\n\n### Proposed Solution\nAdd a Codex option to setup.sh that links skills to the .codex\u002F directory.\n\nExample:\n\\`\\`\\`bash\n.\u002Fscripts\u002Fsetup.sh --agent codex\n\\`\\`\\`\n\n### Affected Area\nScripts (setup, installation)\n\n### Alternatives Considered\nManually symlinking, but that defeats the purpose of the setup script.\n\"\n```\n\n---\n\n## Label System\n\n### Applied Automatically on Issue Creation\n\n| Template | Labels added |\n|----------|-------------|\n| Bug Report | `bug`, `status:needs-review` |\n| Feature Request | `enhancement`, `status:needs-review` |\n\n### Applied by Maintainers\n\n| Label | When to apply |\n|-------|--------------|\n| `status:approved` | Issue accepted for implementation — PRs can now be opened |\n| `priority:high` | Critical bug or urgent feature |\n| `priority:medium` | Important but not blocking |\n| `priority:low` | Nice to have |\n\n---\n\n## Maintainer Approval Workflow\n\n```\n1. New issue arrives with status:needs-review\n2. Review the issue — is it valid, clear, and in scope?\n3. If YES → add status:approved label\n4. If NO → comment with reason, close if needed\n5. Contributor can now open a PR linking this issue\n```\n\n---\n\n## Decision Tree\n\n```\nIs it a bug?                    → Use Bug Report template\nIs it a new feature\u002Fimprovement? → Use Feature Request template\nIs it a question?               → Use Discussions, NOT issues\nIs it a duplicate?              → Link to existing issue, close\n```\n\n---\n\n## Commands\n\n```bash\n# Search existing issues before creating\ngh issue list --search \"keyword\"\n\n# Create bug report\ngh issue create --template \"bug_report.yml\" --title \"fix(scope): description\"\n\n# Create feature request\ngh issue create --template \"feature_request.yml\" --title \"feat(scope): description\"\n\n# Maintainer: approve an issue\ngh issue edit \u003Cnumber> --add-label \"status:approved\"\n\n# Maintainer: add priority\ngh issue edit \u003Cnumber> --add-label \"priority:high\"\n```\n",{"name":5,"license":15,"metadata":24,"description":27},{"author":25,"version":26},"gentleman-programming","1.0","Issue creation workflow for Agent Teams Lite following the issue-first enforcement system. Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature.\n","main","5dc86f90a5cbe45db3acd917825461b3ed6937fb","config\u002F.config\u002Fkilo\u002Fskills\u002Fissue-creation",0,"https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev","🌐 Apasionado por crear soluciones web escalables y eficientes. \r\n🧑‍🏫 Coach Dev.\r\n💻 Frontend Dev. \r\n🎚️Backend Dev.\r\n📊 Agile\u002FScrum.\r\n🚀100% remoto.","2026-08-26 07:28:05",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add davidcoachdev\u002Fdcfiles --skill issue-creation",{"tool":42,"command":43},"bunx","bunx skills add davidcoachdev\u002Fdcfiles --skill issue-creation",{"tool":45,"command":46},"pnpm","pnpm dlx skills add davidcoachdev\u002Fdcfiles --skill issue-creation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fkilo\u002Fskills\u002Fissue-creation\u002FSKILL.md",true,[],[51,58,65,72,80,87],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7740FETMZY1VTYAEFY1TWY7","zustand-5","Zustand 5 state management patterns. Trigger: When managing React state with Zustand.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fzustand-5\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M773ZZM9V68SA1AKP4WF4J29","zod-4","Zod 4 schema validation patterns. Trigger: When using Zod for validation - breaking changes from v3.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fzod-4\u002FSKILL.md",[],[],{"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":19},"01M773ZJFR90CQAY0N9QR40QVP","x-bookmark-quote-posts","Workflow para revisar bookmarks de X\u002FTwitter y convertirlos en drafts de quote posts. Accede a la sección de bookmarks vía browser headless, extrae posts recientes, y genera drafts con voz personal del usuario. No publica ni muta X — solo genera contenido para revisión. Trigger: X bookmarks, Twitter bookmarks, quote posts, bookmark automation, crear quote posts, revisar bookmarks, growth content X.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fx-bookmark-quote-posts\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M773Z2RGV3786FV310SDB0YD","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","MIT","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M773YJH3KDSW467CSS63CSRJ","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M773Y3S3H2CPRK5S8YFHWB5C","work-unit-commits","Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fwork-unit-commits\u002FSKILL.md",[],[]]