[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MP2YNPAE38FNR7TSM3T5B1":3,"skill-same:01M6MP2YNPAE38FNR7TSM3T5B1":73},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6MP2YNPAE38FNR7TSM3T5B1","commit",null,"Generate a Conventional Commits message, commit, and optionally push to remote.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1566,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyagizdo\u002Fquiver\u002Fskills\u002Fcommit\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"auto","changes","my","remote","make","prompting","message","conventional commits","commit changes","user","write","commits","push","commit message","git","generate","git commit","2026-11-10 10:12:30",false,"---\nname: commit\ndescription: Generate a Conventional Commits message, commit, and optionally push to remote.\nargument-hint: \"[--push] (auto commit & push without prompting)\"\nwhen-to-use: \"user wants to commit changes or write a commit message -- '\u002Fcommit', 'commit this', 'make a commit', 'git commit', 'commit my changes'\"\n---\n\n# Gather Git Context\n\n```\n!`git rev-parse --is-inside-work-tree 2>\u002Fdev\u002Fnull || echo \"NO_GIT\"`\n```\n\n```\n!`git status --short 2>\u002Fdev\u002Fnull || echo \"NO_GIT\"`\n```\n\n```\n!`git diff --cached 2>\u002Fdev\u002Fnull || echo \"NO_GIT\"`\n```\n\n```\n!`git log --oneline -10 2>\u002Fdev\u002Fnull || echo \"NO_COMMITS\"`\n```\n\n---\n\n# Instructions\n\n## Step 0 -- Git Availability\n\nIf any gather-context block above returned `NO_GIT`, this directory is not a git repository.\nPrint: `> No git repository detected. \u002Fcommit requires a git repo.`\n**Stop here.**\n\n---\n\nSilently determine which case applies — do not show the case label or decision logic to the user:\n\n- **No changes:** If `git status` is empty → tell the user and stop.\n- **Nothing staged:** If `git diff --cached` is empty but `git status` shows changes → tell the user to stage files and run `\u002Fquiver:commit` again, then stop.\n- **Staged changes exist:** Proceed silently to Commit Message Generation.\n\n---\n\n# Commit Message Generation\n\nAnalyze `git diff --cached` and the recent log. Generate a Conventional Commits message following these rules:\n\n**Type** — Select one based on primary intent:\n\n| Type | When to Use |\n|------|-------------|\n| `feat` | New feature or capability visible to users |\n| `fix` | Bug fix |\n| `docs` | Documentation only (README, comments, JSDoc) |\n| `style` | Formatting, whitespace, semicolons — no logic change |\n| `refactor` | Code restructuring with no behavior change |\n| `perf` | Performance improvement |\n| `test` | Adding or fixing tests |\n| `build` | Build system or external dependencies (npm, Makefile) |\n| `ci` | CI\u002FCD configuration (GitHub Actions, CircleCI) |\n| `chore` | Maintenance tasks (version bumps, tooling config) |\n| `revert` | Reverting a previous commit |\n\n**Scope** — From file paths: single directory → its name, single file → domain name, cross-cutting → omit.\n\n**Breaking changes** — If the change removes\u002Frenames public APIs, changes signatures, alters data formats, or removes CLI flags\u002Fcommands, add `!` after type\u002Fscope and a `BREAKING CHANGE:` footer.\n\n**Subject line** — Imperative mood, lowercase after colon, no period, ≤72 chars total, describe *what* not *how*.\n\n**Body** — Almost never. Only for breaking changes or when the subject alone would be misleading. Wrap at 72 chars. Never include file lists — `git log --stat` shows this.\n\n**Footers** — `BREAKING CHANGE:` if applicable. `Refs: #issue` if relevant.\n\nInclude a body or footers only for breaking changes or multi-type changes where the subject alone is genuinely ambiguous. Default to subject-only. Don't add `Co-authored-by` or attribution footers unless explicitly requested.\n\n---\n\n# Output\n\n**Important:** The user must see the full commit message before answering the prompt. Print it to the chat stream and keep the `AskUserQuestion` question itself to one short line -- see **Default (no flag)** below.\n\n## Flag: `--push`\n\nIf `$ARGUMENTS` contains \"push\" (e.g., `\u002Fquiver:commit --push`), skip the `AskUserQuestion` step entirely. Instead, show the generated commit message, then immediately execute **Commit & Push** (commit + push to remote) without prompting.\n\n## Default (no flag)\n\nTwo steps, both mandatory: print the message, then ask. Do not paste the commit message into the `AskUserQuestion` question field -- that field is rendered as a single truncated line by some Claude Code surfaces, so a multi-line message is cut off or dropped entirely and the user is asked to approve something they cannot read.\n\n**Step 1 -- print the message** as normal chat output, verbatim inside a fenced block, so the user sees exactly what `git commit` will receive:\n\n```\n{type}({scope}): {subject}\n\n{body lines, if the message has a body}\n```\n\n**Step 2 -- ask, and wait for the answer:**\n\n- **Question:** `\"Commit this?\"` -- one short line. No newlines, no message text, no ANSI escape codes. `AskUserQuestion` renders the question in a TUI box that prints escape sequences literally instead of styling them.\n- **Header:** \"Action\"\n- **Options:**\n  1. **Commit** — \"Commit with this message\"\n  2. **Commit & Push** — \"Commit and push to remote\"\n  3. **Edit** — \"Revise the message\"\n  4. **Cancel** — \"Abort without committing\"\n\nPrinting the message is not approval. It is only the readable copy of what the prompt is about, and it exists because the prompt cannot display it. Never run `git commit` without an answer from this `AskUserQuestion`. The user asking for a commit in their message is not the answer either -- that is what put the skill on this step. `--push` is the only path that skips the prompt.\n\n---\n\n# Commit Execution\n\n**On commit or commit & push:**\n\n1. Commit using a HEREDOC:\n   ```\n   git commit -m \"$(cat \u003C\u003C'EOF'\n   {full commit message}\n   EOF\n   )\"\n   ```\n2. Verify: `git log --oneline -1` and `git status --short`.\n\n**If commit & push**, also:\n\n3. Detect branch: `git branch --show-current`\n4. Push: if `git rev-parse --abbrev-ref @{upstream} 2>\u002Fdev\u002Fnull` succeeds → `git push`, otherwise → `git push -u origin {branch}`\n5. Verify push exit code is 0.\n\n**Output:**\n\n> **Committed:** `{short hash}` {subject}\n> **Branch:** `{branch name}`\n> **Pushed to:** `origin\u002F{branch}` *(only if pushed)*\n\n**On edit:** Ask what to change, revise, re-present, and ask again.\n\n**On cancel:**\n\n> **Commit cancelled.** Staged changes are intact.\n\n**Stop here.**\n\n---\n\n# Error Handling\n\nIf `git commit` fails, show the error verbatim and suggest the user fix the issue and re-run `\u002Fquiver:commit`. Never retry automatically or use `--no-verify`.\n","# Gather Git Context\n\n```\n!`git rev-parse --is-inside-work-tree 2>\u002Fdev\u002Fnull || echo \"NO_GIT\"`\n```\n\n```\n!`git status --short 2>\u002Fdev\u002Fnull || echo \"NO_GIT\"`\n```\n\n```\n!`git diff --cached 2>\u002Fdev\u002Fnull || echo \"NO_GIT\"`\n```\n\n```\n!`git log --oneline -10 2>\u002Fdev\u002Fnull || echo \"NO_COMMITS\"`\n```\n\n---\n\n# Instructions\n\n## Step 0 -- Git Availability\n\nIf any gather-context block above returned `NO_GIT`, this directory is not a git repository.\nPrint: `> No git repository detected. \u002Fcommit requires a git repo.`\n**Stop here.**\n\n---\n\nSilently determine which case applies — do not show the case label or decision logic to the user:\n\n- **No changes:** If `git status` is empty → tell the user and stop.\n- **Nothing staged:** If `git diff --cached` is empty but `git status` shows changes → tell the user to stage files and run `\u002Fquiver:commit` again, then stop.\n- **Staged changes exist:** Proceed silently to Commit Message Generation.\n\n---\n\n# Commit Message Generation\n\nAnalyze `git diff --cached` and the recent log. Generate a Conventional Commits message following these rules:\n\n**Type** — Select one based on primary intent:\n\n| Type | When to Use |\n|------|-------------|\n| `feat` | New feature or capability visible to users |\n| `fix` | Bug fix |\n| `docs` | Documentation only (README, comments, JSDoc) |\n| `style` | Formatting, whitespace, semicolons — no logic change |\n| `refactor` | Code restructuring with no behavior change |\n| `perf` | Performance improvement |\n| `test` | Adding or fixing tests |\n| `build` | Build system or external dependencies (npm, Makefile) |\n| `ci` | CI\u002FCD configuration (GitHub Actions, CircleCI) |\n| `chore` | Maintenance tasks (version bumps, tooling config) |\n| `revert` | Reverting a previous commit |\n\n**Scope** — From file paths: single directory → its name, single file → domain name, cross-cutting → omit.\n\n**Breaking changes** — If the change removes\u002Frenames public APIs, changes signatures, alters data formats, or removes CLI flags\u002Fcommands, add `!` after type\u002Fscope and a `BREAKING CHANGE:` footer.\n\n**Subject line** — Imperative mood, lowercase after colon, no period, ≤72 chars total, describe *what* not *how*.\n\n**Body** — Almost never. Only for breaking changes or when the subject alone would be misleading. Wrap at 72 chars. Never include file lists — `git log --stat` shows this.\n\n**Footers** — `BREAKING CHANGE:` if applicable. `Refs: #issue` if relevant.\n\nInclude a body or footers only for breaking changes or multi-type changes where the subject alone is genuinely ambiguous. Default to subject-only. Don't add `Co-authored-by` or attribution footers unless explicitly requested.\n\n---\n\n# Output\n\n**Important:** The user must see the full commit message before answering the prompt. Print it to the chat stream and keep the `AskUserQuestion` question itself to one short line -- see **Default (no flag)** below.\n\n## Flag: `--push`\n\nIf `$ARGUMENTS` contains \"push\" (e.g., `\u002Fquiver:commit --push`), skip the `AskUserQuestion` step entirely. Instead, show the generated commit message, then immediately execute **Commit & Push** (commit + push to remote) without prompting.\n\n## Default (no flag)\n\nTwo steps, both mandatory: print the message, then ask. Do not paste the commit message into the `AskUserQuestion` question field -- that field is rendered as a single truncated line by some Claude Code surfaces, so a multi-line message is cut off or dropped entirely and the user is asked to approve something they cannot read.\n\n**Step 1 -- print the message** as normal chat output, verbatim inside a fenced block, so the user sees exactly what `git commit` will receive:\n\n```\n{type}({scope}): {subject}\n\n{body lines, if the message has a body}\n```\n\n**Step 2 -- ask, and wait for the answer:**\n\n- **Question:** `\"Commit this?\"` -- one short line. No newlines, no message text, no ANSI escape codes. `AskUserQuestion` renders the question in a TUI box that prints escape sequences literally instead of styling them.\n- **Header:** \"Action\"\n- **Options:**\n  1. **Commit** — \"Commit with this message\"\n  2. **Commit & Push** — \"Commit and push to remote\"\n  3. **Edit** — \"Revise the message\"\n  4. **Cancel** — \"Abort without committing\"\n\nPrinting the message is not approval. It is only the readable copy of what the prompt is about, and it exists because the prompt cannot display it. Never run `git commit` without an answer from this `AskUserQuestion`. The user asking for a commit in their message is not the answer either -- that is what put the skill on this step. `--push` is the only path that skips the prompt.\n\n---\n\n# Commit Execution\n\n**On commit or commit & push:**\n\n1. Commit using a HEREDOC:\n   ```\n   git commit -m \"$(cat \u003C\u003C'EOF'\n   {full commit message}\n   EOF\n   )\"\n   ```\n2. Verify: `git log --oneline -1` and `git status --short`.\n\n**If commit & push**, also:\n\n3. Detect branch: `git branch --show-current`\n4. Push: if `git rev-parse --abbrev-ref @{upstream} 2>\u002Fdev\u002Fnull` succeeds → `git push`, otherwise → `git push -u origin {branch}`\n5. Verify push exit code is 0.\n\n**Output:**\n\n> **Committed:** `{short hash}` {subject}\n> **Branch:** `{branch name}`\n> **Pushed to:** `origin\u002F{branch}` *(only if pushed)*\n\n**On edit:** Ask what to change, revise, re-present, and ask again.\n\n**On cancel:**\n\n> **Commit cancelled.** Staged changes are intact.\n\n**Stop here.**\n\n---\n\n# Error Handling\n\nIf `git commit` fails, show the error verbatim and suggest the user fix the issue and re-run `\u002Fquiver:commit`. Never retry automatically or use `--no-verify`.\n",{"name":5,"description":7,"when-to-use":41,"argument-hint":42},"user wants to commit changes or write a commit message -- '\u002Fcommit', 'commit this', 'make a commit', 'git commit', 'commit my changes'","[--push] (auto commit & push without prompting)","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fyagizdo\u002Fquiver\u002Fskills\u002Fcommit",483,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-13 02:16:32",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill commit",{"tool":59,"command":60},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill commit",{"tool":62,"command":63},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyagizdo\u002Fquiver\u002Fskills\u002Fcommit\u002FSKILL.md",true,[67],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"TEST-PLAN.md","REFERENCE","参考文档",2446,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyagizdo\u002Fquiver\u002Fskills\u002Fcommit\u002FTEST-PLAN.md",[74,82,89,96,123,148],{"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":81},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":81},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":81},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":36},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","when","you","done","reviewer","io","change","cli","merge","past",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":36},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[130,131,132,118,133,134,135,136,137,138,139,140,141,142,108,143,144,145,146,147],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":165,"publishedAt":36},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[154,159,162],{"categoryNo":155,"categoryName":156,"taxonomyType":157,"taxonomyTypeDesc":158},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":160,"categoryName":161,"taxonomyType":157,"taxonomyTypeDesc":158},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":163,"categoryName":164,"taxonomyType":157,"taxonomyTypeDesc":158},"01JBSEEDCAT000000000000010","后端与接口",[150,166,167,168,169,170,171,144,172,109,173,174,175,176,114,177,178,179,180,181],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]