daily-update

To bundle daily maintenance tasks into a single pull request, this skill orchestrates per-day sub-skills, collects their working-tree edits, and packages the combined diff into one PR. It manages branch lifecycles to prevent duplicate runs and reduce review noise.

The best way to automate Obsidian vault housekeeping is by using an orchestrated workflow that sequences sub-skills like daily-changelog, audit-docs, and triage-issues. This captures all working-tree edits and submits them as a single bundle for streamlined end-of-day cleanup.

To prevent empty pull requests during automated daily git branching, this workflow applies safeguards that verify working-tree changes before packaging the diff. It ensures a PR is only created when actual edits are collected from the executed sub-skills.

Orchestration handles sub-skill failures by capturing errors gracefully and continuing with the remaining sequencing steps. It packages the successful working-tree edits into the PR and provides clear summary reporting, ensuring partial workflow failures do not block the entire daily update.

Yes, you can use git branching to manage daily changelog and issue triage together by running them as sequenced sub-skills within a single orchestrated workflow. This collects all audit and triage edits into one bundled diff before creating the pull request.