[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F1NG6AB3827D65PXJK97VT":3,"skill-same:01M7F1NG6AB3827D65PXJK97VT":45},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7F1NG6AB3827D65PXJK97VT","git-commit",null,"Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions \"\u002Fcommit\". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type\u002Fscope\u002Fdescription overrides, (4) Intelligent file staging for logical grouping","MesitaDeNoche\u002Ftreasure-szsdevelopers","MesitaDeNoche","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184248336?v=4","01M7F1DAE7QEB7QM5AMTG0MF70","Andres Felipe Mesa Colorado","01M7F1DAEY0XBE65P8ZPWCJX4R",0,"MIT","https:\u002F\u002Fgithub.com\u002FMesitaDeNoche\u002Ftreasure-szsdevelopers\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fgit-commit\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: git-commit\ndescription: 'Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions \"\u002Fcommit\". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type\u002Fscope\u002Fdescription overrides, (4) Intelligent file staging for logical grouping'\nlicense: MIT\nallowed-tools: Bash\n---\n\n# Git Commit with Conventional Commits\n\n## Overview\n\nCreate standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff to determine appropriate type, scope, and message.\n\n## Conventional Commit Format\n\n```\n\u003Ctype>[optional scope]: \u003Cdescription>\n\n[optional body]\n\n[optional footer(s)]\n```\n\n## Commit Types\n\n| Type       | Purpose                        |\n| ---------- | ------------------------------ |\n| `feat`     | New feature                    |\n| `fix`      | Bug fix                        |\n| `docs`     | Documentation only             |\n| `style`    | Formatting\u002Fstyle (no logic)    |\n| `refactor` | Code refactor (no feature\u002Ffix) |\n| `perf`     | Performance improvement        |\n| `test`     | Add\u002Fupdate tests               |\n| `build`    | Build system\u002Fdependencies      |\n| `ci`       | CI\u002Fconfig changes              |\n| `chore`    | Maintenance\u002Fmisc               |\n| `revert`   | Revert commit                  |\n\n## Breaking Changes\n\n```\n# Exclamation mark after type\u002Fscope\nfeat!: remove deprecated endpoint\n\n# BREAKING CHANGE footer\nfeat: allow config to extend other configs\n\nBREAKING CHANGE: `extends` key behavior changed\n```\n\n## Workflow\n\n### 1. Analyze Diff\n\n```bash\n# If files are staged, use staged diff\ngit diff --staged\n\n# If nothing staged, use working tree diff\ngit diff\n\n# Also check status\ngit status --porcelain\n```\n\n### 2. Stage Files (if needed)\n\nIf nothing is staged or you want to group changes differently:\n\n```bash\n# Stage specific files\ngit add path\u002Fto\u002Ffile1 path\u002Fto\u002Ffile2\n\n# Stage by pattern\ngit add *.test.*\ngit add src\u002Fcomponents\u002F*\n\n# Interactive staging\ngit add -p\n```\n\n**Never commit secrets** (.env, credentials.json, private keys).\n\n### 3. Generate Commit Message\n\nAnalyze the diff to determine:\n\n- **Type**: What kind of change is this?\n- **Scope**: What area\u002Fmodule is affected?\n- **Description**: One-line summary of what changed (present tense, imperative mood, \u003C72 chars)\n\n### 4. Execute Commit\n\n```bash\n# Single line\ngit commit -m \"\u003Ctype>[scope]: \u003Cdescription>\"\n\n# Multi-line with body\u002Ffooter\ngit commit -m \"$(cat \u003C\u003C'EOF'\n\u003Ctype>[scope]: \u003Cdescription>\n\n\u003Coptional body>\n\n\u003Coptional footer>\nEOF\n)\"\n```\n\n## Best Practices\n\n- One logical change per commit\n- Present tense: \"add\" not \"added\"\n- Imperative mood: \"fix bug\" not \"fixes bug\"\n- Reference issues: `Closes #123`, `Refs #456`\n- Keep description under 72 characters\n\n## Git Safety Protocol\n\n- NEVER update git config\n- NEVER run destructive commands (--force, hard reset) without explicit request\n- NEVER skip hooks (--no-verify) unless user asks\n- NEVER force push to main\u002Fmaster\n- If commit fails due to hooks, fix and create NEW commit (don't amend)\n","# Git Commit with Conventional Commits\n\n## Overview\n\nCreate standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff to determine appropriate type, scope, and message.\n\n## Conventional Commit Format\n\n```\n\u003Ctype>[optional scope]: \u003Cdescription>\n\n[optional body]\n\n[optional footer(s)]\n```\n\n## Commit Types\n\n| Type       | Purpose                        |\n| ---------- | ------------------------------ |\n| `feat`     | New feature                    |\n| `fix`      | Bug fix                        |\n| `docs`     | Documentation only             |\n| `style`    | Formatting\u002Fstyle (no logic)    |\n| `refactor` | Code refactor (no feature\u002Ffix) |\n| `perf`     | Performance improvement        |\n| `test`     | Add\u002Fupdate tests               |\n| `build`    | Build system\u002Fdependencies      |\n| `ci`       | CI\u002Fconfig changes              |\n| `chore`    | Maintenance\u002Fmisc               |\n| `revert`   | Revert commit                  |\n\n## Breaking Changes\n\n```\n# Exclamation mark after type\u002Fscope\nfeat!: remove deprecated endpoint\n\n# BREAKING CHANGE footer\nfeat: allow config to extend other configs\n\nBREAKING CHANGE: `extends` key behavior changed\n```\n\n## Workflow\n\n### 1. Analyze Diff\n\n```bash\n# If files are staged, use staged diff\ngit diff --staged\n\n# If nothing staged, use working tree diff\ngit diff\n\n# Also check status\ngit status --porcelain\n```\n\n### 2. Stage Files (if needed)\n\nIf nothing is staged or you want to group changes differently:\n\n```bash\n# Stage specific files\ngit add path\u002Fto\u002Ffile1 path\u002Fto\u002Ffile2\n\n# Stage by pattern\ngit add *.test.*\ngit add src\u002Fcomponents\u002F*\n\n# Interactive staging\ngit add -p\n```\n\n**Never commit secrets** (.env, credentials.json, private keys).\n\n### 3. Generate Commit Message\n\nAnalyze the diff to determine:\n\n- **Type**: What kind of change is this?\n- **Scope**: What area\u002Fmodule is affected?\n- **Description**: One-line summary of what changed (present tense, imperative mood, \u003C72 chars)\n\n### 4. Execute Commit\n\n```bash\n# Single line\ngit commit -m \"\u003Ctype>[scope]: \u003Cdescription>\"\n\n# Multi-line with body\u002Ffooter\ngit commit -m \"$(cat \u003C\u003C'EOF'\n\u003Ctype>[scope]: \u003Cdescription>\n\n\u003Coptional body>\n\n\u003Coptional footer>\nEOF\n)\"\n```\n\n## Best Practices\n\n- One logical change per commit\n- Present tense: \"add\" not \"added\"\n- Imperative mood: \"fix bug\" not \"fixes bug\"\n- Reference issues: `Closes #123`, `Refs #456`\n- Keep description under 72 characters\n\n## Git Safety Protocol\n\n- NEVER update git config\n- NEVER run destructive commands (--force, hard reset) without explicit request\n- NEVER skip hooks (--no-verify) unless user asks\n- NEVER force push to main\u002Fmaster\n- If commit fails due to hooks, fix and create NEW commit (don't amend)\n",{"name":5,"license":15,"description":7,"allowed-tools":24},"Bash","main","0415d8a054bffdd2ac7e81ff7a265adf9c191a7f",".kiro\u002Fskills\u002Fgit-commit","https:\u002F\u002Fgithub.com\u002FMesitaDeNoche\u002Ftreasure-szsdevelopers","https:\u002F\u002Fgithub.com\u002FMesitaDeNoche","2026-10-17 21:08:43",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add MesitaDeNoche\u002Ftreasure-szsdevelopers --skill git-commit",{"tool":37,"command":38},"bunx","bunx skills add MesitaDeNoche\u002Ftreasure-szsdevelopers --skill git-commit",{"tool":40,"command":41},"pnpm","pnpm dlx skills add MesitaDeNoche\u002Ftreasure-szsdevelopers --skill git-commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMesitaDeNoche\u002Ftreasure-szsdevelopers\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fgit-commit\u002FSKILL.md",true,[],[46,55,62,69,77,86],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":50,"licenseFileUrl":51,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7F207ZT51PJ123DVW1P5YJG","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FMesitaDeNoche\u002Ftreasure-szsdevelopers\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMesitaDeNoche\u002Ftreasure-szsdevelopers\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7F1ZRQ052XQPW0QB3JVH6RP","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FMesitaDeNoche\u002Ftreasure-szsdevelopers\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7F1ZHXA6EE24B0NYQEF54YR","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002FMesitaDeNoche\u002Ftreasure-szsdevelopers\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fvercel-composition-patterns\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":50,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7F1Z0RTPJ7H3ZA34R8Q6R6Q","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002FMesitaDeNoche\u002Ftreasure-szsdevelopers\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMesitaDeNoche\u002Ftreasure-szsdevelopers\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7F1YDN83T634ZM15XXPKPFR","security-review","Security code review for vulnerabilities. Use when asked to \"security review\", \"find vulnerabilities\", \"check for security issues\", \"audit security\", \"OWASP review\", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.","CC-BY-SA-4.0","https:\u002F\u002Fgithub.com\u002FMesitaDeNoche\u002Ftreasure-szsdevelopers\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fsecurity-review\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FMesitaDeNoche\u002Ftreasure-szsdevelopers\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[],{"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":19},"01M7F1Y1PZH176PE60CDZ675FE","resend","Use when working with the Resend email API — sending transactional emails (single or batch), receiving inbound emails via webhooks, managing email templates, tracking delivery events, managing domains, contacts, broadcasts, webhooks, API keys, automations, events, viewing API request logs, checking account usage and quotas, or setting up the Resend SDK. Always use this skill when the user mentions Resend, even for simple tasks like \"send an email with Resend\" — the skill contains critical gotchas (idempotency keys, webhook verification, template variable syntax) that prevent common production issues.","https:\u002F\u002Fgithub.com\u002FMesitaDeNoche\u002Ftreasure-szsdevelopers\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fresend\u002FSKILL.md",[],[]]