[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AZSPKV3PHYA2CZB73GGJGT":3,"skill-same:01M7AZSPKV3PHYA2CZB73GGJGT":50},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7AZSPKV3PHYA2CZB73GGJGT","speckit-git-feature",null,"Create a feature branch with sequential or timestamp numbering","arrrrny\u002Fziki","arrrrny","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F48218623?v=4","01M7AT2E1VCEKRXW66PKN6VF10","Ahmet TOK","01M7AZQZB8R6MX6CAY1XFT2S53",0,"MIT","https:\u002F\u002Fgithub.com\u002Farrrrny\u002Fziki\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fspeckit-git-feature\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: speckit-git-feature\ndescription: Create a feature branch with sequential or timestamp numbering\ncompatibility: Requires spec-kit project structure with .specify\u002F directory\nmetadata:\n  author: spec-kit-core\n  source: git:commands\u002Fspeckit.git.feature.md\n---\n\n# Create Feature Branch\n\nCreate and switch to a new git feature branch for the given specification. This command handles **branch creation only** — the spec directory and files are created by the core `\u002Fspeckit-specify` workflow.\n\n## User Input\n\n```text\n$ARGUMENTS\n```\n\nYou **MUST** consider the user input before proceeding (if not empty).\n\n## Environment Variable Override\n\nIf the user explicitly provided `GIT_BRANCH_NAME` (e.g., via environment variable, argument, or in their request), pass it through to the script by setting the `GIT_BRANCH_NAME` environment variable before invoking the script. When `GIT_BRANCH_NAME` is set:\n- The script uses the exact value as the branch name, bypassing all prefix\u002Fsuffix generation\n- `--short-name`, `--number`, and `--timestamp` flags are ignored\n- `FEATURE_NUM` is extracted when the final path segment starts with a numeric or timestamp feature marker (for example `042-name`, `feat\u002F042-name`, or `jdoe\u002Fapp\u002F042-name`), otherwise set to the full branch name\n\n## Prerequisites\n\n- Verify Git is available by running `git rev-parse --is-inside-work-tree 2>\u002Fdev\u002Fnull`\n- If Git is not available, warn the user and skip branch creation\n\n## Branch Numbering Mode\n\nDetermine the branch numbering strategy by checking configuration in this order:\n\n1. Check `.specify\u002Fextensions\u002Fgit\u002Fgit-config.yml` for `branch_numbering` value\n2. Check `.specify\u002Finit-options.json` for `feature_numbering` value (inherit from core)\n3. Check `.specify\u002Finit-options.json` for `branch_numbering` value (deprecated, backward compatibility — will be removed in a future release)\n4. Default to `sequential` if none of the above exist\n\n## Branch Name Template\n\nCheck `.specify\u002Fextensions\u002Fgit\u002Fgit-config.yml` for an optional `branch_template` value. If it is empty or missing, use the default branch shape `{number}-{slug}`. If it is set, `{slug}` must not appear before `{number}`, its final path segment must start with `{number}-`, and the script expands these tokens:\n\n- `{author}`: sanitized Git config author (`user.name`, falling back to the email local part)\n- `{app}`: sanitized Spec Kit init directory name\n- `{number}`: sequential number or timestamp\n- `{slug}`: generated short branch slug\n\nFor monorepos, a template such as `{author}\u002F{app}\u002F{number}-{slug}` creates names like `jdoe\u002Fweb\u002F008-guided-tour` while preserving per-project feature numbering.\n\nThe script also accepts `branch_prefix` as a shorthand for simple namespaces; it expands to `\u003Cbranch_prefix>\u002F{number}-{slug}`.\n\n## Execution\n\nGenerate a concise short name (2-4 words) for the branch:\n- Analyze the feature description and extract the most meaningful keywords\n- Use action-noun format when possible (e.g., \"add-user-auth\", \"fix-payment-bug\")\n- Preserve technical terms and acronyms (OAuth2, API, JWT, etc.)\n\nRun the appropriate script based on your platform:\n\n- **Bash**: `.specify\u002Fextensions\u002Fgit\u002Fscripts\u002Fbash\u002Fcreate-new-feature-branch.sh --json --short-name \"\u003Cshort-name>\" \"\u003Cfeature description>\"`\n- **Bash (timestamp)**: `.specify\u002Fextensions\u002Fgit\u002Fscripts\u002Fbash\u002Fcreate-new-feature-branch.sh --json --timestamp --short-name \"\u003Cshort-name>\" \"\u003Cfeature description>\"`\n- **PowerShell**: `.specify\u002Fextensions\u002Fgit\u002Fscripts\u002Fpowershell\u002Fcreate-new-feature-branch.ps1 -Json -ShortName \"\u003Cshort-name>\" \"\u003Cfeature description>\"`\n- **PowerShell (timestamp)**: `.specify\u002Fextensions\u002Fgit\u002Fscripts\u002Fpowershell\u002Fcreate-new-feature-branch.ps1 -Json -Timestamp -ShortName \"\u003Cshort-name>\" \"\u003Cfeature description>\"`\n\n## Worktree Activation (MANDATORY when `create_worktree: true`)\n\nIf the JSON output contains `WORKTREE_PATH`, you **MUST** automatically switch the\nworking directory into that worktree immediately after the script returns, and run\nevery subsequent Spec Kit command from there. This is not optional: the primary\ncheckout must stay on its original branch, and the spec, plan, and tasks must be\ncreated inside the worktree so the feature is fully isolated.\n\n- Parse `WORKTREE_PATH` from the script's JSON output.\n- Change directory into it before doing anything else:\n  - **Bash**: `cd \"$WORKTREE_PATH\"`\n  - **PowerShell**: `Set-Location \"$env:WORKTREE_PATH\"`\n- Verify the switch with `git rev-parse --show-toplevel`; it must match the worktree\n  directory, not the primary checkout.\n- Continue the workflow (e.g. `\u002Fspeckit-specify`) from the worktree root.\n- If `WORKTREE_PATH` is absent, the feature branch was created on the current checkout\n  as usual — do not change directory.\n\n**IMPORTANT**:\n- Do NOT pass `--number` — the script determines the correct next number automatically\n- Always include the JSON flag (`--json` for Bash, `-Json` for PowerShell) so the output can be parsed reliably\n- You must only ever run this script once per feature\n- The JSON output will contain `BRANCH_NAME` and `FEATURE_NUM`, and `WORKTREE_PATH` when worktree mode is active\n- Do not manually expand `branch_template`; the script reads the git extension config and applies it consistently\n- When `WORKTREE_PATH` is present, switching into it (above) is mandatory before any further steps\n\n## Graceful Degradation\n\nIf Git is not installed or the current directory is not a Git repository:\n- Branch creation is skipped with a warning: `[specify] Warning: Git repository not detected; skipped branch creation`\n- The script still outputs `BRANCH_NAME` and `FEATURE_NUM` so the caller can reference them\n\n## Worktree Mode\n\nIf `.specify\u002Fextensions\u002Fgit\u002Fgit-config.yml` sets `create_worktree: true`, the script\ncreates a git worktree for the new feature branch instead of checking out the branch\non the current checkout. Concretely it runs `git worktree add -b \u003Cbranch> \u003Cpath>`\n(attaching to an existing branch with `git worktree add \u003Cpath> \u003Cbranch>` when\n`--allow-existing-branch` is given), leaving `HEAD` of the primary checkout untouched\nso multiple features can be worked on in parallel.\n\n- By default the worktree is created inside the project at\n  `.worktrees\u002F\u003Cbranch>` (e.g. `myproject\u002F.worktrees\u002F003-user-auth`).\n- Override the computed path with the `SPECIFY_WORKTREE_PATH` environment variable.\n- The script still outputs `BRANCH_NAME` (the branch name) and `FEATURE_NUM`; when\n  worktree mode is active it additionally outputs `WORKTREE_PATH` (the worktree\n  directory). **You MUST `cd` into `WORKTREE_PATH` automatically** — see the\n  *Worktree Activation* section above — so the rest of the Spec Kit workflow runs\n  inside the worktree rather than the primary checkout.\n\n## Output\n\nThe script outputs JSON with:\n- `BRANCH_NAME`: The branch name (e.g., `003-user-auth`, `20260319-143022-user-auth`, or `jdoe\u002Fweb\u002F003-user-auth`)\n- `FEATURE_NUM`: The numeric or timestamp prefix used\n- `WORKTREE_PATH`: (only when `create_worktree: true`) The worktree directory created for the feature","# Create Feature Branch\n\nCreate and switch to a new git feature branch for the given specification. This command handles **branch creation only** — the spec directory and files are created by the core `\u002Fspeckit-specify` workflow.\n\n## User Input\n\n```text\n$ARGUMENTS\n```\n\nYou **MUST** consider the user input before proceeding (if not empty).\n\n## Environment Variable Override\n\nIf the user explicitly provided `GIT_BRANCH_NAME` (e.g., via environment variable, argument, or in their request), pass it through to the script by setting the `GIT_BRANCH_NAME` environment variable before invoking the script. When `GIT_BRANCH_NAME` is set:\n- The script uses the exact value as the branch name, bypassing all prefix\u002Fsuffix generation\n- `--short-name`, `--number`, and `--timestamp` flags are ignored\n- `FEATURE_NUM` is extracted when the final path segment starts with a numeric or timestamp feature marker (for example `042-name`, `feat\u002F042-name`, or `jdoe\u002Fapp\u002F042-name`), otherwise set to the full branch name\n\n## Prerequisites\n\n- Verify Git is available by running `git rev-parse --is-inside-work-tree 2>\u002Fdev\u002Fnull`\n- If Git is not available, warn the user and skip branch creation\n\n## Branch Numbering Mode\n\nDetermine the branch numbering strategy by checking configuration in this order:\n\n1. Check `.specify\u002Fextensions\u002Fgit\u002Fgit-config.yml` for `branch_numbering` value\n2. Check `.specify\u002Finit-options.json` for `feature_numbering` value (inherit from core)\n3. Check `.specify\u002Finit-options.json` for `branch_numbering` value (deprecated, backward compatibility — will be removed in a future release)\n4. Default to `sequential` if none of the above exist\n\n## Branch Name Template\n\nCheck `.specify\u002Fextensions\u002Fgit\u002Fgit-config.yml` for an optional `branch_template` value. If it is empty or missing, use the default branch shape `{number}-{slug}`. If it is set, `{slug}` must not appear before `{number}`, its final path segment must start with `{number}-`, and the script expands these tokens:\n\n- `{author}`: sanitized Git config author (`user.name`, falling back to the email local part)\n- `{app}`: sanitized Spec Kit init directory name\n- `{number}`: sequential number or timestamp\n- `{slug}`: generated short branch slug\n\nFor monorepos, a template such as `{author}\u002F{app}\u002F{number}-{slug}` creates names like `jdoe\u002Fweb\u002F008-guided-tour` while preserving per-project feature numbering.\n\nThe script also accepts `branch_prefix` as a shorthand for simple namespaces; it expands to `\u003Cbranch_prefix>\u002F{number}-{slug}`.\n\n## Execution\n\nGenerate a concise short name (2-4 words) for the branch:\n- Analyze the feature description and extract the most meaningful keywords\n- Use action-noun format when possible (e.g., \"add-user-auth\", \"fix-payment-bug\")\n- Preserve technical terms and acronyms (OAuth2, API, JWT, etc.)\n\nRun the appropriate script based on your platform:\n\n- **Bash**: `.specify\u002Fextensions\u002Fgit\u002Fscripts\u002Fbash\u002Fcreate-new-feature-branch.sh --json --short-name \"\u003Cshort-name>\" \"\u003Cfeature description>\"`\n- **Bash (timestamp)**: `.specify\u002Fextensions\u002Fgit\u002Fscripts\u002Fbash\u002Fcreate-new-feature-branch.sh --json --timestamp --short-name \"\u003Cshort-name>\" \"\u003Cfeature description>\"`\n- **PowerShell**: `.specify\u002Fextensions\u002Fgit\u002Fscripts\u002Fpowershell\u002Fcreate-new-feature-branch.ps1 -Json -ShortName \"\u003Cshort-name>\" \"\u003Cfeature description>\"`\n- **PowerShell (timestamp)**: `.specify\u002Fextensions\u002Fgit\u002Fscripts\u002Fpowershell\u002Fcreate-new-feature-branch.ps1 -Json -Timestamp -ShortName \"\u003Cshort-name>\" \"\u003Cfeature description>\"`\n\n## Worktree Activation (MANDATORY when `create_worktree: true`)\n\nIf the JSON output contains `WORKTREE_PATH`, you **MUST** automatically switch the\nworking directory into that worktree immediately after the script returns, and run\nevery subsequent Spec Kit command from there. This is not optional: the primary\ncheckout must stay on its original branch, and the spec, plan, and tasks must be\ncreated inside the worktree so the feature is fully isolated.\n\n- Parse `WORKTREE_PATH` from the script's JSON output.\n- Change directory into it before doing anything else:\n  - **Bash**: `cd \"$WORKTREE_PATH\"`\n  - **PowerShell**: `Set-Location \"$env:WORKTREE_PATH\"`\n- Verify the switch with `git rev-parse --show-toplevel`; it must match the worktree\n  directory, not the primary checkout.\n- Continue the workflow (e.g. `\u002Fspeckit-specify`) from the worktree root.\n- If `WORKTREE_PATH` is absent, the feature branch was created on the current checkout\n  as usual — do not change directory.\n\n**IMPORTANT**:\n- Do NOT pass `--number` — the script determines the correct next number automatically\n- Always include the JSON flag (`--json` for Bash, `-Json` for PowerShell) so the output can be parsed reliably\n- You must only ever run this script once per feature\n- The JSON output will contain `BRANCH_NAME` and `FEATURE_NUM`, and `WORKTREE_PATH` when worktree mode is active\n- Do not manually expand `branch_template`; the script reads the git extension config and applies it consistently\n- When `WORKTREE_PATH` is present, switching into it (above) is mandatory before any further steps\n\n## Graceful Degradation\n\nIf Git is not installed or the current directory is not a Git repository:\n- Branch creation is skipped with a warning: `[specify] Warning: Git repository not detected; skipped branch creation`\n- The script still outputs `BRANCH_NAME` and `FEATURE_NUM` so the caller can reference them\n\n## Worktree Mode\n\nIf `.specify\u002Fextensions\u002Fgit\u002Fgit-config.yml` sets `create_worktree: true`, the script\ncreates a git worktree for the new feature branch instead of checking out the branch\non the current checkout. Concretely it runs `git worktree add -b \u003Cbranch> \u003Cpath>`\n(attaching to an existing branch with `git worktree add \u003Cpath> \u003Cbranch>` when\n`--allow-existing-branch` is given), leaving `HEAD` of the primary checkout untouched\nso multiple features can be worked on in parallel.\n\n- By default the worktree is created inside the project at\n  `.worktrees\u002F\u003Cbranch>` (e.g. `myproject\u002F.worktrees\u002F003-user-auth`).\n- Override the computed path with the `SPECIFY_WORKTREE_PATH` environment variable.\n- The script still outputs `BRANCH_NAME` (the branch name) and `FEATURE_NUM`; when\n  worktree mode is active it additionally outputs `WORKTREE_PATH` (the worktree\n  directory). **You MUST `cd` into `WORKTREE_PATH` automatically** — see the\n  *Worktree Activation* section above — so the rest of the Spec Kit workflow runs\n  inside the worktree rather than the primary checkout.\n\n## Output\n\nThe script outputs JSON with:\n- `BRANCH_NAME`: The branch name (e.g., `003-user-auth`, `20260319-143022-user-auth`, or `jdoe\u002Fweb\u002F003-user-auth`)\n- `FEATURE_NUM`: The numeric or timestamp prefix used\n- `WORKTREE_PATH`: (only when `create_worktree: true`) The worktree directory created for the feature",{"name":5,"metadata":24,"description":7,"compatibility":27},{"author":25,"source":26},"spec-kit-core","git:commands\u002Fspeckit.git.feature.md","Requires spec-kit project structure with .specify\u002F directory","master","7c8cce5753420b462b701bb326502fdf3c5884af",".agents\u002Fskills\u002Fspeckit-git-feature","https:\u002F\u002Fgithub.com\u002Farrrrny\u002Fziki","https:\u002F\u002Fgithub.com\u002Farrrrny","https:\u002F\u002Farrrrny.com","AI Engineer @ ZikZak AI Moscow, Russia","2026-11-11 20:51:08",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add arrrrny\u002Fziki --skill speckit-git-feature",{"tool":42,"command":43},"bunx","bunx skills add arrrrny\u002Fziki --skill speckit-git-feature",{"tool":45,"command":46},"pnpm","pnpm dlx skills add arrrrny\u002Fziki --skill speckit-git-feature","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Farrrrny\u002Fziki\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fspeckit-git-feature\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7AZY7ZKNC7K7969TPA52R4W","speckit-tdd-verify","Audit the feature's TDD discipline and test strength from cold context: test-first evidence in git history, red-phase evidence, test-smell rubric, mutation testing on the changed files, and acceptance-criteria coverage, then write specs\u002F\u003Cfeature>\u002Ftdd\u002Fverification.md with a verdict and remediation tasks","https:\u002F\u002Fgithub.com\u002Farrrrny\u002Fziki\u002Fblob\u002Fmaster\u002F.specify\u002Fextensions\u002Ftdd\u002F.specify-dev\u002Fagent-commands\u002Fkimi\u002Fspeckit-tdd-verify\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7AZY47FS1FY2JFYBCQMWSJQ","speckit-tdd-setup","Detect the repository's test stack and write .specify\u002Fmemory\u002Ftdd-profile.md with the exact verified commands the loop needs (single test, full suite, coverage, mutation), plus the TDD principle to add to the project constitution","https:\u002F\u002Fgithub.com\u002Farrrrny\u002Fziki\u002Fblob\u002Fmaster\u002F.specify\u002Fextensions\u002Ftdd\u002F.specify-dev\u002Fagent-commands\u002Fkimi\u002Fspeckit-tdd-setup\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7AZXYP759RBHDS1RBD7YQHA","speckit-tdd-run","Drive the red-green-refactor loop one behavior at a time from the test list: write one failing test, prove it fails for the right reason, make it pass with the smallest change, refactor while green, record the evidence in the feature's tdd\u002Fcycle-log.md, and tick the tasks.md tasks the completed behaviors cover","https:\u002F\u002Fgithub.com\u002Farrrrny\u002Fziki\u002Fblob\u002Fmaster\u002F.specify\u002Fextensions\u002Ftdd\u002F.specify-dev\u002Fagent-commands\u002Fkimi\u002Fspeckit-tdd-run\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7AZXTMFNR4SZ2ECXNHD8P69","speckit-tdd-plan","Derive the feature's test list from spec.md and plan.md into specs\u002F\u003Cfeature>\u002Ftdd\u002Ftest-list.md (outer acceptance behaviors, inner unit behaviors, each traced to an acceptance criterion) and make the test tasks in tasks.md mandatory and correctly ordered","https:\u002F\u002Fgithub.com\u002Farrrrny\u002Fziki\u002Fblob\u002Fmaster\u002F.specify\u002Fextensions\u002Ftdd\u002F.specify-dev\u002Fagent-commands\u002Fkimi\u002Fspeckit-tdd-plan\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7AZXPFC8HW76ZE9N4KTKPEP","speckit-spec-stats-runs","On-demand execution — reads verified suite command from .specify\u002Fmemory\u002Ftdd-profile.md, runs it for selected specs (--all, spec id\u002Fslug, or default active feature), captures pass\u002Ffail + duration + tail, appends run record to .specify\u002Fstats\u002Fruns.json, refreshes dashboard health column","https:\u002F\u002Fgithub.com\u002Farrrrny\u002Fziki\u002Fblob\u002Fmaster\u002F.specify\u002Fextensions\u002Fspec-stats\u002F.specify-dev\u002Fagent-commands\u002Fzed\u002Fspeckit-spec-stats-runs\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},"01M7AZXJ088ENB97FZD5VQFDNA","speckit-spec-stats-report","Main generator — scans all specs\u002F*\u002F, derives per-feature stage, task progress, health, last updated; when the TDD extension is installed, adds a deep TDD table (acceptance\u002Funit\u002Fcharacterization counts, DONE, loop mode, tasks.md state); renders dashboard to configurable output path and writes .specify\u002Fstats\u002Fstats.json snapshot","https:\u002F\u002Fgithub.com\u002Farrrrny\u002Fziki\u002Fblob\u002Fmaster\u002F.specify\u002Fextensions\u002Fspec-stats\u002F.specify-dev\u002Fagent-commands\u002Fzed\u002Fspeckit-spec-stats-report\u002FSKILL.md",[],[]]