Initialize a Git repository with an initial commit
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
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:
✓ Git repository initializedIf Git is not installed:
specs/)If Git is installed but git init, git add ., or git commit fails:
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Stages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream. TRIGGER when: the user wants to commit, save, or check in the current changes. DO NOT TRIGGER when: opening a pull request → pr.
The English summary is being prepared. Showing the original description.
Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.
The English summary is being prepared. Showing the original description.
Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.
The English summary is being prepared. Showing the original description.
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.
The English summary is being prepared. Showing the original description.
Watches an open pull request's CI until green and fixes failing checks. TRIGGER when: the user wants to watch a pull request's CI, babysit a PR until it goes green, or fix failing CI checks on an open PR. DO NOT TRIGGER when: opening the PR in the first place → pr; rebasing the branch onto its base → rebase.
The English summary is being prepared. Showing the original description.
Opens a pull request, publishing the current branch as a PR. TRIGGER when: the user wants to open a pull request, publish the current branch as a PR, or take the current work through to an open PR. DO NOT TRIGGER when: only committing changes → commit; babysitting CI after the PR is already open → monitoring-pull-requests.
The English summary is being prepared. Showing the original description.