init-projectlisted

# Init Project ## 1. Check Uncommitted Changes If inside a git repo with uncommitted changes — ask user whether to commit first, continue without commit, or stop. ## 2. Apply Template Move existing files to `old/` (find next available name: `old`, `old2`, `old3`...): ```bash OLD_DIR="old" N=2 while [ -e "$OLD_DIR" ]; do OLD_DIR="old${N}"; ((N++)); done mkdir "$OLD_DIR" find . -maxdepth 1 ! -name '.' ! -name '..' ! -name '.git' ! -name "$OLD_DIR" -exec mv {} "$OLD_DIR/" \; ``` Copy template: ```bash cp -rp ~/.claude/shared/templates/new-project/. . ``` After copy: - Verify `.claude/skills/project-knowledge/` exists - Security check: look for sensitive files in `$OLD_DIR/` (`.env*`, `*.key`, `*.pem`, `credentials.json`, `secrets/`) not covered by `.gitignore`. If found — add to `.gitignore` before proceeding. ## 3. Init Git and GitHub 1. Init git if not initialized 2. Verify `gh` CLI is installed and authenticated 3. Ask user for GitHub repository name 4. Create repo: `gh repo create {name} --private --source=. --remote=origin` 5. Initial commit and push to current branch 6. Create `dev` branch, push it ## 4. Init Project Knowledge Run `init-project-knowledge` skill to fill project documentation from existing files in the repo. ## 5. Sketch Offer After project knowledge is initialized, ask the user once — "Хочешь начать со скетча? `/sketch` — быстрый прототип за 3-5 вопросов, без спеков и валидаторов. Подходит если идея ещё не оформлена или нужен быстрый proof-of-