@olegkoval/agent-skills 1.17.0 → 1.19.0

package/packages/software-development/obsidian-pr-sync/adapters/grok/skills/obsidian-pr-sync/SKILL.md

@@ -0,0 +1,154 @@
+---
+name: obsidian-pr-sync
+description: >
+  Fetch open GitHub PRs where the user is an assignee or review-requested reviewer,
+  then write or refresh a "## PRs to review" section in today's Obsidian daily note.
+  Use this skill whenever the user asks to sync PRs to Obsidian, update their daily note
+  with GitHub reviews, check what PRs need attention, or run a morning PR sync routine.
+  Also suitable for scheduled/automated runs — fully idempotent (re-running replaces
+  the section, never appends).
+license: MIT
+allowed-tools: Bash, Read, Write, Edit
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, and other Agent Skills compatible tools. Requires the GitHub CLI (`gh`) authenticated and a daily note vault.
+metadata:
+  targets: [_source-only]
+  author: Oleg Koval
+  tags:
+    - github
+    - obsidian
+    - daily-note
+    - pull-requests
+    - productivity
+    - morning-routine
+---
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+# Obsidian PR Sync
+
+Fetch all open PRs where the user is assigned or requested as reviewer, filter out
+noise (bots, drafts, self-authored), and write a clean grouped section into today's
+daily note.
+
+## Configuration
+
+Before running, confirm:
+- `VAULT_DAILY` — absolute path to the daily notes folder (e.g. `/Users/you/obsidian/vault/Lead/Daily`)
+- `GH_USERNAME` — GitHub login to exclude self-authored PRs (e.g. `oleg-koval`)
+- `ORG_PREFIX` — org name to group as "Work" (e.g. `Teifi-Digital`); everything else goes to "Personal"
+
+If not specified by the user, infer from context (git config, existing vault files).
+
+## Step 1 — Fetch PRs
+
+Run two `gh` queries and merge results, deduplicating by URL:
+
+```bash
+# Review-requested
+gh search prs --review-requested=@me --state=open \
+  --json title,url,repository,author,createdAt,isDraft --limit 50
+
+# Assigned
+gh search prs --assignee=@me --state=open \
+  --json title,url,repository,author,createdAt,isDraft --limit 50
+```
+
+Merge both lists, deduplicate by `url`. The union is what needs attention.
+
+## Step 2 — Filter
+
+Discard entries where:
+- `isDraft` is `true`
+- `author.login` matches any bot pattern: `dependabot`, `copilot`, `renovate`, `github-actions`, or `author.is_bot` is `true`
+- `author.login` equals `GH_USERNAME` — self-authored PRs are not reviews; they're your own work
+
+## Step 3 — Enrich authors
+
+For each unique author login, resolve a display name for the Obsidian wiki-link:
+
+```bash
+gh api /users/<login> --jq '.name // .login'
+```
+
+If the API returns a name, use it (e.g. `Rutger Klaassen`). If it returns null, fall
+back to the login with first letter uppercased. This gives `[[Rutger Klaassen]]` or
+`[[Merlijnmacgillavry]]`.
+
+Batch these lookups — run them in parallel if possible to keep the sync fast.
+
+## Step 4 — Calculate age
+
+For each PR: `days_old = (today - createdAt).days`. Use today's date in local time.
+
+## Step 5 — Build the section
+
+Format the section exactly as:
+
+```markdown
+## PRs to review
+
+### Work (<ORG_PREFIX>)
+- [ ] [TITLE](url) by [[Author Name]] (N days old)
+
+### Personal
+- [ ] [TITLE](url) by [[Author Name]] (N days old)
+```
+
+Rules:
+- **Work**: `repository.nameWithOwner` starts with `<ORG_PREFIX>/`
+- **Personal**: everything else
+- Within each group, sort by `createdAt` ascending (oldest first — most overdue at top)
+- If a group has no PRs, omit that subsection entirely (don't render an empty `### Work` header)
+- If there are zero PRs total, write: `## PRs to review\n\n_No open PRs — clear queue! 🎉_`
+- Add `⚠️` after the age if `days_old >= 7`
+
+**Example line:**
+```
+- [ ] [RSL-108] Image sync from InRiver by [[Merlijn Mac Gillavry]] (12 days old ⚠️)
+```
+
+## Step 6 — Write to today's daily note
+
+**Find today's note:**
+```bash
+TODAY=$(date +%Y-%m-%d)
+NOTE="${VAULT_DAILY}/${TODAY}.md"
+```
+
+If the file doesn't exist, create it with standard daily template frontmatter first,
+then append the section. If the file exists:
+
+**Replacement logic (idempotent):**
+- If `## PRs to review` already exists: replace everything from that line up to (but not
+  including) the next `## ` heading or end-of-file with the newly built section.
+- If it doesn't exist: append the section at the end of the file (before the nav footer
+  line `*← [[...` if present, otherwise at the very end).
+
+This ensures re-running the skill produces the same result, not a growing list.
+
+## Invocation patterns
+
+**Manual (user-triggered):**
+The user says something like "sync my PRs to today's note" or "update obsidian with my reviews".
+Run the full flow and confirm how many PRs were written.
+
+**Scheduled morning routine:**
+Same flow. No user prompt needed — just run, update the note, and report a one-line
+summary: `"PR sync: 3 work PRs, 2 personal PRs written to 2026-05-11.md"`.
+
+**In a remote CCR agent:**
+Clone the vault repo, run the sync, commit and push. The local Obsidian Git plugin
+pulls the changes automatically.
+
+## Output to user
+
+After writing the file, show a brief confirmation:
+
+```
+Synced N PRs to Lead/Daily/YYYY-MM-DD.md
+  Work (<ORG_PREFIX>): X PRs
+  Personal: Y PRs
+  Skipped: Z bots/drafts
+```
+
+If any `gh` call fails (e.g. auth expired), surface the error clearly rather than
+writing a partial/corrupt section.

package/packages/software-development/obsidian-task-rollover/adapters/grok/plugin.json

@@ -0,0 +1,6 @@
+{
+  "name": "olko:obsidian-task-rollover",
+  "version": "0.1.0",
+  "description": "Bullet-journal end-of-day task migration: copy unchecked tasks from today's Obsidian daily note to the next workday's note under '## Carried over', and mark them [>] in the source. Skips weekends, idempotent.",
+  "skills": "skills/"
+}

package/packages/software-development/obsidian-task-rollover/adapters/grok/skills/obsidian-task-rollover/SKILL.md

@@ -0,0 +1,198 @@
+---
+name: obsidian-task-rollover
+description: >
+  Migrate unfinished tasks from a daily Obsidian note to the next workday's note,
+  bullet-journal style. Marks migrated tasks in the source note with [>] (the BJ
+  migration symbol) and copies them to the target note under "## Carried over".
+  Use this skill whenever the user says "roll over today's tasks", "migrate unfinished
+  tasks to tomorrow", "end of day task sync", "move open tasks to next workday",
+  or when a scheduled end-of-day / start-of-day routine fires. Fully idempotent —
+  safe to re-run; already-migrated tasks ([>]) are not touched again.
+license: MIT
+allowed-tools: Bash, Read, Write, Edit
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, and other Agent Skills compatible tools. Requires daily notes at a configurable vault path.
+metadata:
+  targets: [_source-only]
+  author: Oleg Koval
+  tags:
+    - obsidian
+    - daily-note
+    - bullet-journal
+    - productivity
+    - task-rollover
+    - end-of-day
+---
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+# Obsidian Task Rollover
+
+Bullet-journal–style end-of-day task migration. Unfinished tasks (`- [ ]`) from
+today's note get copied forward to the next workday, and marked as migrated in
+today's note.
+
+## Configuration
+
+- `VAULT_DAILY` — absolute path to the daily notes folder (e.g. `/Users/you/obsidian/vault/Lead/Daily`)
+
+If not specified, infer from context or ask.
+
+## Step 1 — Identify source note
+
+Default source = **today's note**. If the user specifies a date ("roll over Monday's
+tasks"), resolve that date instead.
+
+```bash
+SOURCE_DATE=$(date +%Y-%m-%d)
+SOURCE="${VAULT_DAILY}/${SOURCE_DATE}.md"
+```
+
+If the source note doesn't exist, report and stop — nothing to migrate.
+
+## Step 2 — Find next workday
+
+```bash
+TARGET_DATE=$(python3 -c "
+from datetime import date, timedelta
+d = date.fromisoformat('${SOURCE_DATE}') + timedelta(days=1)
+while d.weekday() >= 5:  # 5=Sat, 6=Sun
+    d += timedelta(days=1)
+print(d)
+")
+TARGET="${VAULT_DAILY}/${TARGET_DATE}.md"
+```
+
+Skips weekends. If today is Friday, tasks roll to Monday.
+
+## Step 3 — Extract incomplete tasks
+
+Read the source note and collect all lines matching `- [ ] ` that are:
+- **Not** inside the `## PRs to review` section (that section is auto-managed by
+  the `obsidian-pr-sync` skill — don't touch it)
+- **Not** already migrated (`- [>]` lines — idempotency guard)
+
+Sections to skip entirely: `## PRs to review`. Stop collecting at the nav footer
+(`*← [[...`).
+
+Collect both the task lines and which section (h2 heading) they belong to, so the
+target note can group them the same way.
+
+## Step 4 — Mark tasks as migrated in source note
+
+For each collected task line in the source note, replace:
+```
+- [ ] some task
+```
+with:
+```
+- [>] some task → [[Lead/Daily/TARGET_DATE|TARGET_DATE]]
+```
+
+The `[>]` is the bullet journal migration arrow — "moved forward". The link lets you
+jump to where the task landed.
+
+**Do not** replace tasks that are already checked (`- [x]`) or already migrated
+(`- [>`). Only unticked `- [ ]` tasks.
+
+## Step 5 — Write to target note
+
+### If the target note exists
+
+Check whether a `## Carried over` section already exists:
+- If yes: **replace** its content (idempotent — re-running a migration is safe)
+- If no: **insert** it before the nav footer line (`*← [[...`) or at end of file
+
+### If the target note doesn't exist
+
+Create it using the standard daily note template:
+```markdown
+---
+type: daily
+date: TARGET_DATE
+tags: [lead/daily]
+---
+
+# WEEKDAY, D MMM YYYY
+
+## Top 3 for today
+1.
+2.
+3.
+
+## People check-in
+> Who needs something from me today?
+
+- [[]]
+
+## Notes / journal
+
+
+## Open loops
+> Things I started but didn't finish
+
+-
+
+## Actions
+- [ ]
+
+---
+*← [[Lead/Daily/SOURCE_DATE|Yesterday]]  |  [[Lead/Daily/NEXT_NEXT_DATE|Tomorrow]] →*
+```
+Then append the `## Carried over` section.
+
+### Carried over section format
+
+```markdown
+## Carried over
+
+> Migrated from [[Lead/Daily/SOURCE_DATE|SOURCE_DATE]]
+
+### SECTION_NAME (if tasks came from a named section)
+- [ ] task text ↩ [[Lead/Daily/SOURCE_DATE|SOURCE_DATE]]
+
+### Actions (if tasks came from ## Actions)
+- [ ] another task ↩ [[Lead/Daily/SOURCE_DATE|SOURCE_DATE]]
+```
+
+Rules:
+- Group tasks by the section they came from in the source note
+- If all tasks are from `## Actions`, omit the subsection header (keep it flat)
+- The `↩` link back to the source date lets you trace where the task originated
+
+## Step 6 — Report
+
+```
+Rolled over N tasks from SOURCE_DATE → TARGET_DATE
+  From ## Actions: X tasks
+  From ## Open loops: Y tasks
+  Marked [>] in: Lead/Daily/SOURCE_DATE.md
+  Written to:     Lead/Daily/TARGET_DATE.md
+```
+
+If there are zero incomplete tasks, report:
+```
+No incomplete tasks in SOURCE_DATE — nothing to roll over ✓
+```
+
+## Invocation patterns
+
+**Manual:**
+- "roll over today's tasks to tomorrow"
+- "migrate my open tasks, it's end of day"
+- "carry forward unfinished items from today"
+
+**Scheduled (end-of-day or start-of-morning):**
+Runs silently. Picks up today's note automatically.
+
+**In a remote CCR agent:**
+Clone the vault repo, run the rollover, commit and push. The local Obsidian Git
+plugin pulls the changes automatically.
+
+## Edge cases
+
+- **Tasks with sub-bullets**: Copy the full block (task + its indented children)
+- **Duplicate migration**: Re-running replaces the `## Carried over` section — never
+  duplicates. Tasks already marked `[>]` in source are not re-processed.
+- **Friday → Monday**: The weekend-skip logic handles this. The Monday note is created
+  if it doesn't exist.
+- **Task already in target**: No dedup check — if you manually added the same task to
+  tomorrow and then run migration, it'll appear twice. Acceptable — easy to clean up.

package/packages/software-development/open-source-publisher/adapters/grok/plugin.json

@@ -0,0 +1,6 @@
+{
+  "name": "olko:open-source-publisher",
+  "version": "0.1.0",
+  "description": "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, optional donation setup, and optional motion previews for generated static images.",
+  "skills": "skills/"
+}