devrites 6.4.3 → 6.4.4

package/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 All notable changes to DevRites are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and DevRites adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). Releases are generated automatically by [semantic-release](https://semantic-release.gitbook.io/) from Conventional Commits on `main`.
 
+## [6.4.4](https://github.com/ViktorsBaikers/DevRites/compare/v6.4.3...v6.4.4) (2026-10-16)
+
+### Fixed
+
+* **devrites:** force-add ignore-matched paths in checkpoint and ship ([#118](https://github.com/ViktorsBaikers/DevRites/issues/118)) ([ea25b06](https://github.com/ViktorsBaikers/DevRites/commit/ea25b0629b6428db7352c9d094c836d38ac40913))
+
 ## [6.4.3](https://github.com/ViktorsBaikers/DevRites/compare/v6.4.2...v6.4.3) (2026-10-16)
 
 ### Fixed

package/README.md

@@ -31,7 +31,7 @@ history can't lose it. After you clear the conversation, switch hosts, or hand
 the feature to another engineer, the next session reads the same plan,
 decisions, and evidence before it continues.
 
-**Status:** [`v6.4.3`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v6.4.3): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
+**Status:** [`v6.4.4`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v6.4.4): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
 
 This is the latest published release; `main` may contain unreleased work.
 

package/pack/.claude/skills/rite-build/reference/checkpoint.md

@@ -27,7 +27,10 @@ A native-worktree `transfer_commit` is transport on the worker branch only.
 ## The commit
 Stage the exact candidate paths from the manifest, each as its own argv.
 Never stage `touched-files.md`, a directory, glob, unrelated path, or user change.
-Verify the staged set, then commit locally.
+Before planning, run `git check-ignore -v --no-index -- <paths>`: every match, tracked
+or not, goes in the `git add -f --` list, because `git add` exits 1 on a named ignored
+path even after staging it. Keep each command's stderr. Verify the staged set, then
+commit locally.
 
 Subject: `WIP(<slug>):` plus an imperative summary of the change (from the
 goal). Never a slice id, `SLICE-###`, a slice number, or "this slice"

package/pack/.claude/skills/rite-ship/reference/git-ship.md

@@ -74,7 +74,9 @@ Pre-GO is read-only. Do not run the disclosed collapse or staging commands.
 2. **Exact staging.** Run `git add -- "$path"` once for each disclosed manifest
    row, passing each validated project-relative path as its own quoted argv
    element. Use no glob, directory, `-A`, `.env`, secret, out-of-scope path,
-   `eval`, or interpolated command string.
+   `eval`, or interpolated command string. A row that `git check-ignore -v --no-index`
+   matches, tracked or not, is disclosed and staged with `git add -f --`: plain
+   `git add` exits 1 on a named ignored path even after staging it.
 3. **Compare staged scope.** Compare the NUL-delimited output of
    `git diff --cached --name-status --no-renames -z` to the manifest's exact
    state/path set. `present` maps only to `A` or `M`; `deleted` maps only to `D`.

package/pack/generated/claude/skills/rite-build/reference/checkpoint.md

@@ -27,7 +27,10 @@ A native-worktree `transfer_commit` is transport on the worker branch only.
 ## The commit
 Stage the exact candidate paths from the manifest, each as its own argv.
 Never stage `touched-files.md`, a directory, glob, unrelated path, or user change.
-Verify the staged set, then commit locally.
+Before planning, run `git check-ignore -v --no-index -- <paths>`: every match, tracked
+or not, goes in the `git add -f --` list, because `git add` exits 1 on a named ignored
+path even after staging it. Keep each command's stderr. Verify the staged set, then
+commit locally.
 
 Subject: `WIP(<slug>):` plus an imperative summary of the change (from the
 goal). Never a slice id, `SLICE-###`, a slice number, or "this slice"

package/pack/generated/claude/skills/rite-ship/reference/git-ship.md

@@ -74,7 +74,9 @@ Pre-GO is read-only. Do not run the disclosed collapse or staging commands.
 2. **Exact staging.** Run `git add -- "$path"` once for each disclosed manifest
    row, passing each validated project-relative path as its own quoted argv
    element. Use no glob, directory, `-A`, `.env`, secret, out-of-scope path,
-   `eval`, or interpolated command string.
+   `eval`, or interpolated command string. A row that `git check-ignore -v --no-index`
+   matches, tracked or not, is disclosed and staged with `git add -f --`: plain
+   `git add` exits 1 on a named ignored path even after staging it.
 3. **Compare staged scope.** Compare the NUL-delimited output of
    `git diff --cached --name-status --no-renames -z` to the manifest's exact
    state/path set. `present` maps only to `A` or `M`; `deleted` maps only to `D`.

package/pack/generated/codex/skills/rite-build/reference/checkpoint.md

@@ -27,7 +27,10 @@ A native-worktree `transfer_commit` is transport on the worker branch only.
 ## The commit
 Stage the exact candidate paths from the manifest, each as its own argv.
 Never stage `touched-files.md`, a directory, glob, unrelated path, or user change.
-Verify the staged set, then commit locally.
+Before planning, run `git check-ignore -v --no-index -- <paths>`: every match, tracked
+or not, goes in the `git add -f --` list, because `git add` exits 1 on a named ignored
+path even after staging it. Keep each command's stderr. Verify the staged set, then
+commit locally.
 
 Subject: `WIP(<slug>):` plus an imperative summary of the change (from the
 goal). Never a slice id, `SLICE-###`, a slice number, or "this slice"

package/pack/generated/codex/skills/rite-ship/reference/git-ship.md

@@ -74,7 +74,9 @@ Pre-GO is read-only. Do not run the disclosed collapse or staging commands.
 2. **Exact staging.** Run `git add -- "$path"` once for each disclosed manifest
    row, passing each validated project-relative path as its own quoted argv
    element. Use no glob, directory, `-A`, `.env`, secret, out-of-scope path,
-   `eval`, or interpolated command string.
+   `eval`, or interpolated command string. A row that `git check-ignore -v --no-index`
+   matches, tracked or not, is disclosed and staged with `git add -f --`: plain
+   `git add` exits 1 on a named ignored path even after staging it.
 3. **Compare staged scope.** Compare the NUL-delimited output of
    `git diff --cached --name-status --no-renames -z` to the manifest's exact
    state/path set. `present` maps only to `A` or `M`; `deleted` maps only to `D`.

package/pack/generated/devin/skills/rite-build/reference/checkpoint.md

@@ -27,7 +27,10 @@ A native-worktree `transfer_commit` is transport on the worker branch only.
 ## The commit
 Stage the exact candidate paths from the manifest, each as its own argv.
 Never stage `touched-files.md`, a directory, glob, unrelated path, or user change.
-Verify the staged set, then commit locally.
+Before planning, run `git check-ignore -v --no-index -- <paths>`: every match, tracked
+or not, goes in the `git add -f --` list, because `git add` exits 1 on a named ignored
+path even after staging it. Keep each command's stderr. Verify the staged set, then
+commit locally.
 
 Subject: `WIP(<slug>):` plus an imperative summary of the change (from the
 goal). Never a slice id, `SLICE-###`, a slice number, or "this slice"

package/pack/generated/devin/skills/rite-ship/reference/git-ship.md

@@ -74,7 +74,9 @@ Pre-GO is read-only. Do not run the disclosed collapse or staging commands.
 2. **Exact staging.** Run `git add -- "$path"` once for each disclosed manifest
    row, passing each validated project-relative path as its own quoted argv
    element. Use no glob, directory, `-A`, `.env`, secret, out-of-scope path,
-   `eval`, or interpolated command string.
+   `eval`, or interpolated command string. A row that `git check-ignore -v --no-index`
+   matches, tracked or not, is disclosed and staged with `git add -f --`: plain
+   `git add` exits 1 on a named ignored path even after staging it.
 3. **Compare staged scope.** Compare the NUL-delimited output of
    `git diff --cached --name-status --no-renames -z` to the manifest's exact
    state/path set. `present` maps only to `A` or `M`; `deleted` maps only to `D`.

package/pack/generated/omp/skills/rite-build/reference/checkpoint.md

@@ -27,7 +27,10 @@ A native-worktree `transfer_commit` is transport on the worker branch only.
 ## The commit
 Stage the exact candidate paths from the manifest, each as its own argv.
 Never stage `touched-files.md`, a directory, glob, unrelated path, or user change.
-Verify the staged set, then commit locally.
+Before planning, run `git check-ignore -v --no-index -- <paths>`: every match, tracked
+or not, goes in the `git add -f --` list, because `git add` exits 1 on a named ignored
+path even after staging it. Keep each command's stderr. Verify the staged set, then
+commit locally.
 
 Subject: `WIP(<slug>):` plus an imperative summary of the change (from the
 goal). Never a slice id, `SLICE-###`, a slice number, or "this slice"

package/pack/generated/omp/skills/rite-ship/reference/git-ship.md

@@ -74,7 +74,9 @@ Pre-GO is read-only. Do not run the disclosed collapse or staging commands.
 2. **Exact staging.** Run `git add -- "$path"` once for each disclosed manifest
    row, passing each validated project-relative path as its own quoted argv
    element. Use no glob, directory, `-A`, `.env`, secret, out-of-scope path,
-   `eval`, or interpolated command string.
+   `eval`, or interpolated command string. A row that `git check-ignore -v --no-index`
+   matches, tracked or not, is disclosed and staged with `git add -f --`: plain
+   `git add` exits 1 on a named ignored path even after staging it.
 3. **Compare staged scope.** Compare the NUL-delimited output of
    `git diff --cached --name-status --no-renames -z` to the manifest's exact
    state/path set. `present` maps only to `A` or `M`; `deleted` maps only to `D`.

package/pack/generated/pi/skills/rite-build/reference/checkpoint.md

@@ -27,7 +27,10 @@ A native-worktree `transfer_commit` is transport on the worker branch only.
 ## The commit
 Stage the exact candidate paths from the manifest, each as its own argv.
 Never stage `touched-files.md`, a directory, glob, unrelated path, or user change.
-Verify the staged set, then commit locally.
+Before planning, run `git check-ignore -v --no-index -- <paths>`: every match, tracked
+or not, goes in the `git add -f --` list, because `git add` exits 1 on a named ignored
+path even after staging it. Keep each command's stderr. Verify the staged set, then
+commit locally.
 
 Subject: `WIP(<slug>):` plus an imperative summary of the change (from the
 goal). Never a slice id, `SLICE-###`, a slice number, or "this slice"

package/pack/generated/pi/skills/rite-ship/reference/git-ship.md

@@ -74,7 +74,9 @@ Pre-GO is read-only. Do not run the disclosed collapse or staging commands.
 2. **Exact staging.** Run `git add -- "$path"` once for each disclosed manifest
    row, passing each validated project-relative path as its own quoted argv
    element. Use no glob, directory, `-A`, `.env`, secret, out-of-scope path,
-   `eval`, or interpolated command string.
+   `eval`, or interpolated command string. A row that `git check-ignore -v --no-index`
+   matches, tracked or not, is disclosed and staged with `git add -f --`: plain
+   `git add` exits 1 on a named ignored path even after staging it.
 3. **Compare staged scope.** Compare the NUL-delimited output of
    `git diff --cached --name-status --no-renames -z` to the manifest's exact
    state/path set. `present` maps only to `A` or `M`; `deleted` maps only to `D`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "devrites",
-  "version": "6.4.3",
+  "version": "6.4.4",
   "description": "DevRites: a disciplined senior-engineer workflow pack for Claude Code, Codex, omp, pi, and Devin CLI",
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://github.com/ViktorsBaikers/DevRites#readme",