claude-dev-env 1.55.0 → 1.55.1

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": "claude-dev-env",
3
- "version": "1.55.0",
3
+ "version": "1.55.1",
4
4
  "description": "Claude Code development standards — rules, hooks, agents, commands, and skills",
5
5
  "type": "module",
6
6
  "bin": {
@@ -111,6 +111,16 @@ git -C "<path>" log --oneline -1 main
111
111
 
112
112
  Report the move as `main <old> → <new>`, or "already up to date" when nothing changed.
113
113
 
114
+ Then report what the checkout runs — a move of the `main` ref says nothing about the files on disk:
115
+
116
+ ```
117
+ git -C "<path>" branch --show-current
118
+ git -C "<path>" status --short
119
+ ```
120
+
121
+ - **Checked-out branch.** When a branch other than `main` is checked out, say so plainly: the fast-forward moves a ref only and no file on disk changes. Code that runs from this checkout comes from the checked-out branch, not from `main`.
122
+ - **Dirty tracked files.** List every modified tracked file from `status --short`. Uncommitted edits sit on top of the checked-out branch and are what runs — flag them, because a ref update can neither see nor repair them. When the tree is clean, report "working tree clean".
123
+
114
124
  ## Constraints (non-negotiable)
115
125
 
116
126
  - **Fast-forward only.** If the remote's `main` is not a descendant of local `main`, stop. Never `--force`, never `branch -f`, never a merge commit. Divergence is a job for `/rebase`.
@@ -125,6 +135,7 @@ Report the move as `main <old> → <new>`, or "already up to date" when nothing
125
135
  - `<remote>/main` only moves after an explicit `git fetch`. Fetch inside every run; never compare against a remote-tracking ref left over from an earlier fetch.
126
136
  - `origin` is not always the source of truth. When a fork is `origin` and the canonical repo is another remote (often `upstream`), the confirmed remote should be the canonical one, not whichever is named `origin`.
127
137
  - Quote the path on every command — `git -C "<path>"` — so paths with spaces or a NAS drive letter survive.
138
+ - "Up to date" describes the `main` ref, not the running code. A checkout deployed on a feature branch, or carrying uncommitted edits, runs that branch plus those edits regardless of where `main` points. Phase 4's checkout-state report exists so the operator sees that gap on every run.
128
139
 
129
140
  ## What this skill does NOT do
130
141