@olegkoval/agent-skills 1.27.0 → 1.29.0

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-agent-skills",
   "description": "Agent-agnostic skill catalog for Codex, Claude, Cursor, Grok, Copilot, Windsurf, Kiro, and other skill-aware tools.",
-  "version": "1.26.0",
+  "version": "1.28.0",
   "author": {
     "name": "Oleg Koval"
   },
@@ -9,6 +9,7 @@
   "repository": "https://github.com/oleg-koval/agent-skills",
   "license": "MIT",
   "skills": [
+    "./packages/software-development/lekker-review",
     "./packages/software-development/self-critique",
     "./packages/software-development/docs-index-keeper",
     "./packages/software-development/semantic-release-beta",
@@ -47,6 +48,10 @@
     "./packages/software-development/ci-fix-loop",
     "./packages/software-development/pr-to-green",
     "./packages/software-development/dependabot-triage",
-    "./packages/software-development/store-listing-copy"
+    "./packages/software-development/store-listing-copy",
+    "./packages/software-development/pr-finalize-complete",
+    "./packages/software-development/morning-routine",
+    "./packages/software-development/release-day",
+    "./packages/software-development/branch-cleanup"
   ]
 }

package/.cursor-plugin/index.json

@@ -124,7 +124,7 @@
     {
       "name": "olko:garmin-watchface",
       "source": "./packages/wearables/garmin-watchface/adapters/cursor",
-      "description": "Build, test, screenshot and publish Garmin Connect IQ watch faces in Monkey C."
+      "description": "Design, build, test, screenshot and publish Garmin Connect IQ watch faces in Monkey C."
     },
     {
       "name": "olko:coderabbitloop",
@@ -185,6 +185,26 @@
       "name": "olko:store-listing-copy",
       "source": "./packages/software-development/store-listing-copy/adapters/cursor",
       "description": "Generate platform-validated App Store, Google Play, and Connect IQ store listing copy (title, subtitle, description, what's new, keywords) from a git changelog or release notes."
+    },
+    {
+      "name": "olko:pr-finalize-complete",
+      "source": "./packages/software-development/pr-finalize-complete/adapters/cursor",
+      "description": "Comprehensive PR finalization workflow for PRs that may already be partially addressed: checks each review comment's actual current status in code, distinguishes fixed vs. stale vs. still-present findings, verifies test coverage, runs real lint/test gates, and reports what still needs a human."
+    },
+    {
+      "name": "olko:morning-routine",
+      "source": "./packages/software-development/morning-routine/adapters/cursor",
+      "description": "Run the complete start-of-day setup in one pass: roll over unfinished Obsidian tasks to today's daily note, sync open GitHub PRs that need your attention, and sweep Dependabot patch bumps. Chains obsidian-task-rollover, obsidian-pr-sync, and dependabot-triage."
+    },
+    {
+      "name": "olko:release-day",
+      "source": "./packages/software-development/release-day/adapters/cursor",
+      "description": "Orchestrate a full release-day workflow for iOS, Android, or Garmin apps: verify main branch CI is green, generate changelog, draft platform-ready store listing copy, trigger semantic-release or tag manually, wait for the build, and queue the App Store submission."
+    },
+    {
+      "name": "olko:branch-cleanup",
+      "source": "./packages/software-development/branch-cleanup/adapters/cursor",
+      "description": "Prune stale git branches after a merge wave: delete closed/merged remote branches, remove local tracking refs that no longer exist on the remote, and optionally clean up merged local branches. Natural follow-up to dependabot-triage."
     }
   ]
 }

package/.grok-plugin/index.json

@@ -134,7 +134,7 @@
     {
       "name": "olko:garmin-watchface",
       "source": "./packages/wearables/garmin-watchface/adapters/grok",
-      "description": "Build, test, screenshot and publish Garmin Connect IQ watch faces in Monkey C."
+      "description": "Design, build, test, screenshot and publish Garmin Connect IQ watch faces in Monkey C."
     },
     {
       "name": "olko:coderabbitloop",
@@ -195,6 +195,26 @@
       "name": "olko:store-listing-copy",
       "source": "./packages/software-development/store-listing-copy/adapters/grok",
       "description": "Generate platform-validated App Store, Google Play, and Connect IQ store listing copy (title, subtitle, description, what's new, keywords) from a git changelog or release notes."
+    },
+    {
+      "name": "olko:pr-finalize-complete",
+      "source": "./packages/software-development/pr-finalize-complete/adapters/grok",
+      "description": "Comprehensive PR finalization workflow for PRs that may already be partially addressed: checks each review comment's actual current status in code, distinguishes fixed vs. stale vs. still-present findings, verifies test coverage, runs real lint/test gates, and reports what still needs a human."
+    },
+    {
+      "name": "olko:morning-routine",
+      "source": "./packages/software-development/morning-routine/adapters/grok",
+      "description": "Run the complete start-of-day setup in one pass: roll over unfinished Obsidian tasks to today's daily note, sync open GitHub PRs that need your attention, and sweep Dependabot patch bumps. Chains obsidian-task-rollover, obsidian-pr-sync, and dependabot-triage."
+    },
+    {
+      "name": "olko:release-day",
+      "source": "./packages/software-development/release-day/adapters/grok",
+      "description": "Orchestrate a full release-day workflow for iOS, Android, or Garmin apps: verify main branch CI is green, generate changelog, draft platform-ready store listing copy, trigger semantic-release or tag manually, wait for the build, and queue the App Store submission."
+    },
+    {
+      "name": "olko:branch-cleanup",
+      "source": "./packages/software-development/branch-cleanup/adapters/grok",
+      "description": "Prune stale git branches after a merge wave: delete closed/merged remote branches, remove local tracking refs that no longer exist on the remote, and optionally clean up merged local branches. Natural follow-up to dependabot-triage."
     }
   ]
 }

package/.kiro/steering/garmin-watchface.md

@@ -2,7 +2,7 @@
 
 ---
 inclusion: manual
-description: "Build, test, screenshot and publish Garmin Connect IQ watch faces in Monkey C."
+description: "Design, build, test, screenshot and publish Garmin Connect IQ watch faces in Monkey C."
 ---
 
 # Garmin Connect IQ watch faces
@@ -12,43 +12,43 @@ that draws off the bottom of the screen, a test suite that contains no tests, an
 a colour that is not the colour you get. Everything below is a failure mode that
 looked like success first.
 
-**Read `references/` files as needed — do not read them all up front.**
+**Read `reference/` files as needed — do not read them all up front.**
 
 | File | When |
 | --- | --- |
-| `references/display.md` | Choosing colours, anything about brightness or legibility |
-| `references/layout.md` | Positioning anything; content clipped, overlapping, or off-screen |
-| `references/testing.md` | Writing tests; a suspiciously clean test run |
-| `references/simulator.md` | Screenshots, settings not applying, monkeydo hanging |
-| `references/devices.md` | Adding device support, launcher icons, API levels |
-| `references/store.md` | Publishing, listing copy, IP questions |
-| `references/publishing.md` | Driving the store portal in a browser; upload/update flow, validator rejections |
+| `reference/display.md` | Choosing colours, brightness, legibility; **AMOLED always-on and burn-in** |
+| `reference/layout.md` | Positioning anything; content clipped, overlapping, or off-screen |
+| `reference/testing.md` | Writing tests; a suspiciously clean test run |
+| `reference/simulator.md` | Screenshots, settings not applying, monkeydo hanging |
+| `reference/devices.md` | Adding device support, launcher icons, API levels |
+| `reference/store.md` | Publishing, listing copy, IP questions |
+| `reference/publishing.md` | Driving the store portal in a browser; upload/update flow, validator rejections |
 
 ## Tools
 
 Run these rather than reinventing them. All are standalone.
 
 ```bash
-<skill-dir>/scripts/ciq-doctor                    # toolchain check: SDK, JDK, key, devices
-<skill-dir>/scripts/ciq-devices                   # survey installed devices by resolution
-<skill-dir>/scripts/ciq-devices --same-as fenix6pro   # products you can add with no code change
-<skill-dir>/scripts/ciq-capture out.png           # calibrated simulator screenshot
-<skill-dir>/scripts/ciq-capture out.png --face --size 260   # cropped + masked to the round display
-<skill-dir>/scripts/ciq-calibrate                 # re-derive the display rect if capture looks wrong
-<skill-dir>/scripts/ciq-release       # pre-submission check: package, screenshots, icon, keys, copy
+bin/ciq-doctor                    # toolchain check: SDK, JDK, key, devices
+bin/ciq-devices                   # survey installed devices by resolution
+bin/ciq-devices --same-as fenix6pro   # products you can add with no code change
+bin/ciq-capture out.png           # calibrated simulator screenshot
+bin/ciq-capture out.png --face --size 260   # cropped + masked to the round display
+bin/ciq-calibrate                 # re-derive the display rect if capture looks wrong
+bin/ciq-release                   # pre-submission check: package, screenshots, icon, keys, copy
 ```
 
-`<skill-dir>/scripts/ciq-release` is what you run before opening the store
-portal. Every check in it is something otherwise discovered halfway through the
-submission form -- a stale screenshot set, an icon still copied from the last
-project, or copy containing a character the description validator rejects.
+`bin/ciq-release` is what you run before opening the store portal. Every check
+in it is something otherwise discovered halfway through the submission form --
+a stale screenshot set, an icon still copied from the last project, or copy
+containing a character the description validator rejects.
 
-`<skill-dir>/scripts/ciq-capture` exists because `screencapture -R` grabs a screen *region*, not
+`bin/ciq-capture` exists because `screencapture -R` grabs a screen *region*, not
 a window: without a frontmost check it silently photographs whatever is on top,
 and the window moves between simulator restarts. Both failure modes produce a
 plausible PNG of the wrong thing.
 
-## The five things that will bite you
+## The seven things that will bite you
 
 ### 1. `make test` can compile zero tests and report success
 
@@ -58,7 +58,7 @@ get `BUILD SUCCESSFUL` and a green run with nothing compiled — even when the t
 files reference symbols that no longer exist.
 
 Fix: a second jungle passed as an additional `-f`. See
-`<skill-dir>/templates/monkey.test.jungle` and the `test` target in `<skill-dir>/templates/Makefile`.
+`templates/monkey.test.jungle` and the `test` target in `templates/Makefile`.
 
 **Prove it before you trust it.** Put a deliberately unresolvable symbol in one
 test and confirm the build fails:
@@ -79,6 +79,13 @@ they look. Measured on fenix 6 Pro:
 | `FONT_SMALL` | 32 |
 | `FONT_NUMBER_MEDIUM` | 74 |
 
+**Font tiers already scale with the device.** `FONT_XTINY` is a tier, not a
+pixel height: a 454px watch supplies a proportionately taller glyph than a
+260px one, unasked. So when text looks wrong at a new resolution, the bug is a
+LENGTH that failed to scale, never the font. Do not add screen-size branching
+to pick a bigger tier -- doing so double-scales, and labels end up wider than
+the containers naming them.
+
 Content drawn past the screen height is simply invisible — no error, no warning,
 no clipping indicator. A two-line `FONT_NUMBER_MEDIUM` block is 148px of a 260px
 face.
@@ -93,7 +100,7 @@ function clampRuleY(derived as Number, footerH as Number) as Number {
 }
 ```
 
-See `references/layout.md`.
+See `reference/layout.md`.
 
 ### 3. The screen is round; your layout is not
 
@@ -122,7 +129,7 @@ simulator's backlit LCD.
 Corollary: a saturated colour on a glyph reflects only its own channel, making
 the thing you want to read the *dimmest* thing on screen.
 
-See `references/display.md`.
+See `reference/display.md`.
 
 ### 5. The simulator lies about settings
 
@@ -133,14 +140,59 @@ settings code.
 
 Reset also drops the loaded device, so relaunch and re-push afterwards.
 
-See `references/simulator.md`.
+See `reference/simulator.md`.
+
+### 6. On AMOLED, the face you designed is the one that fails review
+
+`requiresBurnInProtection` devices must show a restricted always-on frame
+between wrist raises. The trap is that the *stronger* your face's identity —
+a bright panel, a filled dial — the worse a dimmed version of it performs,
+because it still lights most of the screen. The always-on frame has to be a
+different drawing: outlines where there were fills, and shifted a few pixels on
+a cycle so no pixel is driven continuously.
+
+Also note the flag can be **null** on older products, and a null propagating
+into a `Boolean` field throws at the first wrist drop.
+
+See the AMOLED section of `reference/display.md`.
+
+### 7. A watch face CAN have settings on the watch
+
+`AppBase.getSettingsView()` has existed since **API 3.2.0** and the SDK
+documents it as "only applicable to watch faces and data fields". Plenty of
+store copy — including, at one point, this author's own — claims settings are
+reachable only from the phone. They are not.
+
+The override signature must include `or Null` or the compiler rejects it as
+narrowing:
+
+```monkeyc
+function getSettingsView() as
+    [WatchUi.Views] or [WatchUi.Views, WatchUi.InputDelegates] or Null {
+    return [new SettingsMenu(), new SettingsMenuDelegate()];
+}
+```
+
+Two things to get right in the menu itself:
+
+- `ToggleMenuItem` has **already flipped its own state** by the time `onSelect`
+  runs. Read `isEnabled()`; negating the stored value inverts the setting.
+- A picker should `setFocus()` the current choice, not open at the top of a long
+  list. If the list filters out unavailable options, item position is *not* the
+  option id — count the focus row as you build the list.
+
+Keep one module that owns every property read, each wrapped with a default, and
+have both the phone path and the on-watch menu go through it. Two readers with
+two sets of defaults is exactly how the watch and the phone come to disagree
+about what "off" means — and check the fallbacks actually match
+`properties.xml`, because nothing enforces that.
 
 ## Workflow
 
 ### Starting a face
 
-1. `<skill-dir>/scripts/ciq-doctor` — confirm SDK, JDK, developer key, target device installed.
-2. Copy `<skill-dir>/templates/Makefile`, `<skill-dir>/templates/monkey.jungle`, `<skill-dir>/templates/monkey.test.jungle`.
+1. `bin/ciq-doctor` — confirm SDK, JDK, developer key, target device installed.
+2. Copy `templates/Makefile`, `templates/monkey.jungle`, `templates/monkey.test.jungle`.
 3. Generate a fresh app id: `python3 -c "import uuid;print(uuid.uuid4().hex)"`.
 4. Split source by responsibility. This structure has held up well:
 
@@ -169,7 +221,7 @@ Capture and *look at it*. Layout bugs are invisible in a passing test run:
 
 ```bash
 make build && make sim
-<skill-dir>/scripts/ciq-capture /tmp/face.png --face --size 260
+bin/ciq-capture /tmp/face.png --face --size 260
 ```
 
 Then Read the PNG. Every layout bug in this skill's history was found by looking,
@@ -202,7 +254,7 @@ are what makes it recognisable:
 - **Where the legends sit** — maker's name on the bezel, not the glass.
 
 No system font is a segment display. If you need one, draw it: see
-`references/layout.md` for a working seven-segment renderer, including the ghost
+`reference/layout.md` for a working seven-segment renderer, including the ghost
 (unlit) segments that are most of what sells the effect.
 
-**Do not print a real brand on the face.** See `references/store.md`.
+**Do not print a real brand on the face.** See `reference/store.md`.

package/.windsurf/rules/garmin-watchface.md

@@ -1,7 +1,7 @@
 <!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
 
 ---
-description: "Build, test, screenshot and publish Garmin Connect IQ watch faces in Monkey C."
+description: "Design, build, test, screenshot and publish Garmin Connect IQ watch faces in Monkey C."
 ---
 
 # Garmin Connect IQ watch faces
@@ -11,43 +11,43 @@ that draws off the bottom of the screen, a test suite that contains no tests, an
 a colour that is not the colour you get. Everything below is a failure mode that
 looked like success first.
 
-**Read `references/` files as needed — do not read them all up front.**
+**Read `reference/` files as needed — do not read them all up front.**
 
 | File | When |
 | --- | --- |
-| `references/display.md` | Choosing colours, anything about brightness or legibility |
-| `references/layout.md` | Positioning anything; content clipped, overlapping, or off-screen |
-| `references/testing.md` | Writing tests; a suspiciously clean test run |
-| `references/simulator.md` | Screenshots, settings not applying, monkeydo hanging |
-| `references/devices.md` | Adding device support, launcher icons, API levels |
-| `references/store.md` | Publishing, listing copy, IP questions |
-| `references/publishing.md` | Driving the store portal in a browser; upload/update flow, validator rejections |
+| `reference/display.md` | Choosing colours, brightness, legibility; **AMOLED always-on and burn-in** |
+| `reference/layout.md` | Positioning anything; content clipped, overlapping, or off-screen |
+| `reference/testing.md` | Writing tests; a suspiciously clean test run |
+| `reference/simulator.md` | Screenshots, settings not applying, monkeydo hanging |
+| `reference/devices.md` | Adding device support, launcher icons, API levels |
+| `reference/store.md` | Publishing, listing copy, IP questions |
+| `reference/publishing.md` | Driving the store portal in a browser; upload/update flow, validator rejections |
 
 ## Tools
 
 Run these rather than reinventing them. All are standalone.
 
 ```bash
-<skill-dir>/scripts/ciq-doctor                    # toolchain check: SDK, JDK, key, devices
-<skill-dir>/scripts/ciq-devices                   # survey installed devices by resolution
-<skill-dir>/scripts/ciq-devices --same-as fenix6pro   # products you can add with no code change
-<skill-dir>/scripts/ciq-capture out.png           # calibrated simulator screenshot
-<skill-dir>/scripts/ciq-capture out.png --face --size 260   # cropped + masked to the round display
-<skill-dir>/scripts/ciq-calibrate                 # re-derive the display rect if capture looks wrong
-<skill-dir>/scripts/ciq-release       # pre-submission check: package, screenshots, icon, keys, copy
+bin/ciq-doctor                    # toolchain check: SDK, JDK, key, devices
+bin/ciq-devices                   # survey installed devices by resolution
+bin/ciq-devices --same-as fenix6pro   # products you can add with no code change
+bin/ciq-capture out.png           # calibrated simulator screenshot
+bin/ciq-capture out.png --face --size 260   # cropped + masked to the round display
+bin/ciq-calibrate                 # re-derive the display rect if capture looks wrong
+bin/ciq-release                   # pre-submission check: package, screenshots, icon, keys, copy
 ```
 
-`<skill-dir>/scripts/ciq-release` is what you run before opening the store
-portal. Every check in it is something otherwise discovered halfway through the
-submission form -- a stale screenshot set, an icon still copied from the last
-project, or copy containing a character the description validator rejects.
+`bin/ciq-release` is what you run before opening the store portal. Every check
+in it is something otherwise discovered halfway through the submission form --
+a stale screenshot set, an icon still copied from the last project, or copy
+containing a character the description validator rejects.
 
-`<skill-dir>/scripts/ciq-capture` exists because `screencapture -R` grabs a screen *region*, not
+`bin/ciq-capture` exists because `screencapture -R` grabs a screen *region*, not
 a window: without a frontmost check it silently photographs whatever is on top,
 and the window moves between simulator restarts. Both failure modes produce a
 plausible PNG of the wrong thing.
 
-## The five things that will bite you
+## The seven things that will bite you
 
 ### 1. `make test` can compile zero tests and report success
 
@@ -57,7 +57,7 @@ get `BUILD SUCCESSFUL` and a green run with nothing compiled — even when the t
 files reference symbols that no longer exist.
 
 Fix: a second jungle passed as an additional `-f`. See
-`<skill-dir>/templates/monkey.test.jungle` and the `test` target in `<skill-dir>/templates/Makefile`.
+`templates/monkey.test.jungle` and the `test` target in `templates/Makefile`.
 
 **Prove it before you trust it.** Put a deliberately unresolvable symbol in one
 test and confirm the build fails:
@@ -78,6 +78,13 @@ they look. Measured on fenix 6 Pro:
 | `FONT_SMALL` | 32 |
 | `FONT_NUMBER_MEDIUM` | 74 |
 
+**Font tiers already scale with the device.** `FONT_XTINY` is a tier, not a
+pixel height: a 454px watch supplies a proportionately taller glyph than a
+260px one, unasked. So when text looks wrong at a new resolution, the bug is a
+LENGTH that failed to scale, never the font. Do not add screen-size branching
+to pick a bigger tier -- doing so double-scales, and labels end up wider than
+the containers naming them.
+
 Content drawn past the screen height is simply invisible — no error, no warning,
 no clipping indicator. A two-line `FONT_NUMBER_MEDIUM` block is 148px of a 260px
 face.
@@ -92,7 +99,7 @@ function clampRuleY(derived as Number, footerH as Number) as Number {
 }
 ```
 
-See `references/layout.md`.
+See `reference/layout.md`.
 
 ### 3. The screen is round; your layout is not
 
@@ -121,7 +128,7 @@ simulator's backlit LCD.
 Corollary: a saturated colour on a glyph reflects only its own channel, making
 the thing you want to read the *dimmest* thing on screen.
 
-See `references/display.md`.
+See `reference/display.md`.
 
 ### 5. The simulator lies about settings
 
@@ -132,14 +139,59 @@ settings code.
 
 Reset also drops the loaded device, so relaunch and re-push afterwards.
 
-See `references/simulator.md`.
+See `reference/simulator.md`.
+
+### 6. On AMOLED, the face you designed is the one that fails review
+
+`requiresBurnInProtection` devices must show a restricted always-on frame
+between wrist raises. The trap is that the *stronger* your face's identity —
+a bright panel, a filled dial — the worse a dimmed version of it performs,
+because it still lights most of the screen. The always-on frame has to be a
+different drawing: outlines where there were fills, and shifted a few pixels on
+a cycle so no pixel is driven continuously.
+
+Also note the flag can be **null** on older products, and a null propagating
+into a `Boolean` field throws at the first wrist drop.
+
+See the AMOLED section of `reference/display.md`.
+
+### 7. A watch face CAN have settings on the watch
+
+`AppBase.getSettingsView()` has existed since **API 3.2.0** and the SDK
+documents it as "only applicable to watch faces and data fields". Plenty of
+store copy — including, at one point, this author's own — claims settings are
+reachable only from the phone. They are not.
+
+The override signature must include `or Null` or the compiler rejects it as
+narrowing:
+
+```monkeyc
+function getSettingsView() as
+    [WatchUi.Views] or [WatchUi.Views, WatchUi.InputDelegates] or Null {
+    return [new SettingsMenu(), new SettingsMenuDelegate()];
+}
+```
+
+Two things to get right in the menu itself:
+
+- `ToggleMenuItem` has **already flipped its own state** by the time `onSelect`
+  runs. Read `isEnabled()`; negating the stored value inverts the setting.
+- A picker should `setFocus()` the current choice, not open at the top of a long
+  list. If the list filters out unavailable options, item position is *not* the
+  option id — count the focus row as you build the list.
+
+Keep one module that owns every property read, each wrapped with a default, and
+have both the phone path and the on-watch menu go through it. Two readers with
+two sets of defaults is exactly how the watch and the phone come to disagree
+about what "off" means — and check the fallbacks actually match
+`properties.xml`, because nothing enforces that.
 
 ## Workflow
 
 ### Starting a face
 
-1. `<skill-dir>/scripts/ciq-doctor` — confirm SDK, JDK, developer key, target device installed.
-2. Copy `<skill-dir>/templates/Makefile`, `<skill-dir>/templates/monkey.jungle`, `<skill-dir>/templates/monkey.test.jungle`.
+1. `bin/ciq-doctor` — confirm SDK, JDK, developer key, target device installed.
+2. Copy `templates/Makefile`, `templates/monkey.jungle`, `templates/monkey.test.jungle`.
 3. Generate a fresh app id: `python3 -c "import uuid;print(uuid.uuid4().hex)"`.
 4. Split source by responsibility. This structure has held up well:
 
@@ -168,7 +220,7 @@ Capture and *look at it*. Layout bugs are invisible in a passing test run:
 
 ```bash
 make build && make sim
-<skill-dir>/scripts/ciq-capture /tmp/face.png --face --size 260
+bin/ciq-capture /tmp/face.png --face --size 260
 ```
 
 Then Read the PNG. Every layout bug in this skill's history was found by looking,
@@ -201,7 +253,7 @@ are what makes it recognisable:
 - **Where the legends sit** — maker's name on the bezel, not the glass.
 
 No system font is a segment display. If you need one, draw it: see
-`references/layout.md` for a working seven-segment renderer, including the ghost
+`reference/layout.md` for a working seven-segment renderer, including the ghost
 (unlit) segments that are most of what sells the effect.
 
-**Do not print a real brand on the face.** See `references/store.md`.
+**Do not print a real brand on the face.** See `reference/store.md`.

package/README.md

@@ -3,7 +3,7 @@
   <p><strong>Agent-agnostic skill catalog for Codex, Claude, Cursor, Grok, Copilot, Windsurf, Kiro, and other skill-aware tools.</strong></p>
   <p>
     <img src="https://img.shields.io/badge/license-MIT-16a34a" alt="MIT license">
-    <img src="https://img.shields.io/badge/skills-24-2563eb" alt="24 skills">
+    <img src="https://img.shields.io/badge/skills-40-2563eb" alt="40 skills">
     <img src="https://img.shields.io/badge/platforms-Codex%20%7C%20Claude%20%7C%20Cursor%20%7C%20Grok%20%7C%20Copilot%20%7C%20Windsurf%20%7C%20Kiro-111827" alt="Codex Claude Cursor Grok Copilot Windsurf Kiro">
     <img src="https://img.shields.io/badge/status-public%20catalog-16a34a" alt="Public catalog">
   </p>
@@ -139,11 +139,11 @@ packages/{category}/{skill}/SKILL.md
 
 </details>
 
-## All 39 Skills
+## All 40 Skills
 
 Each entry links to its `SKILL.md`. Reference any skill by its `olko:*` lookup name in a new agent session.
 
-### Software development (34)
+### Software development (35)
 
 | Skill | What it does | Use when |
 |-------|-------------|----------|
@@ -160,6 +160,7 @@ Each entry links to its `SKILL.md`. Reference any skill by its `olko:*` lookup n
 | [geminiloop](packages/software-development/geminiloop/SKILL.md) | Iteratively drives a GitHub PR to zero unresolved Gemini Code Assist comments, treating each as a claim to verify — fixing the correct ones and rebutting the rest with evidence | Clearing a Gemini Code Assist review whose findings need checking first |
 | [gh-cli](packages/software-development/gh-cli/SKILL.md) | Guides GitHub CLI usage for repos, PRs, Actions, releases, issues, and all related GitHub operations | Working with GitHub from the command line and needing reliable `gh` commands |
 | [git-commit](packages/software-development/git-commit/SKILL.md) | Creates conventional commits with diff-aware staging and message generation | Asking to commit changes or wanting a conventional commit message from the current diff |
+| [lekker-review](packages/software-development/lekker-review/SKILL.md) | Runs a FAANG-quality PR review in an isolated worktree: 5 parallel specialist agents, adversarial finding verification, proof-of-bug tests for Criticals, and an optional --fix mode that applies and commits its own findings (Claude Code only — needs the Workflow tool) | Reviewing a GitHub PR beyond what a single-pass review or a bot reviewer catches |
 | [macos-menubar-app](packages/software-development/macos-menubar-app/SKILL.md) | Builds a production-quality macOS menubar or notch app in SwiftUI — MenuBarExtra setup, sandbox entitlements, keyboard shortcuts, sound effects | Building a native macOS utility that lives in the menu bar or Dynamic Island notch |
 | [mvp-oneshot](packages/software-development/mvp-oneshot/SKILL.md) | Takes a rough product idea and produces a scoped, testable MVP plan and initial implementation in a single pass | Going from idea to a shippable one-week MVP without losing scope |
 | [obsidian-pr-sync](packages/software-development/obsidian-pr-sync/SKILL.md) | Fetches open GitHub PRs assigned to you or requesting review and writes a grouped age-sorted section into today's Obsidian daily note | Syncing GitHub review queue to Obsidian at the start of the day or on demand |
@@ -181,6 +182,10 @@ Each entry links to its `SKILL.md`. Reference any skill by its `olko:*` lookup n
 | [pr-to-green](packages/software-development/pr-to-green/SKILL.md) | Orchestrates a GitHub PR from first push to merge-ready: runs ci-fix-loop until checks are green, detects active AI review bots, runs qodoloop and coderabbitloop in sequence, and confirms zero unresolved threads | Driving a PR to merge-ready in one pass without manually chaining the fix loops |
 | [dependabot-triage](packages/software-development/dependabot-triage/SKILL.md) | Triages open Dependabot and Renovate PRs in bulk: classifies by risk tier, auto-approves safe patch bumps, flags breaking major upgrades for human review, and posts a digest | Clearing a backlog of dependency update PRs during a maintenance window |
 | [store-listing-copy](packages/software-development/store-listing-copy/SKILL.md) | Generates platform-validated App Store, Google Play, and Connect IQ store listing copy (title, subtitle, description, what's new, keywords) from a git changelog | Writing store copy before submitting to apple-store-submit or the garmin-watchface store workflow |
+| [pr-finalize-complete](packages/software-development/pr-finalize-complete/SKILL.md) | Comprehensive PR finalization for branches that may already be partially addressed: checks each review comment's actual current status in code, distinguishes fixed vs. stale vs. still-present findings, verifies test coverage, and runs real lint/test gates | Confirming a PR is genuinely merge-ready when review tools show findings that may already be fixed |
+| [morning-routine](packages/software-development/morning-routine/SKILL.md) | Runs the complete start-of-day setup in one pass: rolls over unfinished Obsidian tasks, syncs open GitHub PRs into today's daily note, and sweeps safe Dependabot patch bumps | Starting the workday by chaining obsidian-task-rollover, obsidian-pr-sync, and dependabot-triage in sequence |
+| [release-day](packages/software-development/release-day/SKILL.md) | Orchestrates a full release-day workflow for iOS, Android, or Garmin apps: verifies CI is green, generates a changelog, drafts store listing copy, triggers semantic-release or tags manually, waits for the build, and queues the App Store submission | Cutting a release from "code is ready" to "build submitted" in one orchestrated pass |
+| [branch-cleanup](packages/software-development/branch-cleanup/SKILL.md) | Prunes stale git branches after a merge wave: deletes closed/merged remote branches, removes local tracking refs that no longer exist on the remote, and optionally cleans up merged local branches | Tidying up after a Dependabot triage batch merge or a sprint wind-down |
 
 ### Marketing (2)
 
@@ -205,7 +210,7 @@ Each entry links to its `SKILL.md`. Reference any skill by its `olko:*` lookup n
 
 | Skill | What it does | Use when |
 |-------|-------------|----------|
-| [garmin-watchface](packages/wearables/garmin-watchface/SKILL.md) | Builds, tests, screenshots, and publishes Garmin Connect IQ watch faces in Monkey C | Working on a Connect IQ watch face — layout that clips or overlaps, simulator screenshots, app settings, device support, or store submission |
+| [garmin-watchface](packages/wearables/garmin-watchface/SKILL.md) | Designs, builds, tests, screenshots, and publishes Garmin Connect IQ watch faces in Monkey C | Working on a Connect IQ watch face — SVG design proposals, inspiration gathering, layout that clips or overlaps, simulator screenshots, app settings, device support, or store submission |
 
 ## How to use skills