refresh

Fetch latest origin changes for all registered sub-repos and update their state.

Updated May 7, 2026
One-click install
npx skills add https://github.com/ChazzCoin/claude-orchestrator --skill refresh-chazzcoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refresh
Source: https://github.com/ChazzCoin/claude-orchestrator/tree/main/kit/skills/refresh
Command: npx skills add https://github.com/ChazzCoin/claude-orchestrator --skill refresh-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the synchronization of all registered sub-repos with their latest changes from origin, streamlining the process and ensuring that all codebases are up-to-date.

Core Features & Use Cases

  • Automated Synchronization: Fetches the latest changes from the origin repository for every registered sub-repo.
  • Deterministic Execution: Ensures a predictable execution flow that reads the manifest, fetches changes from each sub-repo, and records the state.
  • Use Case: Ideal for maintaining consistency across multiple codebases by ensuring that all sub-repos are synchronized with their latest code changes.

Quick Start

Run the refresh skill to synchronize all sub-repos with their latest changes from origin.

Frequently Asked Questions about refresh

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

FAQPage Schema
How do I synchronize all sub-repos with the latest changes from origin?

To synchronize all sub-repos, the refresh skill reads your repository manifests and executes git fetch commands to pull the latest code changes from origin. It updates and records the state of each sub-repo for further processing.

What is the best way to automate fetching updates for multiple registered sub-repos?

Automating sub-repo updates requires a deterministic execution flow that reads manifests and runs git fetch across all registered repositories. This ensures every codebase is consistently updated with the latest changes from origin without manual intervention.

Do I need a manifest to fetch latest code changes for registered sub-repos?

Yes, accessing repository manifests is required to fetch the latest code changes for registered sub-repos. The synchronization process relies on these manifests to identify each sub-repo and correctly update its state from origin.

How does sub-repo synchronization work for maintaining consistency across multiple codebases?

Sub-repo synchronization works by executing git fetch commands across all registered sub-repos based on manifest data. It records the updated state of each codebase, ensuring consistency and making them available for downstream processing by other skills.

Can I use this automated synchronization to prepare sub-repos for further processing?

Yes, automated synchronization fetches the latest changes from origin and updates the state of all registered sub-repos. This ensures the updated codebases are immediately available and correctly prepared for further processing by other skills.