@olegkoval/agent-skills 1.22.0 → 1.24.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.21.1",
+  "version": "1.23.0",
   "author": {
     "name": "Oleg Koval"
   },
@@ -38,6 +38,8 @@
     "./packages/software-development/add-to-my-skills",
     "./packages/software-development/ai-tools-setup",
     "./packages/software-development/changelog-generator",
-    "./packages/software-development/wikipedia-uk-editor"
+    "./packages/software-development/wikipedia-uk-editor",
+    "./packages/software-development/pr-description-writer",
+    "./packages/software-development/ci-fix-loop"
   ]
 }

package/.cursor-plugin/index.json

@@ -140,6 +140,16 @@
       "name": "olko:wikipedia-uk-editor",
       "source": "./packages/software-development/wikipedia-uk-editor/adapters/cursor",
       "description": "Draft policy-compliant Ukrainian Wikipedia edits — translate an English article into uk, expand or source an existing uk article, or fix a maintenance backlog item — and return ready-to-paste wikitext plus an edit summary."
+    },
+    {
+      "name": "olko:pr-description-writer",
+      "source": "./packages/software-development/pr-description-writer/adapters/cursor",
+      "description": "Draft and post a GitHub PR title and body from git diff and commit history. Chains after git-commit and before qodoloop / coderabbitloop."
+    },
+    {
+      "name": "olko:ci-fix-loop",
+      "source": "./packages/software-development/ci-fix-loop/adapters/cursor",
+      "description": "Diagnose GitHub Actions CI failures in a loop: fetch failing check logs, fix, push, and repeat until green. Direct analog of qodoloop / coderabbitloop for test and lint failures."
     }
   ]
 }

package/.grok-plugin/index.json

@@ -150,6 +150,16 @@
       "name": "olko:wikipedia-uk-editor",
       "source": "./packages/software-development/wikipedia-uk-editor/adapters/grok",
       "description": "Draft policy-compliant Ukrainian Wikipedia edits — translate an English article into uk, expand or source an existing uk article, or fix a maintenance backlog item — and return ready-to-paste wikitext plus an edit summary."
+    },
+    {
+      "name": "olko:pr-description-writer",
+      "source": "./packages/software-development/pr-description-writer/adapters/grok",
+      "description": "Draft and post a GitHub PR title and body from git diff and commit history. Chains after git-commit and before qodoloop / coderabbitloop."
+    },
+    {
+      "name": "olko:ci-fix-loop",
+      "source": "./packages/software-development/ci-fix-loop/adapters/grok",
+      "description": "Diagnose GitHub Actions CI failures in a loop: fetch failing check logs, fix, push, and repeat until green. Direct analog of qodoloop / coderabbitloop for test and lint failures."
     }
   ]
 }

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

@@ -22,6 +22,7 @@ looked like success first.
 | `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 |
 
 ## Tools
 
@@ -34,8 +35,14 @@ Run these rather than reinventing them. All are standalone.
 <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
 ```
 
+`<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.
+
 `<skill-dir>/scripts/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

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

@@ -21,6 +21,7 @@ looked like success first.
 | `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 |
 
 ## Tools
 
@@ -33,8 +34,14 @@ Run these rather than reinventing them. All are standalone.
 <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
 ```
 
+`<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.
+
 `<skill-dir>/scripts/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

package/README.md

@@ -140,7 +140,7 @@ packages/{category}/{skill}/SKILL.md
 
 Each entry links to its `SKILL.md`. Reference any skill by its `olko:*` lookup name in a new agent session.
 
-### Software development (25)
+### Software development (27)
 
 | Skill | What it does | Use when |
 |-------|-------------|----------|
@@ -148,6 +148,7 @@ Each entry links to its `SKILL.md`. Reference any skill by its `olko:*` lookup n
 | [ai-tools-setup](packages/software-development/ai-tools-setup/SKILL.md) | Sets up, repairs, and reports on the RTK + ICM + Vox AI development toolkit — installs missing tools, fixes broken hooks and MCP config | Bootstrapping AI dev tools on a new machine or diagnosing broken integrations |
 | [apple-store-submit](packages/software-development/apple-store-submit/SKILL.md) | Handles App Store rejection emails end-to-end — parses rejection reasons, creates a fix plan, implements code changes, and prepares resubmission | Responding to App Store rejections for privacy strings, entitlements, or guideline violations |
 | [changelog-generator](packages/software-development/changelog-generator/SKILL.md) | Transforms git commits into polished user-facing changelogs by categorising changes and rewriting technical commit messages | Preparing release notes, app store update descriptions, or a public changelog |
+| [ci-fix-loop](packages/software-development/ci-fix-loop/SKILL.md) | Diagnoses GitHub Actions CI failures in a loop: fetches failing check logs, applies a targeted fix, pushes, and waits for the next run — repeating until green or a blocker needs a human | CI is red after a push and you want it driven to green automatically |
 | [cloudflare-block-countries](packages/software-development/cloudflare-block-countries/SKILL.md) | Blocks specific countries via Cloudflare WAF Custom Rules using the API | Geo-blocking traffic or setting up WAF country rules across single or multiple zones |
 | [coderabbitloop](packages/software-development/coderabbitloop/SKILL.md) | Iteratively drives a GitHub PR to zero unresolved CodeRabbit findings, reading each inline comment's own Prompt for AI Agents block, replying to the thread, and resolving it | Fully addressing a PR against CodeRabbit's review before merging |
 | [crash-course](packages/software-development/crash-course/SKILL.md) | Expert tutor for rapid, source-grounded learning of any topic: a timed 4-hour sprint plus cheat-sheet, learning-ladder, quiz-me, Feynman, and resource-curation modes | Ramping up on an unfamiliar codebase, project, or concept under time pressure |
@@ -160,6 +161,7 @@ Each entry links to its `SKILL.md`. Reference any skill by its `olko:*` lookup n
 | [obsidian-task-rollover](packages/software-development/obsidian-task-rollover/SKILL.md) | Migrates unchecked tasks from today's Obsidian daily note to the next workday under `## Carried over` | End-of-day bullet-journal task migration |
 | [open-source-publisher](packages/software-development/open-source-publisher/SKILL.md) | Prepares an open-source repository for public publishing with branding, CI/CD, and release hygiene | Releasing a private project publicly with proper GitHub Pages, README, and social preview |
 | [product-builder](packages/software-development/product-builder/SKILL.md) | Builds a full-stack web app or SaaS product from a user description using production-oriented defaults | Building a complete app, SaaS, dashboard, or product rather than a prototype |
+| [pr-description-writer](packages/software-development/pr-description-writer/SKILL.md) | Drafts and posts a GitHub PR title and body from git diff and commit history, respecting existing PR templates | Opening a PR after pushing a branch or wanting a structured PR description written automatically |
 | [promptctl](packages/software-development/promptctl/SKILL.md) | Uses `promptctl` for reusable prompt templates, scoring, and workflow automation | A project needs prompt conventions, review, scoring, or reusable prompt workflows |
 | [qodoloop](packages/software-development/qodoloop/SKILL.md) | Iteratively drives a GitHub PR to zero unresolved Qodo findings, reading each finding's own Agent Prompt, replying to the thread, and resolving it | Fully addressing a PR against Qodo's code review before merging |
 | [relay](packages/software-development/relay/SKILL.md) | Uses `claude-relay` to run long or rate-limit-prone tasks autonomously across subscription accounts | A task will outlive one session or hit rate limits partway through |

package/catalog/skills.json

@@ -698,6 +698,50 @@
         "hermes",
         "pi"
       ]
+    },
+    {
+      "name": "pr-description-writer",
+      "lookupName": "olko:pr-description-writer",
+      "category": "software-development",
+      "path": "packages/software-development/pr-description-writer",
+      "description": "Draft and post a GitHub PR title and body from git diff and commit history. Chains after git-commit and before qodoloop / coderabbitloop.",
+      "tags": [
+        "git",
+        "github",
+        "pull-request",
+        "description",
+        "pr",
+        "workflow"
+      ],
+      "adapters": [
+        "codex",
+        "claude",
+        "cursor",
+        "copilot",
+        "grok"
+      ]
+    },
+    {
+      "name": "ci-fix-loop",
+      "lookupName": "olko:ci-fix-loop",
+      "category": "software-development",
+      "path": "packages/software-development/ci-fix-loop",
+      "description": "Diagnose GitHub Actions CI failures in a loop: fetch failing check logs, fix, push, and repeat until green. Direct analog of qodoloop / coderabbitloop for test and lint failures.",
+      "tags": [
+        "github-actions",
+        "ci",
+        "testing",
+        "automation",
+        "loop",
+        "fix"
+      ],
+      "adapters": [
+        "codex",
+        "claude",
+        "cursor",
+        "copilot",
+        "grok"
+      ]
     }
   ]
 }

package/package.json

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

package/packages/software-development/ci-fix-loop/SKILL.md

@@ -0,0 +1,202 @@
+---
+name: ci-fix-loop
+description: >
+  Diagnose GitHub Actions CI failures in a loop: fetch the failing check logs, identify
+  the root cause, apply a targeted fix, push, and wait for the next run — repeating until
+  all checks are green or a real blocker needs a human. Use when CI is red after a push,
+  when the user says "fix CI", "make tests pass", "diagnose CI failures", or "drive this
+  to green". Direct analog of qodoloop / coderabbitloop for automated test and lint failures.
+license: MIT
+allowed-tools: Bash, Read, Write, Edit
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, and other Agent Skills compatible tools. Requires git and gh (GitHub CLI) authenticated, with a GitHub Actions workflow configured.
+metadata:
+  targets: [_source-only]
+  author: Oleg Koval
+  tags:
+    - github-actions
+    - ci
+    - testing
+    - automation
+    - loop
+    - fix
+source: weekly-pattern-learner
+source_reason: "qodoloop and coderabbitloop share the push→poll→diagnose→fix→repeat loop; CI failures have the same shape but no dedicated skill existed"
+source_date: "2026-07-28"
+---
+
+> 🤖 *Auto-generated by **weekly-pattern-learner** · qodoloop and coderabbitloop share the push→poll→diagnose→fix→repeat loop; CI failures have the same shape but no dedicated skill existed*
+
+# CI Fix Loop
+
+Drive a GitHub Actions CI run from red to green: fetch failure logs, diagnose, apply
+a targeted fix, push, and repeat until all required checks pass or a blocker is hit.
+
+## Inputs
+
+- **PR number** (optional): detect from current branch if not given.
+- **Check names** (optional): limit to specific failing checks instead of all.
+- **Max iterations** (default: 5)
+
+## Workflow
+
+### 1. Identify the PR and current CI state
+
+```bash
+# Detect PR from current branch
+gh pr view --json number,headRefName,headRefOid \
+  -q '{number, branch: .headRefName, sha: .headRefOid}'
+
+# Current check status
+gh pr checks --json name,state,conclusion 2>/dev/null \
+  || gh run list --branch <branch> --limit 5
+```
+
+Classify each check as: `pass`, `fail`, `pending`, or `skipped`.
+
+**Exit immediately if all required checks already pass** — nothing to do.
+
+### 2. Loop (max 5 iterations)
+
+#### A. Identify failing checks
+
+```bash
+gh pr checks --json name,state,conclusion \
+  --jq '.[] | select(.conclusion == "failure" or .state == "FAILURE")'
+```
+
+For each failing check, record: check name, workflow file, job name.
+
+Stop if the working set is empty — all required checks are green.
+
+#### B. Check for base-branch regression first
+
+Before touching any code, verify the failure is not already present on `main`:
+
+```bash
+gh run list --branch <base-branch> --workflow <workflow-name> --limit 3 \
+  --json conclusion --jq '.[].conclusion'
+```
+
+If the same check is failing on the base branch, **stop and report** —
+this is not your PR's fault. Do not attempt a fix that masks a base-branch problem.
+Wait for a `Base branch recovered` notice before re-trying.
+
+#### C. Fetch failure logs
+
+For each failing check:
+
+```bash
+# Latest run ID for this branch/workflow
+gh run list --branch <branch> --workflow <workflow-name> --limit 1 \
+  --json databaseId --jq '.[0].databaseId'
+
+# Fetch only failing steps (not the full log)
+gh run view <run-id> --log-failed
+```
+
+Cap log reading at ~200 lines per job — the error is almost always in the last
+50 lines of a failed step.
+
+#### D. Diagnose
+
+Classify the failure before writing any code:
+
+| Category | Examples | Fix target |
+|---|---|---|
+| Test failure | `FAIL TestFoo`, `AssertionError`, `expected X got Y` | Source or test |
+| Lint / format | `gofmt`, `eslint`, `ruff`, `prettier` | Run auto-formatter |
+| Build error | compile error, missing import, type mismatch | Source |
+| Dependency | `npm ERR!`, missing module, lockfile mismatch | Update lockfile |
+| CI config | YAML parse error, bad action ref, missing secret | Workflow YAML |
+| Flaky test | same test passes on manual re-run | Re-run first; mark if it keeps failing |
+
+For flaky-looking failures, re-run the check before touching code:
+
+```bash
+gh run rerun <run-id> --failed
+```
+
+Wait for the rerun result. If it passes on rerun, skip this iteration and go to
+step F to poll for the new result.
+
+#### E. Apply a targeted fix
+
+Fix **only** what the log names as the failure. Do not refactor surrounding code,
+add unrelated tests, or touch files the failing step never mentioned.
+
+Common one-liners:
+
+```bash
+# Go format
+gofmt -w .
+goimports -w .
+
+# Node format / lint
+npx prettier --write .
+npx eslint --fix .
+
+# Python
+ruff check --fix .
+black .
+
+# Lockfile
+npm install          # Node
+poetry lock --no-update  # Python
+go mod tidy          # Go
+```
+
+For test failures: read the failing test and the code it exercises. Fix the code
+or the assertion — but not both in one commit unless the test was clearly wrong
+and the fix is trivial.
+
+#### F. Commit and push
+
+Stage **only the files touched in step E** — never `git add -A`, which can sweep
+in unrelated local changes:
+
+```bash
+git add <files touched>
+git commit -m "fix(ci): <what was broken> (ci-fix-loop iteration N)"
+git push
+```
+
+Confirm the push succeeded before polling. A resolved check whose fix never reached
+the branch is worse than an unresolved one.
+
+#### G. Wait for CI on the new SHA
+
+Poll every ~15s (timeout ~8min) for all previously-failing checks to complete
+on the new push:
+
+```bash
+gh pr checks --json name,state,conclusion,startedAt
+```
+
+Wait until all previously-failing checks show a new result (`pass` or `fail`)
+on the current SHA. Do not act on a result that still shows the old SHA.
+
+Go back to step A.
+
+### 3. Report
+
+| Field | Value |
+|---|---|
+| Iterations | N |
+| Checks fixed | names + root cause |
+| Checks blocked | names + reason (flaky / needs human / base-branch red) |
+| Final status | all green / partial / blocked |
+
+```
+CI fix loop complete.
+  Iterations:  2
+  Fixed:       lint (gofmt: 3 files), test (TestUserCreate — nil pointer in fixture)
+  Blocked:     none
+  Status:      all required checks green
+```
+
+## Chaining
+
+| Before this skill | After this skill |
+|---|---|
+| `olko:pr-description-writer` | `olko:qodoloop` |
+| Any `git push` with failing CI | `olko:coderabbitloop` |

package/packages/software-development/ci-fix-loop/adapters/claude/plugin.json

@@ -0,0 +1,5 @@
+{
+  "name": "olko-ci-fix-loop",
+  "description": "Diagnose GitHub Actions CI failures in a loop: fetch failing check logs, fix, push, and repeat until green. Direct analog of qodoloop / coderabbitloop for test and lint failures.",
+  "skills": "./skills"
+}

package/packages/software-development/ci-fix-loop/adapters/claude/skills/ci-fix-loop/SKILL.md

@@ -0,0 +1,203 @@
+---
+name: ci-fix-loop
+description: >
+  Diagnose GitHub Actions CI failures in a loop: fetch the failing check logs, identify
+  the root cause, apply a targeted fix, push, and wait for the next run — repeating until
+  all checks are green or a real blocker needs a human. Use when CI is red after a push,
+  when the user says "fix CI", "make tests pass", "diagnose CI failures", or "drive this
+  to green". Direct analog of qodoloop / coderabbitloop for automated test and lint failures.
+license: MIT
+allowed-tools: Bash, Read, Write, Edit
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, and other Agent Skills compatible tools. Requires git and gh (GitHub CLI) authenticated, with a GitHub Actions workflow configured.
+metadata:
+  targets: [_source-only]
+  author: Oleg Koval
+  tags:
+    - github-actions
+    - ci
+    - testing
+    - automation
+    - loop
+    - fix
+source: weekly-pattern-learner
+source_reason: "qodoloop and coderabbitloop share the push→poll→diagnose→fix→repeat loop; CI failures have the same shape but no dedicated skill existed"
+source_date: "2026-07-28"
+---
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+> 🤖 *Auto-generated by **weekly-pattern-learner** · qodoloop and coderabbitloop share the push→poll→diagnose→fix→repeat loop; CI failures have the same shape but no dedicated skill existed*
+
+# CI Fix Loop
+
+Drive a GitHub Actions CI run from red to green: fetch failure logs, diagnose, apply
+a targeted fix, push, and repeat until all required checks pass or a blocker is hit.
+
+## Inputs
+
+- **PR number** (optional): detect from current branch if not given.
+- **Check names** (optional): limit to specific failing checks instead of all.
+- **Max iterations** (default: 5)
+
+## Workflow
+
+### 1. Identify the PR and current CI state
+
+```bash
+# Detect PR from current branch
+gh pr view --json number,headRefName,headRefOid \
+  -q '{number, branch: .headRefName, sha: .headRefOid}'
+
+# Current check status
+gh pr checks --json name,state,conclusion 2>/dev/null \
+  || gh run list --branch <branch> --limit 5
+```
+
+Classify each check as: `pass`, `fail`, `pending`, or `skipped`.
+
+**Exit immediately if all required checks already pass** — nothing to do.
+
+### 2. Loop (max 5 iterations)
+
+#### A. Identify failing checks
+
+```bash
+gh pr checks --json name,state,conclusion \
+  --jq '.[] | select(.conclusion == "failure" or .state == "FAILURE")'
+```
+
+For each failing check, record: check name, workflow file, job name.
+
+Stop if the working set is empty — all required checks are green.
+
+#### B. Check for base-branch regression first
+
+Before touching any code, verify the failure is not already present on `main`:
+
+```bash
+gh run list --branch <base-branch> --workflow <workflow-name> --limit 3 \
+  --json conclusion --jq '.[].conclusion'
+```
+
+If the same check is failing on the base branch, **stop and report** —
+this is not your PR's fault. Do not attempt a fix that masks a base-branch problem.
+Wait for a `Base branch recovered` notice before re-trying.
+
+#### C. Fetch failure logs
+
+For each failing check:
+
+```bash
+# Latest run ID for this branch/workflow
+gh run list --branch <branch> --workflow <workflow-name> --limit 1 \
+  --json databaseId --jq '.[0].databaseId'
+
+# Fetch only failing steps (not the full log)
+gh run view <run-id> --log-failed
+```
+
+Cap log reading at ~200 lines per job — the error is almost always in the last
+50 lines of a failed step.
+
+#### D. Diagnose
+
+Classify the failure before writing any code:
+
+| Category | Examples | Fix target |
+|---|---|---|
+| Test failure | `FAIL TestFoo`, `AssertionError`, `expected X got Y` | Source or test |
+| Lint / format | `gofmt`, `eslint`, `ruff`, `prettier` | Run auto-formatter |
+| Build error | compile error, missing import, type mismatch | Source |
+| Dependency | `npm ERR!`, missing module, lockfile mismatch | Update lockfile |
+| CI config | YAML parse error, bad action ref, missing secret | Workflow YAML |
+| Flaky test | same test passes on manual re-run | Re-run first; mark if it keeps failing |
+
+For flaky-looking failures, re-run the check before touching code:
+
+```bash
+gh run rerun <run-id> --failed
+```
+
+Wait for the rerun result. If it passes on rerun, skip this iteration and go to
+step F to poll for the new result.
+
+#### E. Apply a targeted fix
+
+Fix **only** what the log names as the failure. Do not refactor surrounding code,
+add unrelated tests, or touch files the failing step never mentioned.
+
+Common one-liners:
+
+```bash
+# Go format
+gofmt -w .
+goimports -w .
+
+# Node format / lint
+npx prettier --write .
+npx eslint --fix .
+
+# Python
+ruff check --fix .
+black .
+
+# Lockfile
+npm install          # Node
+poetry lock --no-update  # Python
+go mod tidy          # Go
+```
+
+For test failures: read the failing test and the code it exercises. Fix the code
+or the assertion — but not both in one commit unless the test was clearly wrong
+and the fix is trivial.
+
+#### F. Commit and push
+
+Stage **only the files touched in step E** — never `git add -A`, which can sweep
+in unrelated local changes:
+
+```bash
+git add <files touched>
+git commit -m "fix(ci): <what was broken> (ci-fix-loop iteration N)"
+git push
+```
+
+Confirm the push succeeded before polling. A resolved check whose fix never reached
+the branch is worse than an unresolved one.
+
+#### G. Wait for CI on the new SHA
+
+Poll every ~15s (timeout ~8min) for all previously-failing checks to complete
+on the new push:
+
+```bash
+gh pr checks --json name,state,conclusion,startedAt
+```
+
+Wait until all previously-failing checks show a new result (`pass` or `fail`)
+on the current SHA. Do not act on a result that still shows the old SHA.
+
+Go back to step A.
+
+### 3. Report
+
+| Field | Value |
+|---|---|
+| Iterations | N |
+| Checks fixed | names + root cause |
+| Checks blocked | names + reason (flaky / needs human / base-branch red) |
+| Final status | all green / partial / blocked |
+
+```
+CI fix loop complete.
+  Iterations:  2
+  Fixed:       lint (gofmt: 3 files), test (TestUserCreate — nil pointer in fixture)
+  Blocked:     none
+  Status:      all required checks green
+```
+
+## Chaining
+
+| Before this skill | After this skill |
+|---|---|
+| `olko:pr-description-writer` | `olko:qodoloop` |
+| Any `git push` with failing CI | `olko:coderabbitloop` |

package/packages/software-development/ci-fix-loop/adapters/codex/README.md

@@ -0,0 +1,20 @@
+# Codex Adapter for ci-fix-loop
+
+This is a Codex-specific adapter for the `olko:ci-fix-loop` skill.
+The canonical skill definition is in `../../SKILL.md`.
+
+## Usage
+
+Invoke in a Codex session:
+
+```text
+Use the olko:ci-fix-loop skill to diagnose and fix the failing GitHub Actions checks on this PR.
+```
+
+## Workflow
+
+See `../../SKILL.md` for the full workflow: identify failing checks, verify the failure
+is not a base-branch regression, fetch failing job logs via `gh run view --log-failed`,
+diagnose the root cause, apply a targeted fix, commit and push staged changes, then poll
+until CI reports a new result — repeating up to 5 times until all required checks are
+green or a real blocker needs a human. The procedure is plain `git`/`gh` and is agent-agnostic.

package/packages/software-development/ci-fix-loop/adapters/cursor/plugin.json

@@ -0,0 +1,6 @@
+{
+  "name": "olko:ci-fix-loop",
+  "version": "0.1.0",
+  "description": "Diagnose GitHub Actions CI failures in a loop: fetch failing check logs, fix, push, and repeat until green. Direct analog of qodoloop / coderabbitloop for test and lint failures.",
+  "skills": "skills/"
+}