一键导入
speckit-git-initialize
Initialize a Git repository with an initial commit
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Initialize a Git repository with an initial commit
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | speckit-git-initialize |
| description | Initialize a Git repository with an initial commit |
| compatibility | Requires spec-kit project structure with .specify/ directory |
| metadata | {"author":"github-spec-kit","source":"git:commands/speckit.git.initialize.md"} |
Initialize a Git repository in the current project directory if one does not already exist.
Run the appropriate script from the project root:
.specify/extensions/git/scripts/bash/initialize-repo.sh.specify/extensions/git/scripts/powershell/initialize-repo.ps1If the extension scripts are not found, fall back to:
git init && git add . && git commit -m "Initial commit from Specify template"git init; git add .; git commit -m "Initial commit from Specify template"The script handles all checks internally:
git init, git add ., and git commit with an initial commit messageReplace the script to add project-specific Git initialization steps:
.gitignore templatesgit config init.defaultBranch)On success:
[OK] Git repository initializedIf Git is not installed:
specs/)If Git is installed but git init, git add ., or git commit fails:
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
Execute the implementation plan by processing and executing all tasks defined in tasks.md
Execute the implementation planning workflow using the plan template to generate design artifacts.
Create or update the feature specification from a natural language feature description.
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
Invoked as "/windowsfy [path]" or when the user asks to "fix windows compatibility", "make package.json cross-platform", "windows portability", "run on windows", "cross-env", "shx", "PowerShell 5.1 error", "rm -rf on windows", "chmod on windows", "NODE_ENV not recognized", "glob not expanded on windows", "native binary on windows", "tfjs-node windows", "better-sqlite3 windows", "transformers windows", "token && is not a valid statement separator", "single quotes in npm scripts", or encounters npm script failures specific to Windows native shells. Path may be a directory, a single package.json file, or omitted (defaults to ./).