@olegkoval/agent-skills 1.71.2 → 1.73.0

package/adapters/claude/olko-github-pr/skills/lekker-review/SKILL.md

@@ -434,7 +434,7 @@ skip the review because the log failed, just say `run log unavailable`.
 | Context: issue-tracker/CI/diff/existing-reviews | always | always | always | always |
 | Context: chat/docs/framework-docs/monitoring/prior-review-memory (optional, MCP-dependent) | skip | skip | included | included + broader recall |
 | Worktree + static checks    | included (`npm ci` per changed lockfile) | skip (WORKTREE_PATH=null) unless `--fix` | included | included          |
-| Review agents               | 1 deps checklist      | 2 triage (haiku)      | 5 specialists (sonnet) | 5 specialists (sonnet)  |
+| Review agents               | 1 deps checklist      | 2 triage (haiku) + project-rules (sonnet) | 5 specialists + project-rules (sonnet) | 5 specialists + project-rules (sonnet)  |
 | Per-finding verification    | none                  | Criticals + Importants | Criticals + Importants | Criticals + Importants |
 | Completeness critic         | skip                  | skip                  | skip                | included                   |
 | Proof-of-bug (failing test per Critical or composed-boundary Important) | skip | skip | included (max 5)    | included (max 5)           |
@@ -767,8 +767,8 @@ must pass it, or the workflow throws on its missing-args guard.
 
 Two optional args tune concurrency; omit both unless a run needs it:
 
-- `reviewBatchPlan` - batch sizes for the review dimensions, default `[5]`
-  (all five at once). The last entry repeats to cover any remainder, so
+- `reviewBatchPlan` - batch sizes for the review dimensions, default `[6]`
+  (all six at once). The last entry repeats to cover any remainder, so
   `[2]` would mean two at a time.
 - `maxConcurrent` - cap for the per-finding fan-outs (verify, critic, prove),
   default `5`.
@@ -780,8 +780,9 @@ The workflow runs three phases:
 
 - **Review:** deps uses the single `deps` checklist agent; scan uses `[triage-quality, triage-logic]` on `haiku`; medium/deep
   use 5 specialists (quality, implementation, simplification, conventions,
-  test-quality) on `sonnet`. Agents receive DIFF_FILE + CONTEXT_FILE by path.
-  All five run concurrently: the stage is self-limiting at one agent per
+  test-quality) on `sonnet`. Scan, medium and deep also run `project-rules`
+  (sonnet), which only checks the diff against each project rule. Agents receive DIFF_FILE + CONTEXT_FILE by path.
+  All run concurrently: the stage is self-limiting at one agent per
   dimension. All reviewers run to completion before verification starts.
   Override per run with the `reviewBatchPlan` arg (e.g. `[1]` runs them
   strictly one at a time on a constrained machine).

package/adapters/claude/olko-github-pr/skills/lekker-review/references/agents/project-rules.md

@@ -0,0 +1,48 @@
+# project-rules: lekker-review agent prompt
+You will receive in your task message: REPO_SLUG, PR_NUMBER, PR_URL, DIFF_FILE, CONTEXT_FILE (JSON), WORKTREE_PATH (may be null).
+Your findings are returned via the StructuredOutput schema enforced by the caller.
+
+You are the project-rules reviewer. Your only job is to find changed lines that
+break the repository's own written rules. Report nothing else: no general bugs,
+no style, no suggestions. Other agents cover those.
+
+Procedure:
+1. Read CONTEXT_FILE. The authoritative rules are "baseProjectRules" when it is a
+   string (the base branch's copy, which the PR author cannot edit), otherwise
+   "projectRules". When the chosen source is missing or empty, return
+   `{"findings": []}` and stop.
+2. List every rule written as a prohibition or an obligation (NEVER, MUST,
+   MUST NOT, ALWAYS, DO NOT, or a plain-English equivalent). Work through the
+   whole source: a rule buried in a long file counts exactly as much as the
+   first one. Preferences and suggestions are not rules.
+3. Read DIFF_FILE. For EACH listed rule, check every `+` line against it. Do not
+   rely on skimming: go rule by rule.
+4. When a rule has a mechanical signature (a literal string, API or function
+   name, import, file pattern, naming pattern, template-literal shape), derive
+   the pattern and search the diff for it (grep or Bash is allowed) instead of
+   relying on reading. Check added file paths in the diff headers too.
+5. A rule is broken by a `+` line (or an added file). Unchanged code is out of
+   scope.
+6. Separately, when "baseProjectRules" is a string, check every `-` line in
+   DIFF_FILE against its rule lines (including the rules files themselves, such
+   as CLAUDE.md or AGENTS.md). A rule line that is removed, or reworded so it
+   forbids or requires less (a NEVER softened to a preference, a dropped
+   exception list, a narrowed scope), is a breach even when no `+` line violates
+   anything. The PR's own copy cannot clear it: compare against the base copy.
+
+Reporting contract (same as the PROJECT RULES AS HARD RULES instruction below):
+- One finding per broken rule, Critical, `rule` set to `PROJECT:<short-kebab-slug>`,
+  `ruleQuote` set to the exact sentence from the authoritative source, file:line on
+  the first violating line, every other violating site in `otherInstances`.
+- When the diff deletes or weakens a rule line that is in "baseProjectRules"
+  (procedure step 6), report an Important finding with `rule`
+  "weakens-project-rule", `ruleQuote` set to the exact base-branch sentence,
+  file:line on the removed or reworded line, and `badCode` set to the verbatim
+  `-` line (plus the replacing `+` line when there is one). `fix` is to restore
+  the rule or to state why the project dropped it.
+- Never quote a rule that is not in the authoritative source.
+- `badCode` is REQUIRED: the verbatim violating line copied from the diff. `fix`
+  is REQUIRED: a concrete drop-in replacement that follows the rule. If you cannot
+  quote and fix it, drop it.
+
+CI status, acceptance criteria and existing reviews are not your concern.

package/adapters/claude/olko-github-pr/skills/lekker-review/references/codex-workflow.md

@@ -66,9 +66,9 @@ unavailable; do not infer what it meant from prose.
 Select dimensions exactly as the Claude workflow does:
 
 - deps: `deps` (single checklist agent; no verifier, no prover)
-- scan: `triage-quality`, `triage-logic`
+- scan: `triage-quality`, `triage-logic`, `project-rules`
 - medium/deep: `quality`, `implementation`, `simplification`, `conventions`,
-  `test-quality`
+  `test-quality`, `project-rules`
 
 For each dimension, spawn a `default` read-only agent with the following
 bounded task:

package/adapters/claude/olko-github-pr/skills/lekker-review/references/github-post.md

@@ -104,6 +104,38 @@ Rules:
   Keep the body itself under ~2,500 characters. If it is longer, the asks are
   buried: cut prose, never cut the numbered asks.
 
+  **Open-source footer:** when the repo is open source, append the footer
+  below after the last section of the body and before the closer. Never add it
+  to a private repo. Open source means the repo is public:
+  `gh repo view <REPO_SLUG> --json isPrivate --jq '.isPrivate|not'`
+  must print `true`. Any other output (private, error) means no footer. Run
+  this check in the same command sequence that writes the payload, immediately
+  before posting, and build the footer from that result alone: never reuse an
+  earlier visibility answer. Never add it to inline comments. It does not count toward the
+  ~2,500-character budget, and it carries no praise, so the no-praise rule below
+  is not affected. Post it verbatim, with no em dashes:
+
+  ````markdown
+  ---
+  <sub>Reviewed with the [lekker-review skill](https://github.com/oleg-koval/agent-skills/tree/main/plugins/olko-github-pr/skills/lekker-review) · [skills.olegkoval.com](https://skills.olegkoval.com)</sub>
+
+  <details>
+  <summary>Install the review skill</summary>
+
+  In Claude Code:
+
+  ```
+  /plugin marketplace add oleg-koval/agent-skills
+  /plugin install olko-github-pr@olko-agent-skills
+  ```
+
+  Then run `/olko-github-pr:lekker-review <PR url>`.
+
+  - Skill source: https://github.com/oleg-koval/agent-skills/tree/main/plugins/olko-github-pr/skills/lekker-review
+  - Catalog and other install options: https://skills.olegkoval.com
+  </details>
+  ````
+
   **Closer:** when `CLOSER` is set (SKILL.md Step 3), append a blank line and
   `CLOSER.md_github` as the very last lines of the body. It does not count
   toward the ~2,500-character budget and is exempt from the no-praise rule
@@ -201,7 +233,11 @@ If the user asks to shorten, reword, or re-scope the comments after posting:
 
 - The review-level `body` alone can be edited in place:
   `gh api repos/<REPO_SLUG>/pulls/<PR_NUMBER>/reviews/<REVIEW_ID> --method PUT --input <json with {"body": ...}>`
-  Inline comments survive this untouched.
+  Inline comments survive this untouched. A body-only PUT replaces the whole
+  body, so the replacement must carry the footer again: re-run the visibility
+  check from Step 1 and append the footer after the last section (before the
+  closer) when the repo is public, and leave it out when it is not. Never keep
+  the footer from the old body without rechecking.
 - **Inline comment bodies cannot be reliably edited on a pending review** --
   `PATCH /pulls/comments/{id}` targets submitted comments. To change them,
   DELETE the pending review and POST a fresh one:

package/adapters/claude/olko-github-pr/skills/lekker-review/scripts/selftest.mjs

@@ -335,8 +335,8 @@ console.log('\ndeps depth: routing, classifier, line validation')
     const dimensionsFor = new Function(dimsSrc + '\nreturn dimensionsFor')()
     const M = { review: 'r', triage: 't' }
     check('deps runs exactly one agent', dimensionsFor('deps', M).map(d => d.file), ['deps.md'])
-    check('scan still runs the triage pair', dimensionsFor('scan', M).length, 2)
-    check('medium still runs five specialists', dimensionsFor('medium', M).length, 5)
+    check('scan runs the triage pair plus project-rules', dimensionsFor('scan', M).map(d => d.key), ['triage-quality', 'triage-logic', 'project-rules'])
+    check('medium runs five specialists plus project-rules', dimensionsFor('medium', M).length, 6)
     check('every dimension prompt file exists',
       ['deps', 'scan', 'medium'].flatMap(d => dimensionsFor(d, M)).every(d => existsSync(join(SKILL, 'references', 'agents', d.file))), true)
   }
@@ -871,7 +871,8 @@ function liftBlock(name) {
 const liftBlockOr = name => { try { return liftBlock(name) } catch { return `const ${name} = ''\n` } }
 const buildPrompt = new Function(
   'dim', 'SUPPRESSED', 'prevSha',
-  [liftBlockOr('PROJECT_RULE_DIMENSIONS'), liftBlockOr('PROJECT_RULE_INSTRUCTION'), liftConst('BUG_CLASS_INSTRUCTION'),
+  [liftBlockOr('PROJECT_RULE_DIMENSIONS'), liftBlockOr('PROJECT_RULE_CORE'), liftBlockOr('IGNORE_ENTRY_NOTE'),
+    liftBlockOr('PROJECT_RULE_INSTRUCTION'), liftBlockOr('PROJECT_RULE_ONLY_INSTRUCTION'), liftConst('BUG_CLASS_INSTRUCTION'),
     `const targetMetadata = '{}', promptDir = 'p', repoSlug = 'o/r', prNumber = 1, prUrl = 'u',
        diffFile = 'd', contextFile = 'c', wtDisplay = 'w'`,
     lift('reviewPrompt'), 'return reviewPrompt(dim)'].join('\n'),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@olegkoval/agent-skills",
-  "version": "1.71.2",
+  "version": "1.73.0",
   "private": false,
   "publishConfig": {
     "access": "public"

package/plugins/olko-apple-kit/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-apple-kit",
   "description": "Build and ship Apple platform apps: macOS menubar apps, App Store submissions.",
-  "version": "1.71.2",
+  "version": "1.73.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-creative/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-creative",
   "description": "Creative and personal projects: photo galleries, music players, listings, wiki editing.",
-  "version": "1.71.2",
+  "version": "1.73.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-garmin-kit/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-garmin-kit",
   "description": "Build, test and publish Garmin Connect IQ watch faces.",
-  "version": "1.71.2",
+  "version": "1.73.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-git-tools/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-git-tools",
   "description": "Everyday git and GitHub CLI operations: conventional commits, branch hygiene.",
-  "version": "1.71.2",
+  "version": "1.73.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-github-pr/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-github-pr",
   "description": "Drive GitHub pull requests to merge-ready: review-bot loops, CI fixes, descriptions, dependency triage.",
-  "version": "1.71.2",
+  "version": "1.73.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-github-pr/skills/lekker-review/README.md

@@ -2,8 +2,8 @@
 
 FAANG-quality PR code review for GitHub. It gathers the context a human reviewer
 would gather and checks the branch out into an isolated worktree when the depth
-requires one. `scan` runs two triage agents. `medium` and
-`deep` run five specialists and attempt proofs for at most five non-rule
+requires one. `scan` runs two triage agents plus project-rules. `medium` and
+`deep` run five specialists plus project-rules and attempt proofs for at most five non-rule
 Critical findings.
 
 ![lekker-review at a glance](assets/poster-overview.png)

package/plugins/olko-github-pr/skills/lekker-review/SKILL.md

@@ -433,7 +433,7 @@ skip the review because the log failed, just say `run log unavailable`.
 | Context: issue-tracker/CI/diff/existing-reviews | always | always | always | always |
 | Context: chat/docs/framework-docs/monitoring/prior-review-memory (optional, MCP-dependent) | skip | skip | included | included + broader recall |
 | Worktree + static checks    | included (`npm ci` per changed lockfile) | skip (WORKTREE_PATH=null) unless `--fix` | included | included          |
-| Review agents               | 1 deps checklist      | 2 triage (haiku)      | 5 specialists (sonnet) | 5 specialists (sonnet)  |
+| Review agents               | 1 deps checklist      | 2 triage (haiku) + project-rules (sonnet) | 5 specialists + project-rules (sonnet) | 5 specialists + project-rules (sonnet)  |
 | Per-finding verification    | none                  | Criticals + Importants | Criticals + Importants | Criticals + Importants |
 | Completeness critic         | skip                  | skip                  | skip                | included                   |
 | Proof-of-bug (failing test per Critical or composed-boundary Important) | skip | skip | included (max 5)    | included (max 5)           |
@@ -766,8 +766,8 @@ must pass it, or the workflow throws on its missing-args guard.
 
 Two optional args tune concurrency; omit both unless a run needs it:
 
-- `reviewBatchPlan` - batch sizes for the review dimensions, default `[5]`
-  (all five at once). The last entry repeats to cover any remainder, so
+- `reviewBatchPlan` - batch sizes for the review dimensions, default `[6]`
+  (all six at once). The last entry repeats to cover any remainder, so
   `[2]` would mean two at a time.
 - `maxConcurrent` - cap for the per-finding fan-outs (verify, critic, prove),
   default `5`.
@@ -779,8 +779,9 @@ The workflow runs three phases:
 
 - **Review:** deps uses the single `deps` checklist agent; scan uses `[triage-quality, triage-logic]` on `haiku`; medium/deep
   use 5 specialists (quality, implementation, simplification, conventions,
-  test-quality) on `sonnet`. Agents receive DIFF_FILE + CONTEXT_FILE by path.
-  All five run concurrently: the stage is self-limiting at one agent per
+  test-quality) on `sonnet`. Scan, medium and deep also run `project-rules`
+  (sonnet), which only checks the diff against each project rule. Agents receive DIFF_FILE + CONTEXT_FILE by path.
+  All run concurrently: the stage is self-limiting at one agent per
   dimension. All reviewers run to completion before verification starts.
   Override per run with the `reviewBatchPlan` arg (e.g. `[1]` runs them
   strictly one at a time on a constrained machine).

package/plugins/olko-github-pr/skills/lekker-review/references/agents/project-rules.md

@@ -0,0 +1,48 @@
+# project-rules: lekker-review agent prompt
+You will receive in your task message: REPO_SLUG, PR_NUMBER, PR_URL, DIFF_FILE, CONTEXT_FILE (JSON), WORKTREE_PATH (may be null).
+Your findings are returned via the StructuredOutput schema enforced by the caller.
+
+You are the project-rules reviewer. Your only job is to find changed lines that
+break the repository's own written rules. Report nothing else: no general bugs,
+no style, no suggestions. Other agents cover those.
+
+Procedure:
+1. Read CONTEXT_FILE. The authoritative rules are "baseProjectRules" when it is a
+   string (the base branch's copy, which the PR author cannot edit), otherwise
+   "projectRules". When the chosen source is missing or empty, return
+   `{"findings": []}` and stop.
+2. List every rule written as a prohibition or an obligation (NEVER, MUST,
+   MUST NOT, ALWAYS, DO NOT, or a plain-English equivalent). Work through the
+   whole source: a rule buried in a long file counts exactly as much as the
+   first one. Preferences and suggestions are not rules.
+3. Read DIFF_FILE. For EACH listed rule, check every `+` line against it. Do not
+   rely on skimming: go rule by rule.
+4. When a rule has a mechanical signature (a literal string, API or function
+   name, import, file pattern, naming pattern, template-literal shape), derive
+   the pattern and search the diff for it (grep or Bash is allowed) instead of
+   relying on reading. Check added file paths in the diff headers too.
+5. A rule is broken by a `+` line (or an added file). Unchanged code is out of
+   scope.
+6. Separately, when "baseProjectRules" is a string, check every `-` line in
+   DIFF_FILE against its rule lines (including the rules files themselves, such
+   as CLAUDE.md or AGENTS.md). A rule line that is removed, or reworded so it
+   forbids or requires less (a NEVER softened to a preference, a dropped
+   exception list, a narrowed scope), is a breach even when no `+` line violates
+   anything. The PR's own copy cannot clear it: compare against the base copy.
+
+Reporting contract (same as the PROJECT RULES AS HARD RULES instruction below):
+- One finding per broken rule, Critical, `rule` set to `PROJECT:<short-kebab-slug>`,
+  `ruleQuote` set to the exact sentence from the authoritative source, file:line on
+  the first violating line, every other violating site in `otherInstances`.
+- When the diff deletes or weakens a rule line that is in "baseProjectRules"
+  (procedure step 6), report an Important finding with `rule`
+  "weakens-project-rule", `ruleQuote` set to the exact base-branch sentence,
+  file:line on the removed or reworded line, and `badCode` set to the verbatim
+  `-` line (plus the replacing `+` line when there is one). `fix` is to restore
+  the rule or to state why the project dropped it.
+- Never quote a rule that is not in the authoritative source.
+- `badCode` is REQUIRED: the verbatim violating line copied from the diff. `fix`
+  is REQUIRED: a concrete drop-in replacement that follows the rule. If you cannot
+  quote and fix it, drop it.
+
+CI status, acceptance criteria and existing reviews are not your concern.

package/plugins/olko-github-pr/skills/lekker-review/references/codex-workflow.md

@@ -66,9 +66,9 @@ unavailable; do not infer what it meant from prose.
 Select dimensions exactly as the Claude workflow does:
 
 - deps: `deps` (single checklist agent; no verifier, no prover)
-- scan: `triage-quality`, `triage-logic`
+- scan: `triage-quality`, `triage-logic`, `project-rules`
 - medium/deep: `quality`, `implementation`, `simplification`, `conventions`,
-  `test-quality`
+  `test-quality`, `project-rules`
 
 For each dimension, spawn a `default` read-only agent with the following
 bounded task:

package/plugins/olko-github-pr/skills/lekker-review/references/github-post.md

@@ -104,6 +104,38 @@ Rules:
   Keep the body itself under ~2,500 characters. If it is longer, the asks are
   buried: cut prose, never cut the numbered asks.
 
+  **Open-source footer:** when the repo is open source, append the footer
+  below after the last section of the body and before the closer. Never add it
+  to a private repo. Open source means the repo is public:
+  `gh repo view <REPO_SLUG> --json isPrivate --jq '.isPrivate|not'`
+  must print `true`. Any other output (private, error) means no footer. Run
+  this check in the same command sequence that writes the payload, immediately
+  before posting, and build the footer from that result alone: never reuse an
+  earlier visibility answer. Never add it to inline comments. It does not count toward the
+  ~2,500-character budget, and it carries no praise, so the no-praise rule below
+  is not affected. Post it verbatim, with no em dashes:
+
+  ````markdown
+  ---
+  <sub>Reviewed with the [lekker-review skill](https://github.com/oleg-koval/agent-skills/tree/main/plugins/olko-github-pr/skills/lekker-review) · [skills.olegkoval.com](https://skills.olegkoval.com)</sub>
+
+  <details>
+  <summary>Install the review skill</summary>
+
+  In Claude Code:
+
+  ```
+  /plugin marketplace add oleg-koval/agent-skills
+  /plugin install olko-github-pr@olko-agent-skills
+  ```
+
+  Then run `/olko-github-pr:lekker-review <PR url>`.
+
+  - Skill source: https://github.com/oleg-koval/agent-skills/tree/main/plugins/olko-github-pr/skills/lekker-review
+  - Catalog and other install options: https://skills.olegkoval.com
+  </details>
+  ````
+
   **Closer:** when `CLOSER` is set (SKILL.md Step 3), append a blank line and
   `CLOSER.md_github` as the very last lines of the body. It does not count
   toward the ~2,500-character budget and is exempt from the no-praise rule
@@ -201,7 +233,11 @@ If the user asks to shorten, reword, or re-scope the comments after posting:
 
 - The review-level `body` alone can be edited in place:
   `gh api repos/<REPO_SLUG>/pulls/<PR_NUMBER>/reviews/<REVIEW_ID> --method PUT --input <json with {"body": ...}>`
-  Inline comments survive this untouched.
+  Inline comments survive this untouched. A body-only PUT replaces the whole
+  body, so the replacement must carry the footer again: re-run the visibility
+  check from Step 1 and append the footer after the last section (before the
+  closer) when the repo is public, and leave it out when it is not. Never keep
+  the footer from the old body without rechecking.
 - **Inline comment bodies cannot be reliably edited on a pending review** --
   `PATCH /pulls/comments/{id}` targets submitted comments. To change them,
   DELETE the pending review and POST a fresh one:

package/plugins/olko-github-pr/skills/lekker-review/scripts/selftest.mjs

@@ -335,8 +335,8 @@ console.log('\ndeps depth: routing, classifier, line validation')
     const dimensionsFor = new Function(dimsSrc + '\nreturn dimensionsFor')()
     const M = { review: 'r', triage: 't' }
     check('deps runs exactly one agent', dimensionsFor('deps', M).map(d => d.file), ['deps.md'])
-    check('scan still runs the triage pair', dimensionsFor('scan', M).length, 2)
-    check('medium still runs five specialists', dimensionsFor('medium', M).length, 5)
+    check('scan runs the triage pair plus project-rules', dimensionsFor('scan', M).map(d => d.key), ['triage-quality', 'triage-logic', 'project-rules'])
+    check('medium runs five specialists plus project-rules', dimensionsFor('medium', M).length, 6)
     check('every dimension prompt file exists',
       ['deps', 'scan', 'medium'].flatMap(d => dimensionsFor(d, M)).every(d => existsSync(join(SKILL, 'references', 'agents', d.file))), true)
   }
@@ -871,7 +871,8 @@ function liftBlock(name) {
 const liftBlockOr = name => { try { return liftBlock(name) } catch { return `const ${name} = ''\n` } }
 const buildPrompt = new Function(
   'dim', 'SUPPRESSED', 'prevSha',
-  [liftBlockOr('PROJECT_RULE_DIMENSIONS'), liftBlockOr('PROJECT_RULE_INSTRUCTION'), liftConst('BUG_CLASS_INSTRUCTION'),
+  [liftBlockOr('PROJECT_RULE_DIMENSIONS'), liftBlockOr('PROJECT_RULE_CORE'), liftBlockOr('IGNORE_ENTRY_NOTE'),
+    liftBlockOr('PROJECT_RULE_INSTRUCTION'), liftBlockOr('PROJECT_RULE_ONLY_INSTRUCTION'), liftConst('BUG_CLASS_INSTRUCTION'),
     `const targetMetadata = '{}', promptDir = 'p', repoSlug = 'o/r', prNumber = 1, prUrl = 'u',
        diffFile = 'd', contextFile = 'c', wtDisplay = 'w'`,
     lift('reviewPrompt'), 'return reviewPrompt(dim)'].join('\n'),

package/plugins/olko-github-pr/skills/lekker-review/workflow.js

@@ -201,6 +201,11 @@ function sameIssue(a, b) {
       && qa !== '' && qb !== '' && qa !== qb) {
     return false
   }
+  // One authoritative rule quote is one breach, whatever each reviewer titled it or
+  // classed it. Location is still gated by the caller's file bucket and line window.
+  if (sameProjectQuote) {
+    return true
+  }
   // Merging two classes would send one class's instances to the other's fix.
   if (a.bugClass && b.bugClass && a.bugClass !== b.bugClass) {
     return false
@@ -222,9 +227,9 @@ const BUG_CLASS_INSTRUCTION = `BUG CLASS: give every finding a "bugClass" (short
   + ` "file:line" (empty array when there is none). Report the class, not just the first hit.`
 
 const PROJECT_RULE_DIMENSIONS = ['quality', 'implementation', 'simplification', 'conventions', 'test-quality',
-  'triage-quality', 'triage-logic']
+  'triage-quality', 'triage-logic', 'project-rules']
 
-const PROJECT_RULE_INSTRUCTION = `PROJECT RULES AS HARD RULES: read "projectRules" from CONTEXT_FILE.`
+const PROJECT_RULE_CORE = `PROJECT RULES AS HARD RULES: read "projectRules" from CONTEXT_FILE.`
   + ` When a changed line violates a project rule written as a prohibition or an obligation`
   + ` (NEVER, MUST, MUST NOT, ALWAYS, DO NOT, or a plain-English equivalent), raise a Critical`
   + ` finding with "rule" set to "PROJECT:<short-kebab-slug>", "ruleQuote" set to the exact`
@@ -234,8 +239,18 @@ const PROJECT_RULE_INSTRUCTION = `PROJECT RULES AS HARD RULES: read "projectRule
   + ` baseProjectRules, raise an Important finding with rule "weakens-project-rule" quoting`
   + ` the removed line. One finding per rule,`
   + ` with every other violating site in "otherInstances". Never quote a rule that is not in`
-  + ` the authoritative source ("baseProjectRules" when it is a string, otherwise "projectRules"). Preferences and suggestions are not hard rules: report them as ordinary`
-  + ` findings. A REVIEW.md ignore entry narrows where you look, it never disables a rule.`
+  + ` the authoritative source ("baseProjectRules" when it is a string, otherwise "projectRules").`
+
+const IGNORE_ENTRY_NOTE = ` A REVIEW.md ignore entry narrows where you look, it never disables a rule.`
+
+const PROJECT_RULE_INSTRUCTION = PROJECT_RULE_CORE
+  + ` Preferences and suggestions are not hard rules: report them as ordinary findings.`
+  + IGNORE_ENTRY_NOTE
+
+// The dedicated reviewer owns hard rules only, so it must not be told to emit preference findings.
+const PROJECT_RULE_ONLY_INSTRUCTION = PROJECT_RULE_CORE
+  + ` Preferences and suggestions are out of scope for you: do not report them.`
+  + IGNORE_ENTRY_NOTE
 
 const BUG_CLASS_PATTERN = /^[a-z0-9]+(-[a-z0-9]+)*$/
 const INSTANCE_PATTERN = new RegExp(INSTANCE_PATTERN_SOURCE)
@@ -397,7 +412,10 @@ function shouldVerify(finding, depth) {
 // Which reviewers run at each depth. `deps` is a PR whose only changes are
 // lockfiles and the dependency keys of package.json: five specialists would
 // produce a couple of notes that a single checklist agent covers, so it gets
-// exactly one.
+// exactly one. `project-rules` runs at every other depth: a rule sentence inside
+// a large rules file was missed when the check was only a side duty of generalist
+// agents. It always runs because the script cannot cheaply tell whether the
+// context holds rules; its prompt returns no findings when they are absent.
 function dimensionsFor(depth, MODEL) {
   if (depth === 'deps') {
     return [{ key: 'deps', file: 'deps.md', model: MODEL.review }]
@@ -406,6 +424,7 @@ function dimensionsFor(depth, MODEL) {
     return [
       { key: 'triage-quality', file: 'triage-quality.md', model: MODEL.triage },
       { key: 'triage-logic',   file: 'triage-logic.md',   model: MODEL.triage },
+      { key: 'project-rules',  file: 'project-rules.md',  model: MODEL.review },
     ]
   }
   return [
@@ -414,6 +433,7 @@ function dimensionsFor(depth, MODEL) {
     { key: 'simplification', file: 'simplification.md', model: MODEL.review },
     { key: 'conventions',    file: 'conventions.md',    model: MODEL.review },
     { key: 'test-quality',   file: 'test-quality.md',   model: MODEL.review },
+    { key: 'project-rules',  file: 'project-rules.md',  model: MODEL.review },
   ]
 }
 
@@ -586,14 +606,14 @@ if (ENGINE === 'revmux' && !findingsFile) {
   throw new Error('lekker-review workflow: engine "revmux" requires findingsFile (adapter output)')
 }
 
-// Concurrency. The review stage is self-limiting: five dimensions means five
+// Concurrency. The review stage is self-limiting: six dimensions means six
 // agents, so it runs them all at once. The other stages are not. Verify,
 // critic and prove spawn one agent PER FINDING, so a finding-heavy PR would
 // fan out far wider than the review that produced it, with no ceiling. Those
 // are capped at the review stage's own width.
 const REVIEW_PLAN = (Array.isArray(reviewBatchPlan) && reviewBatchPlan.length > 0)
   ? reviewBatchPlan
-  : [5]
+  : [6]
 const FANOUT_PLAN = [Math.max(1, maxConcurrent || 5)]
 const targetMetadata = JSON.stringify({ targetLabel })
 
@@ -678,7 +698,7 @@ const budgetAtStart = budget.spent()
     prompt += ' ' + BUG_CLASS_INSTRUCTION
 
     if (PROJECT_RULE_DIMENSIONS.includes(dim.key)) {
-      prompt += ' ' + PROJECT_RULE_INSTRUCTION
+      prompt += ' ' + (dim.key === 'project-rules' ? PROJECT_RULE_ONLY_INSTRUCTION : PROJECT_RULE_INSTRUCTION)
     }
 
     // The deterministic lint pre-flight has already collected every rule the

package/plugins/olko-obsidian/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-obsidian",
   "description": "Keep an Obsidian vault in sync with work: PR sync, task rollover, morning routine.",
-  "version": "1.71.2",
+  "version": "1.73.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-product/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-product",
   "description": "Take a product idea to a shippable build: MVP passes, full-stack scaffolds, UX/UI quality loops, launch plans.",
-  "version": "1.71.2",
+  "version": "1.73.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-reflection/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-reflection",
   "description": "Look back and improve: self-critique, retrospectives, performance review, rapid learning.",
-  "version": "1.71.2",
+  "version": "1.73.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-release/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-release",
   "description": "Ship a release: semantic-release setup, changelogs, store listing copy, release-day routine.",
-  "version": "1.71.2",
+  "version": "1.73.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-skill-meta/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-skill-meta",
   "description": "Author and maintain agent skills and the AI toolchain itself.",
-  "version": "1.71.2",
+  "version": "1.73.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-web-ops/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-web-ops",
   "description": "Operate a website: WAF rules, search console audits, analytics bootstrap, docs indexes.",
-  "version": "1.71.2",
+  "version": "1.73.0",
   "author": {
     "name": "Oleg Koval"
   },