ecc-sync

Synchronizes curated instincts into the repository after ECC Tools pull requests merge.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/diazMelgarejo/orama-system --skill ecc-sync-diazmelgarejo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ecc-sync
Source: https://github.com/diazMelgarejo/orama-system/tree/main/bin/orama-system/skills/ecc-sync
Command: npx skills add https://github.com/diazMelgarejo/orama-system --skill ecc-sync-diazmelgarejo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After an ECC Tools pull request merges into the orama-system repository, learned instincts and session data can drift out of sync. This Skill provides a repeatable post-merge ritual to pull the latest changes, import curated instincts, and commit the synchronized state. ## Core Features & Use Cases - Post-merge sync ritual: Runs git pull, imports instinct YAML files via /instinct-import, and commits the result with a dated message. - Harmonization rules: Supplements rather than replaces existing instinct bundles, excludes timestamp-churn files like ecc-tools.json, and enforces a quality gate of 2-4 curated instincts per stack. - Fallback path: If /instinct-import is unavailable, it directs you to check the ECC Tools MCP server or run import_instincts.py directly. - Use Case: After merging an ECC Tools PR, run this Skill to import the new session instincts into .claude/homunculus/instincts/inherited/ and push a clean sync commit. ## Quick Start Ask the agent to run the ecc-sync post-merge ritual to pull main, import the latest inherited instincts YAML, and commit the sync.

Frequently Asked Questions about ecc-sync

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

FAQPage Schema
How do I sync instincts after merging an ECC Tools PR?▼

Run git pull origin main, then use /instinct-import on the session YAML under .claude/homunculus/instincts/inherited/, verify with /instinct-status, and commit with a dated chore(ecc) message before pushing to main.

What should I do if my git worktree is dirty before syncing?▼

Stash your changes first before pulling. The Skill references a safe cross-host sync reference card in the git-history-surgery skill for handling dirty worktrees during the sync ritual.

What if the /instinct-import command is unavailable?▼

Check that the ECC Tools MCP server is running. If it still fails, run python .claude/homunculus/import_instincts.py directly as a fallback to import the instinct files.

Which files should be excluded during the ECC sync?▼

Exclude timestamp-churn files such as ecc-tools.json and identity.json unless changes to them are intentional. The harmonization rules favor supplementing existing bundles rather than replacing them.

How many instincts should be imported per stack?▼

The quality gate specifies 2 to 4 curated instincts per stack. Bulk auto-dumps are explicitly discouraged to keep the inherited instinct bundles high-signal and maintainable.