[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77Q09QDYGADWN0WM924X6PJ":3,"skill-same:01M77Q09QDYGADWN0WM924X6PJ":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},"01M77Q09QDYGADWN0WM924X6PJ","commit-message-storyteller",null,"Analyzes git diffs or staged changes and generates narrative commit messages that explain WHY a change was made, not just what changed — following Conventional Commits format. Use when asked to \"write a commit message\", \"generate a commit\", \"describe my changes\", \"what should I commit this as\", \"commit this\", \"summarize my diff\", or \"help me commit\". Works with git diff output, staged files, or plain descriptions of changes.","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\u002Fagent\u002Fskills\u002Fcommit-message-storyteller\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Analyzes git diffs or staged changes and generates narrative commit messages that explain WHY a change was made, not just what changed — following Conventional Commits format. Use when asked to \\\"write a commit message\\\", \\\"generate a commit\\\", \\\"describe my changes\\\", \\\"what should I commit this as\\\", \\\"commit this\\\", \\\"summarize my diff\\\", or \\\"help me commit\\\". Works with git diff output, staged files, or plain descriptions of changes.\"\n---\n# Commit Message Storyteller\n\nTransforms raw git diffs and change descriptions into clear, story-driven commit messages that follow the [Conventional Commits](https:\u002F\u002Fwww.conventionalcommits.org\u002F) specification. Instead of \"update file.js\", you get messages that communicate intent, context, and impact.\n\n## When to Use This Skill\n\n- User says \"write a commit message\", \"help me commit\", or \"generate a commit\"\n- User pastes a git diff or describes code changes\n- User says \"what should I commit this as?\" or \"summarize my diff\"\n- User wants better commit history for their team or open-source project\n- User is preparing a pull request and wants meaningful commit messages\n\n## Prerequisites\n\nHave at least one of the following ready:\n- Output from `git diff` or `git diff --staged`\n- A description of what you changed and why\n- A list of modified files\n\n## How It Works\n\n### Step 1: Gather the Change Context\n\nAsk the user (or infer from the diff) for:\n\n1. **What changed** — files, functions, logic affected\n2. **Why it changed** — bug fix, new feature, refactor, performance, etc.\n3. **Who\u002Fwhat triggered it** — issue number, user request, tech debt, etc.\n\nIf the user provides a raw `git diff`, extract this context automatically from the diff.\n\n### Step 2: Identify the Commit Type\n\nMap the change to a Conventional Commits type using this guide:\n\n| Type | Use When |\n|------|----------|\n| `feat` | A new feature or capability is added |\n| `fix` | A bug or incorrect behavior is corrected |\n| `refactor` | Code restructured without changing behavior |\n| `perf` | A change that improves performance |\n| `docs` | Documentation only changes |\n| `style` | Formatting, whitespace, missing semicolons (no logic change) |\n| `test` | Adding or updating tests |\n| `chore` | Build process, dependency updates, config changes |\n| `ci` | CI\u002FCD pipeline changes |\n| `revert` | Reverting a previous commit |\n\nSee `references\u002Fconventional-commits-guide.md` for detailed examples.\n\n### Step 3: Write the Commit Message\n\nFollow this structure:\n\n```\n\u003Ctype>(\u003Coptional scope>): \u003Cshort imperative summary>\n\n\u003Cbody — the story: why this change was made, what problem it solves>\n\n\u003Cfooter — issue refs, breaking change notices>\n```\n\n#### Rules for Each Part\n\n**Subject line (first line):**\n- Use imperative mood: \"add\", \"fix\", \"remove\" — not \"added\" or \"fixes\"\n- Max 72 characters\n- No period at the end\n- Lowercase after the colon\n\n**Body (the story):**\n- Explain the *why*, not the *what* (the diff already shows the what)\n- Describe the problem that existed before this change\n- Mention any alternatives considered if relevant\n- Keep lines under 100 characters\n- Separate from subject with a blank line\n\n**Footer:**\n- Reference issues: `Closes #123`, `Fixes #456`, `Refs #789`\n- Mark breaking changes: `BREAKING CHANGE: \u003Cdescription>`\n\n### Step 4: Generate Output\n\nProduce the commit message in a copyable code block, followed by a one-line plain-English explanation of the story you told.\n\n**Example output:**\n\n```\nfix(auth): prevent token refresh loop on expired sessions\n\nWhen a user's session expired mid-request, the auth middleware was\ntriggering a token refresh, which itself failed validation and triggered\nanother refresh — causing an infinite retry loop that crashed the app.\n\nThis adds a recursion guard flag that aborts the refresh cycle if a\nrefresh is already in progress, returning a clean 401 instead.\n\nCloses #312\n```\n\n> **Story told:** A silent infinite loop on session expiry was crashing the app; this stops the cycle early and returns a clean error.\n\n---\n\n## Multiple Commits from One Diff\n\nIf the diff contains **logically separate changes**, split them into multiple commit messages and tell the user. Use this heuristic:\n\n- Different files with unrelated purposes → likely separate commits\n- Same file but distinct concerns (e.g., bug fix + refactor) → suggest splitting\n- Everything tightly coupled → one commit is fine\n\n---\n\n## Edge Cases\n\n| Situation | How to Handle |\n|-----------|---------------|\n| User provides no context beyond a diff | Infer type and scope from file names and changed symbols |\n| Changes span many files with no clear theme | Ask: \"Is this one logical change, or multiple?\" |\n| Breaking change detected | Add `BREAKING CHANGE:` footer automatically |\n| User says \"keep it short\" | Omit body, just write a strong subject line |\n| No issue number available | Omit the footer entirely |\n\n---\n\n## Quick Reference\n\n```bash\n# Get your staged diff to paste into Copilot\ngit diff --staged\n\n# Or get the last uncommitted working tree changes\ngit diff\n```\n\nSee `references\u002Fconventional-commits-guide.md` for type examples and scope guidelines.\n","# Commit Message Storyteller\n\nTransforms raw git diffs and change descriptions into clear, story-driven commit messages that follow the [Conventional Commits](https:\u002F\u002Fwww.conventionalcommits.org\u002F) specification. Instead of \"update file.js\", you get messages that communicate intent, context, and impact.\n\n## When to Use This Skill\n\n- User says \"write a commit message\", \"help me commit\", or \"generate a commit\"\n- User pastes a git diff or describes code changes\n- User says \"what should I commit this as?\" or \"summarize my diff\"\n- User wants better commit history for their team or open-source project\n- User is preparing a pull request and wants meaningful commit messages\n\n## Prerequisites\n\nHave at least one of the following ready:\n- Output from `git diff` or `git diff --staged`\n- A description of what you changed and why\n- A list of modified files\n\n## How It Works\n\n### Step 1: Gather the Change Context\n\nAsk the user (or infer from the diff) for:\n\n1. **What changed** — files, functions, logic affected\n2. **Why it changed** — bug fix, new feature, refactor, performance, etc.\n3. **Who\u002Fwhat triggered it** — issue number, user request, tech debt, etc.\n\nIf the user provides a raw `git diff`, extract this context automatically from the diff.\n\n### Step 2: Identify the Commit Type\n\nMap the change to a Conventional Commits type using this guide:\n\n| Type | Use When |\n|------|----------|\n| `feat` | A new feature or capability is added |\n| `fix` | A bug or incorrect behavior is corrected |\n| `refactor` | Code restructured without changing behavior |\n| `perf` | A change that improves performance |\n| `docs` | Documentation only changes |\n| `style` | Formatting, whitespace, missing semicolons (no logic change) |\n| `test` | Adding or updating tests |\n| `chore` | Build process, dependency updates, config changes |\n| `ci` | CI\u002FCD pipeline changes |\n| `revert` | Reverting a previous commit |\n\nSee `references\u002Fconventional-commits-guide.md` for detailed examples.\n\n### Step 3: Write the Commit Message\n\nFollow this structure:\n\n```\n\u003Ctype>(\u003Coptional scope>): \u003Cshort imperative summary>\n\n\u003Cbody — the story: why this change was made, what problem it solves>\n\n\u003Cfooter — issue refs, breaking change notices>\n```\n\n#### Rules for Each Part\n\n**Subject line (first line):**\n- Use imperative mood: \"add\", \"fix\", \"remove\" — not \"added\" or \"fixes\"\n- Max 72 characters\n- No period at the end\n- Lowercase after the colon\n\n**Body (the story):**\n- Explain the *why*, not the *what* (the diff already shows the what)\n- Describe the problem that existed before this change\n- Mention any alternatives considered if relevant\n- Keep lines under 100 characters\n- Separate from subject with a blank line\n\n**Footer:**\n- Reference issues: `Closes #123`, `Fixes #456`, `Refs #789`\n- Mark breaking changes: `BREAKING CHANGE: \u003Cdescription>`\n\n### Step 4: Generate Output\n\nProduce the commit message in a copyable code block, followed by a one-line plain-English explanation of the story you told.\n\n**Example output:**\n\n```\nfix(auth): prevent token refresh loop on expired sessions\n\nWhen a user's session expired mid-request, the auth middleware was\ntriggering a token refresh, which itself failed validation and triggered\nanother refresh — causing an infinite retry loop that crashed the app.\n\nThis adds a recursion guard flag that aborts the refresh cycle if a\nrefresh is already in progress, returning a clean 401 instead.\n\nCloses #312\n```\n\n> **Story told:** A silent infinite loop on session expiry was crashing the app; this stops the cycle early and returns a clean error.\n\n---\n\n## Multiple Commits from One Diff\n\nIf the diff contains **logically separate changes**, split them into multiple commit messages and tell the user. Use this heuristic:\n\n- Different files with unrelated purposes → likely separate commits\n- Same file but distinct concerns (e.g., bug fix + refactor) → suggest splitting\n- Everything tightly coupled → one commit is fine\n\n---\n\n## Edge Cases\n\n| Situation | How to Handle |\n|-----------|---------------|\n| User provides no context beyond a diff | Infer type and scope from file names and changed symbols |\n| Changes span many files with no clear theme | Ask: \"Is this one logical change, or multiple?\" |\n| Breaking change detected | Add `BREAKING CHANGE:` footer automatically |\n| User says \"keep it short\" | Omit body, just write a strong subject line |\n| No issue number available | Omit the footer entirely |\n\n---\n\n## Quick Reference\n\n```bash\n# Get your staged diff to paste into Copilot\ngit diff --staged\n\n# Or get the last uncommitted working tree changes\ngit diff\n```\n\nSee `references\u002Fconventional-commits-guide.md` for type examples and scope guidelines.\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fcommit-message-storyteller",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 commit-message-storyteller",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill commit-message-storyteller",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill commit-message-storyteller","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fcommit-message-storyteller\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fconventional-commits-guide.md","REFERENCE","参考文档",4061,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fcommit-message-storyteller\u002Freferences\u002Fconventional-commits-guide.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",[],[]]