Skip to main content
command CX Codex

obsidian-recurring — Claude Code command for recurring tasks

obsidian-recurring is a command that tracks recurring payments or obligations in Obsidian and calculates the next due date. It links tasks to a board, project note, and log.

MIT ★ 5,412 updated 2026-10-24

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brain
Open on GitHub

What obsidian-recurring does

The command checks _CLAUDE.md and searches for an existing note about the obligation. It updates a match or creates a note in the tasks folder resolved through references/folder-map.md. The note has What, Cadence, Blockers, and History sections, plus frontmatter for the cadence, owner, blocker, and calculated next-due. Payments can include an amount.

It adds a card to the relevant board, links the note from a related project or finance note, and writes an entry to today’s daily note and the operation log. On completion, it appends to History and advances next-due. The command follows references/ai-first-rules.md; if it cannot read that file, it reports the problem before writing.

What it helps with

  • track a recurring payment and calculate its next due date
  • put a repeating obligation on the relevant Obsidian board
  • update an existing note instead of duplicating it
  • link an obligation to a project note and operation log
  • record completion and advance the next due date

Example prompts for the agent

  • Track social benefits payments on the 20th of each month and use the amount from our conversation.
  • Add a recurring monthly filing task and use the owner discussed above.
  • Record this recurring operations task as completed and advance its next due date.

How to install obsidian-recurring

1Plugin marketplace

/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brain

2Manually: put the files in place

.claude/commands/obsidian-recurring.md

Call it with /obsidian-recurring. For all projects use ~/.claude/commands/

Questions about obsidian-recurring

How do I install obsidian-recurring in Claude Code?

Run /plugin marketplace add eugeniughelbur/obsidian-second-brain, then /plugin install obsidian-second-brain@obsidian-second-brain.

What does obsidian-recurring do?

It creates or updates an Obsidian note for a repeating obligation, calculates the next due date, and connects the note to a board, related notes, and logs.

What happens if the command cannot read the AI-first rules?

It reports the issue before writing, rather than creating a note that skips those rules.

Source text

obsidian-recurring.md · MIT
---
description: Track a recurring obligation (payment, filing, ops) with a cadence and a computed next-due date
category: vault
triggers_en: ["recurring task", "monthly obligation", "remind me every month", "recurring payment", "track a recurring"]
triggers_de: ["wiederkehrende Aufgabe", "monatliche Verpflichtung", "erinnere mich jeden Monat", "wiederkehrende Zahlung", "etwas Wiederkehrendes verfolgen"]
triggers_es: ["tarea recurrente", "obligación mensual", "recuérdamelo cada mes", "pago recurrente", "haz seguimiento de algo recurrente"]
triggers_pt: ["tarefa recorrente", "obrigação mensal", "me lembre todo mês", "pagamento recorrente", "acompanhe algo recorrente"]
triggers_zh: ["添加一个周期任务", "每个月提醒我", "记录这项定期付款", "跟踪一个重复事项", "记录一件要定期处理的事"]
---

Use the obsidian-second-brain skill. Execute `/obsidian-recurring $ARGUMENTS`:

The argument states the obligation and its cadence (e.g. "pay social benefits, monthly day 20"). Pull blocker/owner detail from the conversation.

1. Read `_CLAUDE.md` first if it exists in the vault root.
2. Search for an existing note on this obligation before creating one (see the anti-fabrication rule). If one exists, update it instead of duplicating. Save new notes to the tasks folder, resolved per `references/folder-map.md` (wiki-style `wiki/tasks/`, Obsidian-style `Tasks/`).
3. Build the note with these sections: What, Cadence, Blockers, History. Use the vault's `templates/` version if one exists.
4. Set frontmatter: `type: recurring-task`, `cadence`, `owner`, `blocker` (wikilink if a person/vendor gates it), `next-due` (compute the next occurrence from today and the cadence), and `amount` if it is a payment.
5. Add a card for the next occurrence to the right board so it surfaces before `next-due`.
6. Propagate: link from the relevant project or finance note, and append a one-line entry to today's daily note and the operation log (`Logs/YYYY-MM-DD.md` if it exists, otherwise `log.md`).
7. On each completion: append a row to History and advance `next-due` to the next occurrence.

---

**AI-first rule:** Every note created or updated by this command MUST follow `references/ai-first-rules.md` - `## For future agent` preamble, rich frontmatter (`type`, `date`, `tags`, `ai-first: true`, plus type-specific fields), recency markers per external claim, mandatory `[[wikilinks]]` for every person/project/concept referenced, sources preserved verbatim with URLs inline, and confidence levels where applicable. If that path does not resolve from your working directory, search upward for it; if you still cannot read it, say so before writing rather than producing a note that silently skips the rule. The vault is for future agent retrieval - not human reading.

**Anti-fabrication:** Search exhaustively before claiming any note, person, or file is absent - false absence is the most common failure mode - and never invent facts, entities, or dates (mark unknowns as `TBD`). See the anti-fabrication and search-completeness hard rules in `references/ai-first-rules.md`.

© Eugeniu Ghelbur · MIT · eugeniughelbur/obsidian-second-brain

Similar slash commands

All slash commands for Notes, tasks and projects →

From the same set51

The whole set →
obsidian-find obsidian-find searches an Obsidian vault and delivers relevant excerpts with context instead of bare filenames. CX Codex +1 ★ 5,412repo stars obsidian-project Creates or updates an Obsidian project note, then links it to a board and the daily note. It fits vaults that track projects through structured notes. CX Codex +1 ★ 5,412repo stars obsidian-review obsidian-review — a command that generates a structured report of work completed over a week or month by reading daily notes, logs, projects, and task completion data from your Obsidian vault. CX Codex +1 ★ 5,412repo stars obsidian-recap obsidian-recap summarizes Obsidian vault activity for today, the week, or the month. It uses parallel subagents to process daily notes, dev logs, and kanban tasks into a structured recap. CX Codex +1 ★ 5,412repo stars obsidian-reindex obsidian-reindex refreshes the semantic search index for an Obsidian vault and reports how many notes are indexed before and after. Runs fast on subsequent calls because it only embeds new or modified notes. CX Codex +1 ★ 5,412repo stars x-pulse x-pulse scans X via Grok x_search for topic trends, popular angles, and post ideas, then saves the research note to your vault. CX Codex +1 ★ 5,412repo stars obsidian-connect obsidian-connect — a command that connects two unrelated domains through your Obsidian vault's link graph. Discovers unexpected intersections and generates concrete ideas at their convergence. CX Codex +1 ★ 5,412repo stars idea-discovery idea-discovery surfaces 3–5 next-direction candidates by reading ungraduated ideas, open project questions, and orphan research notes in your Obsidian vault. CX Codex +1 ★ 5,412repo stars

Project sponsors

Companies that keep this analytics open