consolidation

Consolidates a git-based shared memory pool through commit, push, merge, and search index refresh.

1|Updated Aug 14, 2026
One-click install
npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill consolidation-zhiyuan-zhang0206
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: consolidation
Source: https://github.com/zhiyuan-zhang0206/Ava/tree/main/ava_builtins/plugins/ava_memory/skills/consolidation
Command: npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill consolidation-zhiyuan-zhang0206

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Agents write notes into a shared git-backed memory pool throughout the day, leaving uncommitted changes that are unpushed and unsearchable. This Skill provides the consolidation procedure that keeps the pool committed, pushed, merged across machines, and indexed for semantic search. ## Core Features & Use Cases - Single-box consolidation: One script call stages, commits, pushes, and refreshes the search index, with a keep-local mode for hosts without a remote. - Multi-host orchestration: An arbiter role spawns per-machine stewards that commit and open pull requests, then squash-merges all PRs and refreshes the index. - Threshold and scheduled triggers: A daily 03:00 cron plus watchers that fire when more than 10 files change, diffs exceed 200 lines, or changes sit uncommitted over 30 minutes. - Use Case: On a three-machine cluster, the arbiter wakes at 03:00, spawns a steward per machine, merges each machine's PR into main, refreshes the gateway search index, tells stewards to rebase, and re-curates the MEMORY.md index under its 16000-character cap. ## Quick Start Ask the agent to consolidate the memory pool now by running the consolidate script with a dated summary message and then re-curating MEMORY.md.

Frequently Asked Questions about consolidation

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

FAQPage Schema
How do I consolidate a git-based shared memory pool?▼

Run the consolidate script with a dated summary message, for example python3 ../scripts/consolidate.py -m "2026-08-01: daily notes". It stages, commits, pushes, and refreshes the search index in one command. Fix any pre-commit hook rejections and re-run.

How does multi-host memory consolidation work with arbiter and steward roles?▼

The arbiter holds the daily schedule, spawns a steward on each machine, and waits for pull requests. Each steward commits, pushes, and opens a PR; the arbiter then squash-merges all PRs, refreshes the index, and tells stewards to rebase.

What triggers memory pool consolidation besides the daily schedule?▼

A watcher fires consolidation when more than 10 memory files change, the pending diff exceeds 200 lines, or uncommitted changes are older than 30 minutes. These threshold triggers run alongside the daily 03:00 cron as a safety net.

Why does the pre-commit hook reject memory notes?▼

The hook enforces size caps: individual notes must stay under 8000 characters and MEMORY.md under 16000 characters. Move oversized content to the Vault and leave a pointer note, or split an over-long MEMORY.md index.

Can memory consolidation run without a GitHub remote?▼

Yes. In keep-local mode (AVA_MEMORY_KEEP_LOCAL set), the consolidate script commits and refreshes the local index but skips the push, printing a keep-local notice. Notes remain on that host only.