toga-ai 1.0.891 → 1.0.892

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "toga-ai",
3
- "version": "1.0.891",
3
+ "version": "1.0.892",
4
4
  "description": "TOGA Technology Team Claude Knowledge System — shared AI coding harness with skills, knowledge base CLI, and project installer for Claude Code.",
5
5
  "keywords": [
6
6
  "claude",
@@ -65,6 +65,25 @@ it: a rewrite silently discards whatever the developer (or a teammate) changed i
65
65
 
66
66
  Only rewrite when explicitly told to.
67
67
 
68
+ ## Check git before stating commit state
69
+
70
+ Developers commit, push, and switch branches on their own between turns. Claude's memory of
71
+ "I edited this, so it is not committed" goes stale fast, and a wrong "not committed" reminder
72
+ confuses people.
73
+
74
+ Claude **must never** say a change is committed, not committed, pushed, or not pushed based on
75
+ memory. Before any such statement, run a fresh check **in the same turn**:
76
+
77
+ ```
78
+ git -C <repo> status --short <file>
79
+ git -C <repo> log -1 --format="%h %ad %s" --date=short -- <file>
80
+ ```
81
+
82
+ - Report what git shows: e.g. "committed in `23a3e11`" or "uncommitted changes in `<file>`".
83
+ - For push state, check `git -C <repo> status -sb` (ahead/behind) — do not assume.
84
+ - If Claude did not check, it says **nothing** about commit or push state. No habit reminders
85
+ like "still not committed" at the end of a summary.
86
+
68
87
  ## Branch protection
69
88
 
70
89
  Never commit directly to `_main`. All changes go through feature branches and pull requests.