Menú
End-of-session summary saved to Obsidian with bidirectional daily note linking. Trigger phrases: "done", "wrap up", "session done", "end session"
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Run two heterogeneous fresh-context Herdr reviewers against both code quality and a governing plan, then synthesize evidence-backed feedback. Use when the user asks for a dual or adversarial review, code-versus-plan verification, or independent Claude and Pi reviewers before deciding whether a PR needs changes.
Control herdr from Codex. Use when the user says "use Herder" or asks to inspect, focus, prompt, spawn, or manage herdr workspaces, tabs, panes, or agents from a Codex session, without deciding whether they are inside or outside herdr.
Use when the user explicitly asks Codex Desktop or another shell outside Herdr to create, inspect, prompt, follow up with, or monitor Herdr agent tabs, or when the `codex-herdr` router skill hands off external control.
Fan out a user-provided task list into one reviewed PR per task through Herdr, then shepherd the PR fleet through CI and review without merging. Use when the user asks to fan out PRs, parallelize backlog items into separate PRs, or autonomously drive multiple agent-owned PRs to green.
Inspect and import content into my self-hosted AutoCaliWeb library. Use for catalog status, search, recent imports, shelves, metadata, or importing an ebook, comic, PDF, or audiobook.
Correct-by-construction TypeScript standards. Use for TypeScript engineering or when another skill needs the user's coding standards.
| name | done |
| description | End-of-session summary saved to Obsidian with bidirectional daily note linking. Trigger phrases: "done", "wrap up", "session done", "end session" |
| allowed-tools | Bash, Write, Read, Edit |
Capture what was accomplished this session and save to Obsidian with bidirectional links to today's daily note.
Review the conversation and extract:
KEY-123)repo#123 or full URLs)Derive a short title (3-6 words) summarizing the session.
Format: YYYY-MM-DDTHH-MM-SS-done-<slug>.md
2026-02-17T14-30-00-done-fix-auth-token-refresh.mdWrite to ~/obsidian/Notes/<filename>:
---
date: <ISO8601 timestamp>
daily: [[YYYY-MM-DD]]
tags:
- done
- claude-session
source: claude-code
---
# <Short title>
## Summary
- What was accomplished (bullet points)
## Links
- PR: [repo#123](url)
- Ticket: [KEY-456](url)
- Branch: `branch-name`
## Files Changed
- `path/to/file.ts` - what changed
Omit the Links section if no links were found. Omit individual link types (PR, Ticket, Branch) if not applicable.
Check if ~/obsidian/Notes/YYYY-MM-DD.md exists. If not, create it:
# Journal YYYY-MM-DD
Check if a ## Done section exists in the daily note.
## Done followed by the entry at the end of the file.Entry format:
- [[YYYY-MM-DDTHH-MM-SS-done-slug|brief title]]
Echo both file paths and a brief summary of what was captured.
daily: [[YYYY-MM-DD]] frontmatter creates the backlink from done note to daily note.[[...]] wikilink appended to the daily note creates the forward link from daily note to done note.