devrites 7.0.14 → 7.0.16

package/CHANGELOG.md

@@ -2,6 +2,18 @@
 
 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`.
 
+## [7.0.16](https://github.com/ViktorsBaikers/DevRites/compare/v7.0.15...v7.0.16) (2026-10-27)
+
+### Fixed
+
+* **devrites:** print the command that applies suggested triggers ([#175](https://github.com/ViktorsBaikers/DevRites/issues/175)) ([b32b2b8](https://github.com/ViktorsBaikers/DevRites/commit/b32b2b86de8c4d66a9dfd51f23ae22b683f90979))
+
+## [7.0.15](https://github.com/ViktorsBaikers/DevRites/compare/v7.0.14...v7.0.15) (2026-10-25)
+
+### Fixed
+
+* **devrites:** keep duplicate reviews read-only ([#173](https://github.com/ViktorsBaikers/DevRites/issues/173)) ([602da4b](https://github.com/ViktorsBaikers/DevRites/commit/602da4bba7d020a1abdbc71a563c870ea4287141))
+
 ## [7.0.14](https://github.com/ViktorsBaikers/DevRites/compare/v7.0.13...v7.0.14) (2026-10-25)
 
 ### 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:** [`v7.0.14`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v7.0.14): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
+**Status:** [`v7.0.16`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v7.0.16): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
 
 This is the latest published release; `main` may contain unreleased work.
 

package/engine/internal/lib/context.go

@@ -396,6 +396,9 @@ func RunContext(root string, args []string, stdout, stderr io.Writer) int {
 		if suggested := suggestTriggers(manifest, root, featureDir, opts); len(suggested) > 0 {
 			fmt.Fprintf(stdout, "triggers: suggested=[%s] (advisory — confirm each before use)\n",
 				strings.Join(suggested, ","))
+			// The advisory list is only actionable if the agent is told how to
+			// apply it; no shipped guidance names the flag.
+			fmt.Fprintf(stdout, "triggers: apply with: %s\n", triggerApplyCommand(opts, suggested))
 		}
 	}
 	if len(missingRequired) > 0 {

package/engine/internal/lib/triggers.go

@@ -156,3 +156,26 @@ func afkAllowsParallel(content string) bool {
 	}
 	return n > 1
 }
+
+// triggerApplyCommand renders the command that applies the suggested triggers.
+// The suggestions are never applied automatically (see the file header), so the
+// agent needs a copy-pasteable form or the advisory list has no consumer.
+func triggerApplyCommand(opts contextOpts, suggested []string) string {
+	parts := []string{"devrites-engine", "context"}
+	if opts.slug != "" {
+		parts = append(parts, opts.slug)
+	}
+	for _, flag := range []struct{ name, value string }{
+		{"--phase", opts.phase},
+		{"--skill", opts.skill},
+		{"--role", opts.role},
+		{"--slice", opts.slice},
+		{"--out", opts.out},
+	} {
+		if flag.value != "" {
+			parts = append(parts, flag.name, flag.value)
+		}
+	}
+	parts = append(parts, "--trigger", strings.Join(suggested, ","))
+	return strings.Join(parts, " ")
+}

package/pack/.claude/agents/devrites-code-reviewer.md

@@ -87,10 +87,9 @@ from your side.
     cast, or silent fallback that hides an unclear invariant?
   - Are repository/deployable roots, canonical contract and mutable-state ownership,
     shared resources, and sync/async consistency boundaries preserved without a cycle?
-  - Run `devrites-engine check dup <slug>` for near-duplicate leads, using the
-    mode that matches the packet's diff: `--base <ref>` when the feature's work
-    is committed, `--staged`/`--worktree` for uncommitted diffs. Triage each
-    reported cluster per
+  - Run `devrites-engine check dup` without a feature slug, following the
+    [read-only scan rule](../skills/devrites-lib/reference/standards/code-review.md).
+    Triage each reported cluster per
     [`duplicate-code.md`](../skills/devrites-lib/reference/standards/duplicate-code.md)
     — merge, keep-with-reason, or watch. A `*`-marked unit the diff added needs a
     verdict, not suppression.

package/pack/.claude/skills/devrites-lib/reference/standards/code-review.md

@@ -40,9 +40,9 @@ If it does not, do not merge it.
    Search for a **reimplemented-elsewhere** twin: a new function/module that
    semantically duplicates an existing one (renamed, reshaped, or vendored) is an
    architecture finding; reuse the canonical implementation or justify the fork.
-   Run `devrites-engine check dup` in the mode matching the diff (`--base <ref>`
-   for committed work, `--staged`/`--worktree` for uncommitted) for leads and
-   triage each cluster per [`duplicate-code.md`](duplicate-code.md).
+   Run read-only advisory `devrites-engine check dup` without a slug (no metrics):
+   `--base <ref>` committed; `--staged`/`--worktree` uncommitted. Triage each
+   cluster. Caller bans apply; unavailable scans remain gaps.
 6. **Security:** trust boundaries, input validation, authz, secrets.
 7. **Risk:** migrations, destructive changes, rollback.
 8. **Read depth matches risk:** the review's `Basis` names **full reads of the largest

package/pack/generated/claude/agents/devrites-code-reviewer.md

@@ -93,10 +93,9 @@ from your side.
     cast, or silent fallback that hides an unclear invariant?
   - Are repository/deployable roots, canonical contract and mutable-state ownership,
     shared resources, and sync/async consistency boundaries preserved without a cycle?
-  - Run `devrites-engine check dup <slug>` for near-duplicate leads, using the
-    mode that matches the packet's diff: `--base <ref>` when the feature's work
-    is committed, `--staged`/`--worktree` for uncommitted diffs. Triage each
-    reported cluster per
+  - Run `devrites-engine check dup` without a feature slug, following the
+    [read-only scan rule](../skills/devrites-lib/reference/standards/code-review.md).
+    Triage each reported cluster per
     [`duplicate-code.md`](../skills/devrites-lib/reference/standards/duplicate-code.md)
     — merge, keep-with-reason, or watch. A `*`-marked unit the diff added needs a
     verdict, not suppression.

package/pack/generated/claude/skills/devrites-lib/reference/standards/code-review.md

@@ -40,9 +40,9 @@ If it does not, do not merge it.
    Search for a **reimplemented-elsewhere** twin: a new function/module that
    semantically duplicates an existing one (renamed, reshaped, or vendored) is an
    architecture finding; reuse the canonical implementation or justify the fork.
-   Run `devrites-engine check dup` in the mode matching the diff (`--base <ref>`
-   for committed work, `--staged`/`--worktree` for uncommitted) for leads and
-   triage each cluster per [`duplicate-code.md`](duplicate-code.md).
+   Run read-only advisory `devrites-engine check dup` without a slug (no metrics):
+   `--base <ref>` committed; `--staged`/`--worktree` uncommitted. Triage each
+   cluster. Caller bans apply; unavailable scans remain gaps.
 6. **Security:** trust boundaries, input validation, authz, secrets.
 7. **Risk:** migrations, destructive changes, rollback.
 8. **Read depth matches risk:** the review's `Basis` names **full reads of the largest

package/pack/generated/codex/agents/devrites-code-reviewer.toml

@@ -91,10 +91,9 @@ from your side.
     cast, or silent fallback that hides an unclear invariant?
   - Are repository/deployable roots, canonical contract and mutable-state ownership,
     shared resources, and sync/async consistency boundaries preserved without a cycle?
-  - Run `devrites-engine check dup <slug>` for near-duplicate leads, using the
-    mode that matches the packet's diff: `--base <ref>` when the feature's work
-    is committed, `--staged`/`--worktree` for uncommitted diffs. Triage each
-    reported cluster per
+  - Run `devrites-engine check dup` without a feature slug, following the
+    [read-only scan rule](.agents/skills/devrites-lib/reference/standards/code-review.md).
+    Triage each reported cluster per
     [`duplicate-code.md`](.agents/skills/devrites-lib/reference/standards/duplicate-code.md)
     — merge, keep-with-reason, or watch. A `*`-marked unit the diff added needs a
     verdict, not suppression.

package/pack/generated/codex/skills/devrites-lib/reference/standards/code-review.md

@@ -40,9 +40,9 @@ If it does not, do not merge it.
    Search for a **reimplemented-elsewhere** twin: a new function/module that
    semantically duplicates an existing one (renamed, reshaped, or vendored) is an
    architecture finding; reuse the canonical implementation or justify the fork.
-   Run `devrites-engine check dup` in the mode matching the diff (`--base <ref>`
-   for committed work, `--staged`/`--worktree` for uncommitted) for leads and
-   triage each cluster per [`duplicate-code.md`](duplicate-code.md).
+   Run read-only advisory `devrites-engine check dup` without a slug (no metrics):
+   `--base <ref>` committed; `--staged`/`--worktree` uncommitted. Triage each
+   cluster. Caller bans apply; unavailable scans remain gaps.
 6. **Security:** trust boundaries, input validation, authz, secrets.
 7. **Risk:** migrations, destructive changes, rollback.
 8. **Read depth matches risk:** the review's `Basis` names **full reads of the largest

package/pack/generated/devin/agents/devrites-code-reviewer.md

@@ -95,10 +95,9 @@ from your side.
     cast, or silent fallback that hides an unclear invariant?
   - Are repository/deployable roots, canonical contract and mutable-state ownership,
     shared resources, and sync/async consistency boundaries preserved without a cycle?
-  - Run `devrites-engine check dup <slug>` for near-duplicate leads, using the
-    mode that matches the packet's diff: `--base <ref>` when the feature's work
-    is committed, `--staged`/`--worktree` for uncommitted diffs. Triage each
-    reported cluster per
+  - Run `devrites-engine check dup` without a feature slug, following the
+    [read-only scan rule](../skills/devrites-lib/reference/standards/code-review.md).
+    Triage each reported cluster per
     [`duplicate-code.md`](../skills/devrites-lib/reference/standards/duplicate-code.md)
     — merge, keep-with-reason, or watch. A `*`-marked unit the diff added needs a
     verdict, not suppression.

package/pack/generated/devin/skills/devrites-lib/reference/standards/code-review.md

@@ -40,9 +40,9 @@ If it does not, do not merge it.
    Search for a **reimplemented-elsewhere** twin: a new function/module that
    semantically duplicates an existing one (renamed, reshaped, or vendored) is an
    architecture finding; reuse the canonical implementation or justify the fork.
-   Run `devrites-engine check dup` in the mode matching the diff (`--base <ref>`
-   for committed work, `--staged`/`--worktree` for uncommitted) for leads and
-   triage each cluster per [`duplicate-code.md`](duplicate-code.md).
+   Run read-only advisory `devrites-engine check dup` without a slug (no metrics):
+   `--base <ref>` committed; `--staged`/`--worktree` uncommitted. Triage each
+   cluster. Caller bans apply; unavailable scans remain gaps.
 6. **Security:** trust boundaries, input validation, authz, secrets.
 7. **Risk:** migrations, destructive changes, rollback.
 8. **Read depth matches risk:** the review's `Basis` names **full reads of the largest

package/pack/generated/omp/agents/devrites-code-reviewer.md

@@ -91,10 +91,9 @@ from your side.
     cast, or silent fallback that hides an unclear invariant?
   - Are repository/deployable roots, canonical contract and mutable-state ownership,
     shared resources, and sync/async consistency boundaries preserved without a cycle?
-  - Run `devrites-engine check dup <slug>` for near-duplicate leads, using the
-    mode that matches the packet's diff: `--base <ref>` when the feature's work
-    is committed, `--staged`/`--worktree` for uncommitted diffs. Triage each
-    reported cluster per
+  - Run `devrites-engine check dup` without a feature slug, following the
+    [read-only scan rule](skill://devrites-lib/reference/standards/code-review.md).
+    Triage each reported cluster per
     [`duplicate-code.md`](skill://devrites-lib/reference/standards/duplicate-code.md)
     — merge, keep-with-reason, or watch. A `*`-marked unit the diff added needs a
     verdict, not suppression.

package/pack/generated/omp/skills/devrites-lib/reference/standards/code-review.md

@@ -40,9 +40,9 @@ If it does not, do not merge it.
    Search for a **reimplemented-elsewhere** twin: a new function/module that
    semantically duplicates an existing one (renamed, reshaped, or vendored) is an
    architecture finding; reuse the canonical implementation or justify the fork.
-   Run `devrites-engine check dup` in the mode matching the diff (`--base <ref>`
-   for committed work, `--staged`/`--worktree` for uncommitted) for leads and
-   triage each cluster per [`duplicate-code.md`](duplicate-code.md).
+   Run read-only advisory `devrites-engine check dup` without a slug (no metrics):
+   `--base <ref>` committed; `--staged`/`--worktree` uncommitted. Triage each
+   cluster. Caller bans apply; unavailable scans remain gaps.
 6. **Security:** trust boundaries, input validation, authz, secrets.
 7. **Risk:** migrations, destructive changes, rollback.
 8. **Read depth matches risk:** the review's `Basis` names **full reads of the largest

package/pack/generated/pi/agents/devrites-code-reviewer.md

@@ -92,10 +92,9 @@ from your side.
     cast, or silent fallback that hides an unclear invariant?
   - Are repository/deployable roots, canonical contract and mutable-state ownership,
     shared resources, and sync/async consistency boundaries preserved without a cycle?
-  - Run `devrites-engine check dup <slug>` for near-duplicate leads, using the
-    mode that matches the packet's diff: `--base <ref>` when the feature's work
-    is committed, `--staged`/`--worktree` for uncommitted diffs. Triage each
-    reported cluster per
+  - Run `devrites-engine check dup` without a feature slug, following the
+    [read-only scan rule](../skills/devrites-lib/reference/standards/code-review.md).
+    Triage each reported cluster per
     [`duplicate-code.md`](../skills/devrites-lib/reference/standards/duplicate-code.md)
     — merge, keep-with-reason, or watch. A `*`-marked unit the diff added needs a
     verdict, not suppression.

package/pack/generated/pi/skills/devrites-lib/reference/standards/code-review.md

@@ -40,9 +40,9 @@ If it does not, do not merge it.
    Search for a **reimplemented-elsewhere** twin: a new function/module that
    semantically duplicates an existing one (renamed, reshaped, or vendored) is an
    architecture finding; reuse the canonical implementation or justify the fork.
-   Run `devrites-engine check dup` in the mode matching the diff (`--base <ref>`
-   for committed work, `--staged`/`--worktree` for uncommitted) for leads and
-   triage each cluster per [`duplicate-code.md`](duplicate-code.md).
+   Run read-only advisory `devrites-engine check dup` without a slug (no metrics):
+   `--base <ref>` committed; `--staged`/`--worktree` uncommitted. Triage each
+   cluster. Caller bans apply; unavailable scans remain gaps.
 6. **Security:** trust boundaries, input validation, authz, secrets.
 7. **Risk:** migrations, destructive changes, rollback.
 8. **Read depth matches risk:** the review's `Basis` names **full reads of the largest

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "devrites",
-  "version": "7.0.14",
+  "version": "7.0.16",
   "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",