herald-sync

Aggregate per-repo standups into a narrative and append it to an Obsidian daily note.

1|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/89jobrien/dotfiles --skill herald-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: herald-sync
Source: https://github.com/89jobrien/dotfiles/tree/main/dot-claude/skills/herald-sync
Command: npx skills add https://github.com/89jobrien/dotfiles --skill herald-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-project knowledge capture and narrative synthesis to consolidate work across repos into a single, shareable write-up.

Core Features & Use Cases

  • Cross-repo standups: gather activity from multiple repos and generate a coherent narrative.
  • Obsidian daily note integration: append the Herald Summary under the daily note section.
  • Memory persistence: optionally persist milestones and decisions for future sessions.

Quick Start

Run herald-sync to generate a cross-repo narrative and update your Obsidian vault.

Frequently Asked Questions about herald-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a single narrative from cross-repo activity?

To create a single narrative from cross-repo activity, you need a tool that aggregates per-repo standups into a coherent write-up. This Skill synthesizes structured input from multiple repositories to consolidate your multi-project work.

Can I append cross-project standups to an Obsidian daily note?

Yes, you can append cross-project standups to an Obsidian daily note. The synthesis process writes the aggregated Herald Summary directly into your vault under the daily note section for centralized tracking.

What is the best way to consolidate work across multiple repositories?

The best way to consolidate work across multiple repositories is to synthesize per-repo standups into a shareable write-up. This approach aggregates multi-project activity and optionally persists milestones into memory.

Does generating a cross-project narrative require structured input from each repo?

Yes, generating a cross-project narrative requires structured input from each repo. The synthesis mechanism aggregates these per-repo standups to produce a coherent final narrative and update your vault.

How does memory persistence work when synthesizing cross-repo standups?

Memory persistence works by optionally saving milestones and decisions when synthesizing cross-repo standups. This ensures that key project outcomes from the generated narrative are retained for future sessions.