[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D101B0KRY1VZK95XMJDWVQ":3,"skill-same:01M7D101B0KRY1VZK95XMJDWVQ":47},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":46},"01M7D101B0KRY1VZK95XMJDWVQ","commit",null,"Stage the current changes and create a git commit with a properly formatted English message. Use whenever the user asks to commit, save, or check in their work. Picks a Conventional-Commits-style prefix (fix:, feat:, refactor:, docs:, test:, chore:, style:, perf:) based on the actual diff, keeps the first line a concise summary, and adds a bullet list of details only when the change touches several things.","haru\u002Fredmine_render_switcher","haru","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99401?v=4","01M7D0ZVTHVASR3YEY7WNWZHM4","Haru Iida","01M7D0ZVV4VB9SDVQEAKT4MYZD",4,"MIT","https:\u002F\u002Fgithub.com\u002Fharu\u002Fredmine_render_switcher\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcommit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"commit\"\ndescription: \"Stage the current changes and create a git commit with a properly formatted English message. Use whenever the user asks to commit, save, or check in their work. Picks a Conventional-Commits-style prefix (fix:, feat:, refactor:, docs:, test:, chore:, style:, perf:) based on the actual diff, keeps the first line a concise summary, and adds a bullet list of details only when the change touches several things.\"\nargument-hint: \"Optional: additional context about what changed, or which files to include\"\nuser-invocable: true\ndisable-model-invocation: false\n---\n\n# Commit\n\nStage the outstanding changes and create a single git commit with an English message that follows this project's format.\n\n## User Input\n\n```text\n$ARGUMENTS\n```\n\nConsider any additional context from the user input (e.g. \"only commit the tool changes\", \"this is a bug fix\") before proceeding.\n\n## Procedure\n\n### Step 1: Survey the Changes\n\nRun in parallel:\n- `git status` — see tracked and untracked files\n- `git diff` and `git diff --staged` — see the actual content changes\n- `git log --oneline -10` — match the repository's existing commit message tone\n\n### Step 2: Stage the Changes\n\nStage the modified and new files that belong to this piece of work (`git add \u003Cfiles>`, or `git add -A` when everything in the working tree is part of the same change).\n\nBefore committing, look at the staged file list once more:\n- If anything looks like a secret or credential (`.env`, `*.pem`, `credentials.json`, API keys, etc.), unstage it and warn the user instead of committing it silently.\n- If some staged files clearly belong to unrelated, separate work (not what the user is asking to commit right now), leave them out and mention it to the user.\n\n### Step 3: Determine the Commit Type\n\nLook at the diff and classify the change into a prefix:\n\n| Prefix | When to use |\n|--------|-------------|\n| `fix:` | Bug fix |\n| `feat:` | New feature or capability |\n| `refactor:` | Restructuring without behavior change |\n| `docs:` | Documentation only (README, YARD, locale text) |\n| `test:` | Test-only changes |\n| `chore:` | Tooling, dependencies, config, housekeeping |\n| `style:` | Formatting\u002Fwhitespace only, no logic change |\n| `perf:` | Performance improvement |\n\nIf a change spans multiple categories, pick the one that reflects the primary intent.\n\n### Step 4: Write the Commit Message\n\nFormat:\n- **Line 1**: `\u003Cprefix>: \u003Cconcise summary of the overall change>` — English, imperative mood, no trailing period.\n- **If the change is small** (one focused fix, a single file, a short diff): stop at line 1. No body needed.\n- **If the change touches several things**: leave a blank line after line 1, then a short bullet list (`- ...`), one line per notable change. Keep bullets brief — what changed, not how.\n\nExample (small change):\n```\nfix: correct nil check in issue summary cache lookup\n```\n\nExample (larger change):\n```\nfeat: add vector model profile support to settings\n\n- add use_vector_model_profile and vector_model_profile_id columns\n- update settings UI to select a dedicated vector model profile\n- fall back to the default model profile when unset\n```\n\nDo not add a `Co-Authored-By` line or any other reference to Claude\u002FAI assistance — this project's convention explicitly excludes that from commit messages.\n\n### Step 5: Commit\n\nUse a heredoc so multi-line messages are formatted correctly:\n\n```bash\ngit commit -m \"$(cat \u003C\u003C'EOF'\n\u003Cprefix>: \u003Csummary>\n\n- \u003Cdetail 1>\n- \u003Cdetail 2>\nEOF\n)\"\n```\n\nAlways create a new commit — never `--amend` an existing one unless the user explicitly asks for it.\n\n### Step 6: Confirm\n\nRun `git status` after the commit and report the resulting commit (short hash + first line) to the user. Do not push.\n\n## Notes\n\n- Never push — this skill only commits locally.\n- Never use `--no-verify` to skip hooks.\n- Write commit messages in plain English regardless of the conversation language.\n\n## Error Handling\n\n- If there is nothing staged and nothing to stage (clean working tree), tell the user there is nothing to commit — do not create an empty commit.\n- If a pre-commit hook fails, fix the underlying issue, re-stage, and create a **new** commit — do not amend the previous one (the failed commit never happened).\n- If secrets or clearly unrelated files are detected among the changes, stop and confirm with the user before including them.\n","# Commit\n\nStage the outstanding changes and create a single git commit with an English message that follows this project's format.\n\n## User Input\n\n```text\n$ARGUMENTS\n```\n\nConsider any additional context from the user input (e.g. \"only commit the tool changes\", \"this is a bug fix\") before proceeding.\n\n## Procedure\n\n### Step 1: Survey the Changes\n\nRun in parallel:\n- `git status` — see tracked and untracked files\n- `git diff` and `git diff --staged` — see the actual content changes\n- `git log --oneline -10` — match the repository's existing commit message tone\n\n### Step 2: Stage the Changes\n\nStage the modified and new files that belong to this piece of work (`git add \u003Cfiles>`, or `git add -A` when everything in the working tree is part of the same change).\n\nBefore committing, look at the staged file list once more:\n- If anything looks like a secret or credential (`.env`, `*.pem`, `credentials.json`, API keys, etc.), unstage it and warn the user instead of committing it silently.\n- If some staged files clearly belong to unrelated, separate work (not what the user is asking to commit right now), leave them out and mention it to the user.\n\n### Step 3: Determine the Commit Type\n\nLook at the diff and classify the change into a prefix:\n\n| Prefix | When to use |\n|--------|-------------|\n| `fix:` | Bug fix |\n| `feat:` | New feature or capability |\n| `refactor:` | Restructuring without behavior change |\n| `docs:` | Documentation only (README, YARD, locale text) |\n| `test:` | Test-only changes |\n| `chore:` | Tooling, dependencies, config, housekeeping |\n| `style:` | Formatting\u002Fwhitespace only, no logic change |\n| `perf:` | Performance improvement |\n\nIf a change spans multiple categories, pick the one that reflects the primary intent.\n\n### Step 4: Write the Commit Message\n\nFormat:\n- **Line 1**: `\u003Cprefix>: \u003Cconcise summary of the overall change>` — English, imperative mood, no trailing period.\n- **If the change is small** (one focused fix, a single file, a short diff): stop at line 1. No body needed.\n- **If the change touches several things**: leave a blank line after line 1, then a short bullet list (`- ...`), one line per notable change. Keep bullets brief — what changed, not how.\n\nExample (small change):\n```\nfix: correct nil check in issue summary cache lookup\n```\n\nExample (larger change):\n```\nfeat: add vector model profile support to settings\n\n- add use_vector_model_profile and vector_model_profile_id columns\n- update settings UI to select a dedicated vector model profile\n- fall back to the default model profile when unset\n```\n\nDo not add a `Co-Authored-By` line or any other reference to Claude\u002FAI assistance — this project's convention explicitly excludes that from commit messages.\n\n### Step 5: Commit\n\nUse a heredoc so multi-line messages are formatted correctly:\n\n```bash\ngit commit -m \"$(cat \u003C\u003C'EOF'\n\u003Cprefix>: \u003Csummary>\n\n- \u003Cdetail 1>\n- \u003Cdetail 2>\nEOF\n)\"\n```\n\nAlways create a new commit — never `--amend` an existing one unless the user explicitly asks for it.\n\n### Step 6: Confirm\n\nRun `git status` after the commit and report the resulting commit (short hash + first line) to the user. Do not push.\n\n## Notes\n\n- Never push — this skill only commits locally.\n- Never use `--no-verify` to skip hooks.\n- Write commit messages in plain English regardless of the conversation language.\n\n## Error Handling\n\n- If there is nothing staged and nothing to stage (clean working tree), tell the user there is nothing to commit — do not create an empty commit.\n- If a pre-commit hook fails, fix the underlying issue, re-stage, and create a **new** commit — do not amend the previous one (the failed commit never happened).\n- If secrets or clearly unrelated files are detected among the changes, stop and confirm with the user before including them.\n",{"name":5,"description":7,"argument-hint":24,"user-invocable":25,"disable-model-invocation":20},"Optional: additional context about what changed, or which files to include",true,"main","525b76bfa8636710365d3f466612d94ed0c91bfa",".claude\u002Fskills\u002Fcommit",1,"https:\u002F\u002Fgithub.com\u002Fharu\u002Fredmine_render_switcher","https:\u002F\u002Fgithub.com\u002Fharu","Software Engineer","2026-10-31 22:53:57",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":25},[36,39,42],{"tool":37,"command":38},"npx","npx skills add haru\u002Fredmine_render_switcher --skill commit",{"tool":40,"command":41},"bunx","bunx skills add haru\u002Fredmine_render_switcher --skill commit",{"tool":43,"command":44},"pnpm","pnpm dlx skills add haru\u002Fredmine_render_switcher --skill commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fharu\u002Fredmine_render_switcher\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcommit\u002FSKILL.md",[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7D137RBYCHARK4HPPN5SFCR","speckit-review-types","Type design analysis — encapsulation, invariant expression, usefulness, and enforcement.","https:\u002F\u002Fgithub.com\u002Fharu\u002Fredmine_render_switcher\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Freview\u002F.specify-dev\u002Fagent-commands\u002Fclaude\u002Fspeckit-review-types\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},"01M7D134TVGF753NEVRBJXTQMX","speckit-review-tests","Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.","https:\u002F\u002Fgithub.com\u002Fharu\u002Fredmine_render_switcher\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Freview\u002F.specify-dev\u002Fagent-commands\u002Fclaude\u002Fspeckit-review-tests\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},"01M7D132GQW5KDNACTPY79S6XD","speckit-review-simplify","Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.","https:\u002F\u002Fgithub.com\u002Fharu\u002Fredmine_render_switcher\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Freview\u002F.specify-dev\u002Fagent-commands\u002Fclaude\u002Fspeckit-review-simplify\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":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7D12YC8EA9SR4ST3FTQ2500","speckit-review-run","Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.","https:\u002F\u002Fgithub.com\u002Fharu\u002Fredmine_render_switcher\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Freview\u002F.specify-dev\u002Fagent-commands\u002Fclaude\u002Fspeckit-review-run\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7D12VQ047ZD91V4Z6RGVHJ5","speckit-review-errors","Error handling review — silent failure detection, catch block analysis, error logging.","https:\u002F\u002Fgithub.com\u002Fharu\u002Fredmine_render_switcher\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Freview\u002F.specify-dev\u002Fagent-commands\u002Fclaude\u002Fspeckit-review-errors\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7D12SGPSNT7GVQQR4ETVGFE","speckit-review-comments","Code comment accuracy verification, documentation completeness assessment, comment rot detection.","https:\u002F\u002Fgithub.com\u002Fharu\u002Fredmine_render_switcher\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Freview\u002F.specify-dev\u002Fagent-commands\u002Fclaude\u002Fspeckit-review-comments\u002FSKILL.md",[],[]]