[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77MK34NHNPCGS9EKX7ZXEFW":3,"skill-same:01M77MK34NHNPCGS9EKX7ZXEFW":52},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77MK34NHNPCGS9EKX7ZXEFW","gitmoji",null,"Generates commit messages following the gitmoji convention (https:\u002F\u002Fgitmoji.dev) — picks the right emoji for the intent of the change and writes a well-formed message. Use when asked to \"write a gitmoji commit\", \"add an emoji to my commit message\", \"which gitmoji should I use\", \"gitmoji this change\", or when a project uses gitmoji-style commit messages. Works from a git diff, staged changes, or a plain description of the change. Generates the message only — does not run git commands.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgitmoji\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gitmoji\ndescription: 'Generates commit messages following the gitmoji convention (https:\u002F\u002Fgitmoji.dev) — picks the right emoji for the intent of the change and writes a well-formed message. Use when asked to \"write a gitmoji commit\", \"add an emoji to my commit message\", \"which gitmoji should I use\", \"gitmoji this change\", or when a project uses gitmoji-style commit messages. Works from a git diff, staged changes, or a plain description of the change. Generates the message only — does not run git commands.'\nlicense: MIT\n---\n\n# Gitmoji\n\nGenerates commit messages that follow the [gitmoji](https:\u002F\u002Fgitmoji.dev\u002F) convention: every commit starts with an emoji that identifies the intent of the change at a glance. Given a diff, a list of staged files, or a plain description of a change, this skill picks the single most appropriate gitmoji and writes a concise, well-formed commit message around it.\n\nThis skill **only generates the message** — it never runs `git commit` or any other git command. The output is a copyable message for the user to use.\n\n## When to Use This Skill\n\n- User says \"write a gitmoji commit\", \"gitmoji this change\", or \"add an emoji to my commit message\"\n- User asks \"which gitmoji should I use for this?\"\n- User pastes a git diff or describes a change in a project that uses gitmoji-style commit history\n- User wants an expressive, scannable commit history using emojis\n\n**When not to use:** if the project follows plain [Conventional Commits](https:\u002F\u002Fwww.conventionalcommits.org\u002F) (`feat:`, `fix:`, ...) without emojis, use the `conventional-commit` or `commit-message-storyteller` skill instead. If unsure which convention the project uses, ask the user to provide recent commit history (for example, the output of `git log --oneline -10`).\n\n## Message Format\n\nThe gitmoji specification:\n\n```\n\u003Cintention> [scope?][:?] \u003Cmessage>\n```\n\n- **intention** — exactly one gitmoji expressing the goal of the commit\n- **scope** *(optional)* — the section of the codebase affected, in parentheses\n- **message** — a brief imperative explanation of the change\n\nExamples:\n\n```\n✨ add multi-tenant support to the billing service\n🐛 (auth) prevent token refresh loop on expired sessions\n♻️ (api): extract pagination logic into shared helper\n```\n\n### Emoji Style: Unicode vs Shortcode\n\nGitmoji supports two equivalent notations:\n\n| Style | Example | When to prefer |\n|-------|---------|----------------|\n| Unicode | `✨ add dark mode` | Default — renders everywhere, shorter subject line |\n| Shortcode | `:sparkles: add dark mode` | Platforms that render shortcodes (GitHub, GitLab) or teams that grep commit logs by code |\n\n**Match the repository's existing history.** If recent commits use `:sparkles:`-style shortcodes, generate shortcodes; otherwise default to unicode emojis.\n\n## How It Works\n\n### Step 1: Understand the Change\n\nWork from whatever the user provides:\n\n1. **A git diff** — read it and identify what changed and why\n2. **A list of staged\u002Fmodified files** — infer intent from file names and paths\n3. **A plain description** — use it directly\n\nIf the intent is genuinely ambiguous (e.g. \"updated auth.js\" could be a fix, a feature, or a refactor), ask one short clarifying question rather than guessing.\n\n### Step 2: Identify the Dominant Intent\n\nDetermine the primary purpose of the change. Common intents and their gitmojis:\n\n| Emoji | Shortcode | Intent |\n|-------|-----------|--------|\n| ✨ | `:sparkles:` | Introduce new features |\n| 🐛 | `:bug:` | Fix a bug |\n| 🚑️ | `:ambulance:` | Critical hotfix |\n| 📝 | `:memo:` | Add or update documentation |\n| ♻️ | `:recycle:` | Refactor code (no behavior change) |\n| ✅ | `:white_check_mark:` | Add, update, or pass tests |\n| ⚡️ | `:zap:` | Improve performance |\n| 🎨 | `:art:` | Improve structure \u002F format of the code |\n| 🔥 | `:fire:` | Remove code or files |\n| 🔒️ | `:lock:` | Fix security or privacy issues |\n| ⬆️ | `:arrow_up:` | Upgrade dependencies |\n| 🔧 | `:wrench:` | Add or update configuration files |\n| 💄 | `:lipstick:` | Add or update the UI and style files |\n| 💥 | `:boom:` | Introduce breaking changes |\n| 🚨 | `:rotating_light:` | Fix compiler \u002F linter warnings |\n| 🌐 | `:globe_with_meridians:` | Internationalization and localization |\n\nThis is only the most common subset — **always consult [`references\u002Fgitmoji-reference.md`](references\u002Fgitmoji-reference.md) for the full official list of 75 gitmojis** before settling on one; a more specific emoji often exists (e.g. 🩹 for a trivial fix, ✏️ for a typo, 🚚 for a file move).\n\n### Step 3: Pick Exactly One Emoji\n\nRules for ambiguous cases:\n\n- **Specific beats generic** — a typo fix is ✏️, not 🐛; moving files is 🚚, not ♻️; a trivial non-critical fix is 🩹, not 🐛\n- **Tests:** ✅ for adding\u002Fupdating passing tests; 🧪 only for intentionally failing tests (e.g. TDD red step)\n- **Fix vs hotfix:** 🚑️ only for urgent production fixes; everyday bug fixes are 🐛\n- **Security fix:** 🔒️ wins over 🐛 when the bug is a security issue\n- **Formatting-only changes:** 🎨 for code structure\u002Fformatting; 💄 only for UI\u002Fstyle files (CSS, themes)\n- **One emoji per commit** — never stack emojis; if two intents feel equally dominant, see mixed changes below\n\n### Step 4: Write the Message\n\n- Imperative mood: \"add\", \"fix\", \"remove\" — not \"added\" or \"fixes\"\n- Keep the subject line under 72 characters including the emoji\n- Lowercase start, no trailing period\n- Add a scope in parentheses when the project's history uses scopes\n- Add a body (separated by a blank line) only when the *why* is not obvious from the subject\n\n### Step 5: Output\n\nProduce the commit message in a copyable code block, followed by one line explaining why that gitmoji was chosen. Do **not** execute `git commit`.\n\n**Example output:**\n\n```\n🐛 (auth) prevent token refresh loop on expired sessions\n\nExpired sessions triggered a refresh that failed validation and\nre-triggered itself, crashing the app. A recursion guard now aborts\nthe cycle and returns a clean 401.\n```\n\n> **Why 🐛:** the change corrects incorrect runtime behavior — a bug fix, not urgent enough for 🚑️.\n\n## Edge Cases\n\n| Situation | How to Handle |\n|-----------|---------------|\n| Mixed changes (e.g. feature + refactor in one diff) | Pick the emoji for the *dominant* intent, and suggest splitting into separate commits if the concerns are unrelated |\n| Breaking change | Use 💥 as the intention and describe the break in the body |\n| Revert | ⏪️ with a subject referencing the reverted commit |\n| Merge commit | 🔀 `merge branch '\u003Cname>' into \u003Ctarget>` |\n| Initial commit | 🎉 `begin project` |\n| Work in progress | 🚧 with a clear note of what remains |\n| No matching emoji feels right | Re-scan the [full reference](references\u002Fgitmoji-reference.md); if still nothing fits, fall back to the closest generic intent (✨, 🐛, or ♻️) |\n\n## Quick Reference\n\n```bash\n# Get your staged diff to paste into Copilot\ngit diff --staged\n\n# Check which emoji style the repo already uses\ngit log --oneline -10\n```\n\nSee [`references\u002Fgitmoji-reference.md`](references\u002Fgitmoji-reference.md) for the complete official gitmoji list.\n","# Gitmoji\n\nGenerates commit messages that follow the [gitmoji](https:\u002F\u002Fgitmoji.dev\u002F) convention: every commit starts with an emoji that identifies the intent of the change at a glance. Given a diff, a list of staged files, or a plain description of a change, this skill picks the single most appropriate gitmoji and writes a concise, well-formed commit message around it.\n\nThis skill **only generates the message** — it never runs `git commit` or any other git command. The output is a copyable message for the user to use.\n\n## When to Use This Skill\n\n- User says \"write a gitmoji commit\", \"gitmoji this change\", or \"add an emoji to my commit message\"\n- User asks \"which gitmoji should I use for this?\"\n- User pastes a git diff or describes a change in a project that uses gitmoji-style commit history\n- User wants an expressive, scannable commit history using emojis\n\n**When not to use:** if the project follows plain [Conventional Commits](https:\u002F\u002Fwww.conventionalcommits.org\u002F) (`feat:`, `fix:`, ...) without emojis, use the `conventional-commit` or `commit-message-storyteller` skill instead. If unsure which convention the project uses, ask the user to provide recent commit history (for example, the output of `git log --oneline -10`).\n\n## Message Format\n\nThe gitmoji specification:\n\n```\n\u003Cintention> [scope?][:?] \u003Cmessage>\n```\n\n- **intention** — exactly one gitmoji expressing the goal of the commit\n- **scope** *(optional)* — the section of the codebase affected, in parentheses\n- **message** — a brief imperative explanation of the change\n\nExamples:\n\n```\n✨ add multi-tenant support to the billing service\n🐛 (auth) prevent token refresh loop on expired sessions\n♻️ (api): extract pagination logic into shared helper\n```\n\n### Emoji Style: Unicode vs Shortcode\n\nGitmoji supports two equivalent notations:\n\n| Style | Example | When to prefer |\n|-------|---------|----------------|\n| Unicode | `✨ add dark mode` | Default — renders everywhere, shorter subject line |\n| Shortcode | `:sparkles: add dark mode` | Platforms that render shortcodes (GitHub, GitLab) or teams that grep commit logs by code |\n\n**Match the repository's existing history.** If recent commits use `:sparkles:`-style shortcodes, generate shortcodes; otherwise default to unicode emojis.\n\n## How It Works\n\n### Step 1: Understand the Change\n\nWork from whatever the user provides:\n\n1. **A git diff** — read it and identify what changed and why\n2. **A list of staged\u002Fmodified files** — infer intent from file names and paths\n3. **A plain description** — use it directly\n\nIf the intent is genuinely ambiguous (e.g. \"updated auth.js\" could be a fix, a feature, or a refactor), ask one short clarifying question rather than guessing.\n\n### Step 2: Identify the Dominant Intent\n\nDetermine the primary purpose of the change. Common intents and their gitmojis:\n\n| Emoji | Shortcode | Intent |\n|-------|-----------|--------|\n| ✨ | `:sparkles:` | Introduce new features |\n| 🐛 | `:bug:` | Fix a bug |\n| 🚑️ | `:ambulance:` | Critical hotfix |\n| 📝 | `:memo:` | Add or update documentation |\n| ♻️ | `:recycle:` | Refactor code (no behavior change) |\n| ✅ | `:white_check_mark:` | Add, update, or pass tests |\n| ⚡️ | `:zap:` | Improve performance |\n| 🎨 | `:art:` | Improve structure \u002F format of the code |\n| 🔥 | `:fire:` | Remove code or files |\n| 🔒️ | `:lock:` | Fix security or privacy issues |\n| ⬆️ | `:arrow_up:` | Upgrade dependencies |\n| 🔧 | `:wrench:` | Add or update configuration files |\n| 💄 | `:lipstick:` | Add or update the UI and style files |\n| 💥 | `:boom:` | Introduce breaking changes |\n| 🚨 | `:rotating_light:` | Fix compiler \u002F linter warnings |\n| 🌐 | `:globe_with_meridians:` | Internationalization and localization |\n\nThis is only the most common subset — **always consult [`references\u002Fgitmoji-reference.md`](references\u002Fgitmoji-reference.md) for the full official list of 75 gitmojis** before settling on one; a more specific emoji often exists (e.g. 🩹 for a trivial fix, ✏️ for a typo, 🚚 for a file move).\n\n### Step 3: Pick Exactly One Emoji\n\nRules for ambiguous cases:\n\n- **Specific beats generic** — a typo fix is ✏️, not 🐛; moving files is 🚚, not ♻️; a trivial non-critical fix is 🩹, not 🐛\n- **Tests:** ✅ for adding\u002Fupdating passing tests; 🧪 only for intentionally failing tests (e.g. TDD red step)\n- **Fix vs hotfix:** 🚑️ only for urgent production fixes; everyday bug fixes are 🐛\n- **Security fix:** 🔒️ wins over 🐛 when the bug is a security issue\n- **Formatting-only changes:** 🎨 for code structure\u002Fformatting; 💄 only for UI\u002Fstyle files (CSS, themes)\n- **One emoji per commit** — never stack emojis; if two intents feel equally dominant, see mixed changes below\n\n### Step 4: Write the Message\n\n- Imperative mood: \"add\", \"fix\", \"remove\" — not \"added\" or \"fixes\"\n- Keep the subject line under 72 characters including the emoji\n- Lowercase start, no trailing period\n- Add a scope in parentheses when the project's history uses scopes\n- Add a body (separated by a blank line) only when the *why* is not obvious from the subject\n\n### Step 5: Output\n\nProduce the commit message in a copyable code block, followed by one line explaining why that gitmoji was chosen. Do **not** execute `git commit`.\n\n**Example output:**\n\n```\n🐛 (auth) prevent token refresh loop on expired sessions\n\nExpired sessions triggered a refresh that failed validation and\nre-triggered itself, crashing the app. A recursion guard now aborts\nthe cycle and returns a clean 401.\n```\n\n> **Why 🐛:** the change corrects incorrect runtime behavior — a bug fix, not urgent enough for 🚑️.\n\n## Edge Cases\n\n| Situation | How to Handle |\n|-----------|---------------|\n| Mixed changes (e.g. feature + refactor in one diff) | Pick the emoji for the *dominant* intent, and suggest splitting into separate commits if the concerns are unrelated |\n| Breaking change | Use 💥 as the intention and describe the break in the body |\n| Revert | ⏪️ with a subject referencing the reverted commit |\n| Merge commit | 🔀 `merge branch '\u003Cname>' into \u003Ctarget>` |\n| Initial commit | 🎉 `begin project` |\n| Work in progress | 🚧 with a clear note of what remains |\n| No matching emoji feels right | Re-scan the [full reference](references\u002Fgitmoji-reference.md); if still nothing fits, fall back to the closest generic intent (✨, 🐛, or ♻️) |\n\n## Quick Reference\n\n```bash\n# Get your staged diff to paste into Copilot\ngit diff --staged\n\n# Check which emoji style the repo already uses\ngit log --oneline -10\n```\n\nSee [`references\u002Fgitmoji-reference.md`](references\u002Fgitmoji-reference.md) for the complete official gitmoji list.\n",{"name":5,"license":15,"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92",".agents\u002Fskills\u002Fgitmoji",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill gitmoji",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill gitmoji",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill gitmoji","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgitmoji\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fgitmoji-reference.md","REFERENCE","参考文档",4693,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgitmoji\u002Freferences\u002Fgitmoji-reference.md",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]