@tekyzinc/gsd-t 2.2.1 → 2.4.0

package/README.md

@@ -135,7 +135,7 @@ This will replace changed command files, back up your CLAUDE.md if customized, a
 | Command | Purpose |
 |---------|---------|
 | `/user:branch` | Create and switch to a new git branch |
-| `/user:checkin` | Stage, commit, and push all changes |
+| `/user:checkin` | Auto-bump version, stage, commit, and push |
 | `/user:Claude-md` | Reload CLAUDE.md directives mid-session |
 
 ---
@@ -254,7 +254,7 @@ get-stuff-done-teams/
 ├── commands/                          # 27 slash commands
 │   ├── gsd-t-*.md                     # 24 GSD-T workflow commands
 │   ├── branch.md                      # Git branch helper
-│   ├── checkin.md                     # Git commit/push helper
+│   ├── checkin.md                     # Auto-version + commit/push helper
 │   └── Claude-md.md                   # Reload CLAUDE.md directives
 ├── templates/                         # Document templates
 │   ├── CLAUDE-global.md

package/commands/checkin.md

@@ -1,15 +1,30 @@
 # Check in updated files to GitHub
 
-Automatically stage, commit, and push all updated files to GitHub.
+Automatically stage, commit, and push all updated files to GitHub with automatic version bumping.
 
 ## Instructions
 
 1. Run `git status` to see what files have changed
 2. If there are no changes, inform the user and stop
 3. Run `git diff` to review the changes
-4. Stage all changes with `git add -A`
-5. Create a commit with a descriptive message summarizing the changes
-6. Push to origin with `git push`
-7. Confirm success to the user
+4. Run the **Pre-Commit Gate** checklist from CLAUDE.md — update any docs before proceeding
+
+### Version Bump (Automatic)
+
+5. Determine the version bump type from the nature of the changes:
+   - **patch** (default): Bug fixes, doc updates, refactors, minor improvements, cleanup
+   - **minor**: New features, new commands, new capabilities
+   - **major**: Breaking changes, major rework, incompatible API changes
+6. Read the current version from `package.json`
+7. Bump the version according to the determined type (e.g., `2.3.0` → `2.3.1` for patch)
+8. Update the version in `package.json`
+9. If `.gsd-t/progress.md` exists, check for a `## Version` line and update it (or add one after the `## Date` line)
+
+### Commit and Push
+
+10. Stage all changes (including the version bump) with `git add -A`
+11. Create a commit with a descriptive message summarizing the changes. Include `(vX.Y.Z)` at the end of the first line. Example: `fix: resolve branch guard edge case (v2.3.1)`
+12. Push to origin with `git push`
+13. Confirm success to the user, including the old → new version
 
 Use the standard commit message format with Co-Authored-By line.

package/commands/gsd-t-execute.md

@@ -5,12 +5,15 @@ You are the lead agent coordinating task execution across domains. Choose solo o
 ## Step 1: Load State
 
 Read:
-1. `CLAUDE.md`
+1. `CLAUDE.md` — check for **Branch Guard** (`Expected branch` field)
 2. `.gsd-t/progress.md`
 3. `.gsd-t/contracts/` — all contracts
 4. `.gsd-t/contracts/integration-points.md` — dependency graph
 5. `.gsd-t/domains/*/tasks.md` — all task lists
 
+**Branch check (before any work):**
+Run `git branch --show-current`. If CLAUDE.md declares an expected branch and you're on a different branch, STOP and warn the user. Do NOT execute tasks on the wrong branch.
+
 Identify:
 - Which tasks are already complete (check progress.md)
 - Which tasks are unblocked (no pending dependencies)

package/commands/gsd-t-init.md

@@ -79,6 +79,9 @@ Create a starter template:
 - Workflows: docs/workflows.md
 - Infrastructure: docs/infrastructure.md
 
+## Branch Guard
+**Expected branch**: {current branch from `git branch --show-current`}
+
 ## Conventions
 - {Coding style, naming patterns — fill this in}
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tekyzinc/gsd-t",
-  "version": "2.2.1",
+  "version": "2.4.0",
   "description": "GSD-T: Contract-Driven Development for Claude Code — 27 slash commands with impact analysis, test sync, and milestone archival",
   "author": "Tekyz, Inc.",
   "license": "MIT",

package/templates/CLAUDE-global.md

@@ -52,7 +52,7 @@ PROJECT or FEATURE or SCAN
 | `/user:gsd-t-populate` | Auto-populate docs from existing codebase |
 | `/user:gsd-t-resume` | Restore context, continue |
 | `/user:branch` | Create and switch to a new git branch |
-| `/user:checkin` | Stage, commit, and push all changes |
+| `/user:checkin` | Auto-bump version, stage, commit, and push |
 | `/user:Claude-md` | Reload and apply CLAUDE.md directives |
 
 
@@ -115,6 +115,11 @@ NEVER commit code without running this checklist. This is not optional.
 
 ```
 BEFORE EVERY COMMIT:
+  ├── Am I on the correct branch?
+  │     CHECK → Run `git branch --show-current`
+  │     Compare against "Expected branch" in project CLAUDE.md
+  │     WRONG BRANCH → STOP. Do NOT commit. Switch to the correct branch first.
+  │     No guard set → Proceed (but warn user to set one)
   ├── Did I change an API endpoint or response shape?
   │     YES → Update .gsd-t/contracts/api-contract.md
   ├── Did I change the database schema?

package/templates/CLAUDE-project.md

@@ -21,6 +21,15 @@
 - Workflows: docs/workflows.md
 - Infrastructure: docs/infrastructure.md
 
+## Branch Guard
+<!-- Declare which branch this terminal session should work on. -->
+<!-- Claude will verify the branch before every commit. -->
+**Expected branch**: {main | master | feature-branch-name}
+
+<!-- For multi-branch parallel work (e.g., web + mobile in separate terminals), -->
+<!-- each terminal's CLAUDE.md should declare its own expected branch. -->
+<!-- Example: Web terminal → master, Mobile terminal → Mobile -->
+
 ## GSD-T Workflow
 This project uses contract-driven development.
 - State: .gsd-t/progress.md