@tekyzinc/gsd-t 2.3.0 → 2.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -135,7 +135,7 @@ This will replace changed command files, back up your CLAUDE.md if customized, a
135
135
  | Command | Purpose |
136
136
  |---------|---------|
137
137
  | `/user:branch` | Create and switch to a new git branch |
138
- | `/user:checkin` | Stage, commit, and push all changes |
138
+ | `/user:checkin` | Auto-bump version, stage, commit, and push |
139
139
  | `/user:Claude-md` | Reload CLAUDE.md directives mid-session |
140
140
 
141
141
  ---
@@ -254,7 +254,7 @@ get-stuff-done-teams/
254
254
  ├── commands/ # 27 slash commands
255
255
  │ ├── gsd-t-*.md # 24 GSD-T workflow commands
256
256
  │ ├── branch.md # Git branch helper
257
- │ ├── checkin.md # Git commit/push helper
257
+ │ ├── checkin.md # Auto-version + commit/push helper
258
258
  │ └── Claude-md.md # Reload CLAUDE.md directives
259
259
  ├── templates/ # Document templates
260
260
  │ ├── CLAUDE-global.md
@@ -1,15 +1,30 @@
1
1
  # Check in updated files to GitHub
2
2
 
3
- Automatically stage, commit, and push all updated files to GitHub.
3
+ Automatically stage, commit, and push all updated files to GitHub with automatic version bumping.
4
4
 
5
5
  ## Instructions
6
6
 
7
7
  1. Run `git status` to see what files have changed
8
8
  2. If there are no changes, inform the user and stop
9
9
  3. Run `git diff` to review the changes
10
- 4. Stage all changes with `git add -A`
11
- 5. Create a commit with a descriptive message summarizing the changes
12
- 6. Push to origin with `git push`
13
- 7. Confirm success to the user
10
+ 4. Run the **Pre-Commit Gate** checklist from CLAUDE.md — update any docs before proceeding
11
+
12
+ ### Version Bump (Automatic)
13
+
14
+ 5. Determine the version bump type from the nature of the changes:
15
+ - **patch** (default): Bug fixes, doc updates, refactors, minor improvements, cleanup
16
+ - **minor**: New features, new commands, new capabilities
17
+ - **major**: Breaking changes, major rework, incompatible API changes
18
+ 6. Read the current version from `package.json`
19
+ 7. Bump the version according to the determined type (e.g., `2.3.0` → `2.3.1` for patch)
20
+ 8. Update the version in `package.json`
21
+ 9. If `.gsd-t/progress.md` exists, check for a `## Version` line and update it (or add one after the `## Date` line)
22
+
23
+ ### Commit and Push
24
+
25
+ 10. Stage all changes (including the version bump) with `git add -A`
26
+ 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)`
27
+ 12. Push to origin with `git push`
28
+ 13. Confirm success to the user, including the old → new version
14
29
 
15
30
  Use the standard commit message format with Co-Authored-By line.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tekyzinc/gsd-t",
3
- "version": "2.3.0",
3
+ "version": "2.4.0",
4
4
  "description": "GSD-T: Contract-Driven Development for Claude Code — 27 slash commands with impact analysis, test sync, and milestone archival",
5
5
  "author": "Tekyz, Inc.",
6
6
  "license": "MIT",
@@ -52,7 +52,7 @@ PROJECT or FEATURE or SCAN
52
52
  | `/user:gsd-t-populate` | Auto-populate docs from existing codebase |
53
53
  | `/user:gsd-t-resume` | Restore context, continue |
54
54
  | `/user:branch` | Create and switch to a new git branch |
55
- | `/user:checkin` | Stage, commit, and push all changes |
55
+ | `/user:checkin` | Auto-bump version, stage, commit, and push |
56
56
  | `/user:Claude-md` | Reload and apply CLAUDE.md directives |
57
57
 
58
58