@speclife/cli 0.9.0 → 0.9.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@speclife/cli",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "description": "CLI for SpecLife - for CI/scripts",
   "repository": {
     "type": "git",

package/templates/commands/convert.md

@@ -4,162 +4,25 @@ id: speclife-convert
 category: SpecLife
 description: Switch between branch-only and worktree modes for current change.
 ---
-# /speclife convert
-
-Switch between branch-only and worktree modes for current change.
-
-## ⚡ Execution
-
-**When this command is invoked, IMMEDIATELY execute the workflow below.**
-
-- Parse "to worktree" or "to branch" from the invocation
-- Check prerequisites before proceeding
-- Handle uncommitted changes (prompt to commit/stash)
-- Complete the conversion and report next steps
-
-## Usage
-
-```
-/speclife convert to worktree   # Branch → Worktree
-/speclife convert to branch     # Worktree → Branch
-```
-
-## When to use
-
-**To worktree:** You started simple but now need to work on something else in parallel.
-
-**To branch:** Your IDE struggles with worktrees, or you want simpler setup.
-
-## Steps
-
-### Convert to Worktree
-
-Prerequisites:
-- Must be on a `spec/*` branch in main repo
-- Cannot already be in a worktree
-
-```bash
-# 1. Check we're on a spec branch
-BRANCH=$(git branch --show-current)
-[[ ! "$BRANCH" =~ ^spec/ ]] && error "Not on a spec branch"
-
-# 2. Extract change-id
-CHANGE_ID=${BRANCH#spec/}
-
-# 3. Check worktree doesn't already exist
-[[ -d "worktrees/$CHANGE_ID" ]] && error "Worktree already exists"
-```
-
-Steps:
-1. **Commit changes** if any uncommitted work exists (or ask user to stash)
-2. **Create worktree** from current branch:
-   ```bash
-   git worktree add worktrees/$CHANGE_ID $BRANCH
-   ```
-3. **Return to main** in original repo:
-   ```bash
-   git checkout main
-   ```
-4. **Bootstrap environment** in worktree (symlink node_modules, etc.)
-5. **Report:**
-   ```
-   ✓ Created worktree at worktrees/<change-id>/
-   ✓ Main repo now on main branch
-   
-   Next: cd worktrees/<change-id>/ to continue work
-   ```
-
-### Convert to Branch
-
-Prerequisites:
-- Must be in a worktree (not main repo)
-- Must be on a `spec/*` branch
-
-```bash
-# Detect if we're in a worktree
-WORKTREE_ROOT=$(git rev-parse --path-format=relative --git-common-dir)
-[[ "$WORKTREE_ROOT" == ".git" ]] && error "Not in a worktree"
-```
-
-Steps:
-1. **Commit changes** if any uncommitted work exists (or ask user to stash)
-2. **Note current branch and worktree path**
-3. **Go to main repo:**
-   ```bash
-   cd $(git worktree list | grep -v '^\[' | head -1 | awk '{print $1}')
-   ```
-4. **Checkout the branch:**
-   ```bash
-   git checkout $BRANCH
-   ```
-5. **Remove worktree** (keeps branch):
-   ```bash
-   git worktree remove worktrees/$CHANGE_ID
-   ```
-6. **Report:**
-   ```
-   ✓ Removed worktree
-   ✓ Now on <branch> in main repo
-   
-   Next: Continue work here. Use /speclife convert to worktree if you need parallel work later.
-   ```
-
-## Examples
-
-**Branch → Worktree:**
-```
-User: /speclife convert to worktree
-
-Agent:
-ℹ️ Current: spec/add-oauth on main repo
-✓ Committed pending changes
-✓ Created worktree at worktrees/add-oauth/
-✓ Switched main repo to main branch
-
-Next: cd worktrees/add-oauth/
-```
-
-**Worktree → Branch:**
-```
-User: /speclife convert to branch
-
-Agent:
-ℹ️ Current: worktrees/add-oauth/ on spec/add-oauth
-✓ Committed pending changes
-✓ Checked out spec/add-oauth in main repo
-✓ Removed worktree
-
-Next: Continue in main repo
-```
-
-## Error Handling
-
-**Not on a spec branch:**
-```
-❌ Not on a spec/* branch. This command only works with spec branches.
-```
-
-**Already in target mode:**
-```
-ℹ️ Already in worktree mode. Nothing to convert.
-```
-
-**Uncommitted changes:**
-```
-⚠️ You have uncommitted changes:
-   - src/auth.ts (modified)
-   - package.json (modified)
-
-Options:
-1. Commit now (recommended)
-2. Stash and continue
-3. Abort
-```
-
-## Notes
-
-- Converting preserves all commits and history
-- Branch name stays the same (`spec/<change-id>`)
-- Spec files in `openspec/changes/<change-id>/` work in both modes
-- You can convert back and forth as needed
-
+**Guardrails**
+- Execute immediately—parse "to worktree" or "to branch" from invocation
+- Require: on a `spec/*` branch
+- Handle uncommitted changes: prompt to commit or stash
+
+**Steps (to worktree)**
+1. Check: must be on `spec/*` branch in main repo, worktree doesn't already exist.
+2. Commit any uncommitted changes (or ask user to stash).
+3. Create worktree: `git worktree add worktrees/<change-id> <branch>`.
+4. Return main repo to main: `git checkout main`.
+5. Report: worktree created, next step is `cd worktrees/<change-id>/`.
+
+**Steps (to branch)**
+1. Check: must be in a worktree on `spec/*` branch.
+2. Commit any uncommitted changes.
+3. Go to main repo, checkout the branch: `git checkout <branch>`.
+4. Remove worktree: `git worktree remove worktrees/<change-id>`.
+5. Report: worktree removed, continue in main repo.
+
+**Reference**
+- Converts preserve all commits and history
+- Branch name stays same; spec files work in both modes

package/templates/commands/land.md

@@ -2,245 +2,24 @@
 name: /speclife-land
 id: speclife-land
 category: SpecLife
-description: Merge an approved PR, clean up, and trigger auto-release if applicable.
+description: Merge an approved PR, clean up, and trigger auto-release.
 ---
-# /speclife land
-
-Merge a PR into main. Works with any PR - yours, team members', or external contributors'.
-
-## ⚡ Execution
-
-**When this command is invoked, IMMEDIATELY execute the workflow below.**
-
-- Do NOT skip steps or ask for excessive confirmation
-- If PR number is provided (#42), use that PR
-- If on a feature branch, find the PR for that branch
-- If on main, prompt for PR number
-- **STOP after reporting—this is a terminal command in the workflow**
-
-## TL;DR
-
-```
-/speclife land        # Land PR for current branch
-/speclife land #42    # Land specific PR by number
-```
-
-**Quick flow:**
-1. Find PR (from branch or number)
-2. Verify ready (approved, CI passing)
-3. Detect version bump type (feat → minor, fix → patch)
-4. If major (breaking) → confirm with user
-5. Bump version in feature branch, push
-6. Squash merge PR (version included)
-7. Cleanup (worktree if spec branch)
-8. GitHub Actions auto-creates release
-
-## Mode Detection
-
-```bash
-BRANCH=$(git branch --show-current)
-```
-
-| Invocation | Mode |
-|------------|------|
-| `/speclife land` on feature branch | Land PR for current branch |
-| `/speclife land #42` | Land specific PR |
-| `/speclife land` on main | Prompt for PR number |
-
-## Core Steps
-
-### 1. Find PR
-```bash
-# By branch
-gh pr view --json number,state,reviewDecision
-
-# By number
-gh pr view 42 --json number,state,reviewDecision
-```
-
-### 2. Check Ready
-Required:
-- ✓ State: open
-- ✓ Reviews: approved (or none required)
-- ✓ CI: passing
-- ✓ Mergeable: no conflicts
-
-If not ready → report issues and stop.
-
-### 3. Detect Version Bump
-Analyze PR title/commits to determine version bump:
-
-| Pattern | Bump | Example |
-|---------|------|---------|
-| `feat:` | minor | `feat: add OAuth login` |
-| `fix:` | patch | `fix: correct redirect URL` |
-| `feat!:` or `BREAKING CHANGE` | major | `feat!: redesign auth API` |
-| `docs:`, `chore:`, `test:` | patch | `docs: update README` |
-
-### 4. Confirm for Major (Breaking Changes)
-If major bump detected:
-```
-⚠️ Breaking change detected in PR #42.
-This will bump version to v2.0.0 (major).
-
-Proceed? (y/n)
-```
-- If user confirms → continue
-- If user declines → abort, suggest `/speclife release --major` for manual control
-
-### 5. Bump Version in Feature Branch
-**Do this BEFORE merging, in the feature branch:**
-```bash
-# Get current version
-CURRENT=$(node -p "require('./package.json').version")
-
-# Calculate new version
-npm version <patch|minor|major> --no-git-tag-version
-npm version <patch|minor|major> --no-git-tag-version --workspaces
-
-# Commit and push to feature branch
-git add -A
-git commit -m "chore(release): v<new-version>"
-git push origin <branch>
-```
-
-This ensures the version bump is included in the squash merge.
-
-### 6. Squash Merge PR
-```bash
-gh pr merge $PR --squash --delete-branch
-```
-
-The merged commit includes both the feature AND the version bump.
-
-### 7. Update Local
-```bash
-git checkout main
-git pull origin main
-```
-
-### 8. Cleanup
-
-| Type | Action |
-|------|--------|
-| Spec branch with worktree | `speclife worktree rm <change-id>` |
-| Spec branch (no worktree) | `git branch -d spec/<change-id>` |
-| Ad-hoc branch | `git branch -d <branch>` (if local exists) |
-| External PR | Nothing (no local branch) |
-
-**Detection:**
-```bash
-CHANGE_ID=${BRANCH#spec/}
-WORKTREE_PATH="worktrees/$CHANGE_ID"
-if [[ -d "$WORKTREE_PATH" ]]; then
-  speclife worktree rm $CHANGE_ID  # removes worktree + branch
-else
-  git branch -d $BRANCH            # just removes branch
-fi
-```
-
-### 9. Report and STOP
-```
-✓ Bumped version to v1.3.0 (minor)
-✓ Merged PR #42 (squash)
-✓ Cleaned up worktree
-ℹ️ GitHub Actions will create release automatically
-```
-
-**⛔ STOP HERE.** GitHub Actions will handle tag/release creation.
-
----
-
-<!-- REFERENCE SECTIONS - Read only when needed -->
-
-## Appendix: Error Handling
-
-**PR not found:**
-```
-❌ No PR found for branch. Run /speclife ship first.
-```
-
-**PR not ready:**
-```
-❌ PR #42 not ready:
-   - Review: changes_requested
-   - CI: failing
-Address issues and retry.
-```
-
-**Merge conflicts:**
-```
-❌ Merge conflicts detected.
-Run /speclife sync, resolve, push, then retry.
-```
-
-**On main without PR number:**
-```
-ℹ️ On main. Which PR to land?
-Recent PRs:
-  #45 - feat: dark mode (approved ✓)
-  #44 - fix: memory leak (needs review)
-```
-
-## Appendix: Examples
-
-**Spec branch (minor):**
-```
-User: /speclife land
-
-Agent:
-✓ PR #42 approved, CI passing
-ℹ️ Detected: feat: → minor bump
-✓ Bumped version to v1.3.0
-✓ Pushed version commit to feature branch
-✓ Merged PR #42 (squash)
-✓ Removed worktree
-ℹ️ GitHub Actions will create release v1.3.0
-```
-
-**By PR number (external):**
-```
-User: /speclife land #45
-
-Agent:
-ℹ️ PR #45 by @contributor
-ℹ️ Detected: fix: → patch bump
-✓ Bumped version to v1.2.4
-✓ Merged PR #45 (squash)
-ℹ️ GitHub Actions will create release v1.2.4
-Thanks @contributor!
-```
-
-**Major version (confirmation required):**
-```
-User: /speclife land
-
-Agent:
-✓ PR #50 approved, CI passing
-⚠️ Breaking change detected (feat!:)
-   This will bump to v2.0.0 (major).
-   Proceed? (y/n)
-
-User: y
-
-Agent:
-✓ Bumped version to v2.0.0
-✓ Merged PR #50 (squash)
-ℹ️ GitHub Actions will create release v2.0.0
-```
-
-**Major version (user declines):**
-```
-User: /speclife land
-
-Agent:
-⚠️ Breaking change detected (feat!:)
-   This will bump to v2.0.0 (major).
-   Proceed? (y/n)
-
-User: n
-
-Agent:
-ℹ️ Aborted. When ready, run:
-   /speclife release --major
-```
+**Guardrails**
+- Execute immediately—if PR number provided (#42), use it; if on feature branch, find its PR; if on main, prompt for PR number
+- Confirm with user only for major (breaking) version bumps
+- STOP after reporting—GitHub Actions handles release
+
+**Steps**
+1. Find PR: by branch (`gh pr view`) or by number (`gh pr view <num>`); error if not found.
+2. Check readiness: state=open, approved (or no reviews required), CI passing, no conflicts; report issues and stop if not ready.
+3. Detect version bump from PR title/commits: `feat:` → minor, `fix:/docs:/chore:` → patch, `feat!:/BREAKING CHANGE` → major.
+4. For major bumps: confirm with user; abort if declined (suggest `/speclife release --major` for manual control).
+5. Bump version in feature branch: `npm version <bump> --no-git-tag-version`, commit `chore(release): v<version>`, push.
+6. Squash merge: `gh pr merge --squash --delete-branch`.
+7. Update local: `git checkout main && git pull`.
+8. Cleanup: remove worktree if spec branch (`speclife worktree rm <id>`), else delete local branch.
+9. Report: version bumped, PR merged, cleanup done, GitHub Actions creating release.
+
+**Reference**
+- Version bump happens BEFORE merge so it's included in squash commit
+- Release workflow triggered by `chore(release): vX.X.X` commit message

package/templates/commands/release.md

@@ -2,118 +2,23 @@
 name: /speclife-release
 id: speclife-release
 category: SpecLife
-description: Create a release with version bump for manual releases (major versions).
+description: Create a release with version bump (typically for major versions).
 ---
-# /speclife release
-
-Create a release with version bump. Used for manual releases (typically major versions).
-
-## ⚡ Execution
-
-**When this command is invoked, IMMEDIATELY execute the workflow below.**
-
-- Check that we're on the main branch
-- Analyze commits to determine version bump (or use explicit flag)
-- Update version files and changelog
-- Commit and push to trigger release workflow
-
-## Usage
-
-```
-/speclife release              # Auto-detect version bump
-/speclife release --major      # Force major version bump
-/speclife release --minor      # Force minor version bump  
-/speclife release --patch      # Force patch version bump
-```
-
-## When to Use
-
-- **Major releases**: Breaking changes that require manual review
-- **Forced releases**: When auto-release is disabled or skipped
-- **Independent releases**: Creating a release without going through `/speclife land`
-
-## Preconditions
-
-- On `main` branch
-- Working directory clean
-- Changes merged since last release (for auto-detect)
-
-## Steps
-
-1. **Check branch**: Ensure on `main` branch
-   - If not, suggest switching or report error
-
-2. **Analyze commits**: Determine suggested version bump
-   - Get commits since last tag
-   - `feat:` commits → minor
-   - `fix:` commits → patch
-   - `BREAKING CHANGE` or `!` → major
-   - Use explicit flag if provided (--major, --minor, --patch)
-
-3. **Get current version**: Read from package.json (or equivalent)
-
-4. **Calculate new version**: Apply bump to current version
-   - Major: 1.2.3 → 2.0.0
-   - Minor: 1.2.3 → 1.3.0
-   - Patch: 1.2.3 → 1.2.4
-
-5. **Update version file**: Write new version to package.json
-
-6. **Update CHANGELOG**: Add release notes
-   - Group commits by type (Features, Fixes, etc.)
-   - Include commit messages and PR references
-
-7. **Commit**: `git commit -am "chore(release): vX.X.X"`
-   - This commit message triggers the release workflow
-
-8. **Push**: `git push origin main`
-
-9. **Create release PR** (optional, for review):
-   - If major release, create PR for review
-   - If patch/minor with auto-merge, push directly
-
-10. **Report**: Show next steps
-
-## Example
-
-```
-User: /speclife release --major
-
-Agent:
-Analyzing commits since v1.2.3...
-  - feat: add OAuth login (breaking: changes auth API)
-  - fix: correct redirect URL
-  - docs: update API documentation
-
-Current version: 1.2.3
-New version: 2.0.0 (major bump)
-
-✓ Updated package.json to 2.0.0
-✓ Updated CHANGELOG.md
-✓ Committed: "chore(release): v2.0.0"
-✓ Pushed to origin/main
-
-Release workflow triggered. GitHub Actions will:
-  1. Create tag v2.0.0
-  2. Create GitHub Release with notes
-  3. Publish to npm (if configured)
-
-Done! Release v2.0.0 is being created.
-```
-
-## Release Workflow
-
-When the `chore(release): vX.X.X` commit is pushed, the GitHub Actions workflow (`.github/workflows/speclife-release.yml`) automatically:
-
-1. Extracts version from commit message
-2. Creates git tag
-3. Creates GitHub Release with auto-generated notes
-4. Optionally publishes to package registry
-
-## Notes
-
-- For patch/minor releases, prefer using `/speclife land` which handles auto-release
-- Major releases should go through this command for explicit control
-- The release commit message format `chore(release): vX.X.X` is required for the workflow
-
-
+**Guardrails**
+- Execute immediately—must be on main with clean working directory
+- Use for major releases or when auto-release was skipped
+- For patch/minor, prefer `/speclife land` which handles auto-release
+
+**Steps**
+1. Check branch: must be on `main`; error otherwise.
+2. Analyze commits since last tag: `feat:` → minor, `fix:` → patch, `BREAKING CHANGE` or `!` → major; use explicit flag (--major/--minor/--patch) if provided.
+3. Calculate new version from current `package.json`.
+4. Update version: `npm version <bump> --no-git-tag-version` (and workspaces if monorepo).
+5. Update CHANGELOG.md with grouped commits.
+6. Commit: `git commit -am "chore(release): v<version>"`.
+7. Push: `git push origin main`.
+8. Report: version bumped, pushed, GitHub Actions will create tag and release.
+
+**Reference**
+- Commit message format `chore(release): vX.X.X` triggers release workflow
+- Major releases should use this command; patch/minor typically via `/speclife land`