refresh-references

To keep reference repositories synced automatically, you can use a JSON configuration file to define repo URLs, branches, and descriptions. The skill clones missing repositories and performs fast-forward only updates on existing ones, generating explicit status reports for all managed codebases.

Updating local clones without merge conflicts requires fast-forward only pulls. This approach prevents unintended merge conflicts by strictly advancing the local branch pointer to match the upstream reference repository state without creating divergent commit histories.

GitHub CLI is supported alongside native git operations for cloning and syncing external reference codebases. You can configure multiple upstream repositories with custom branches in a single JSON file, then execute one command to sync them all for pattern lookups.

Fast-forward only repository syncing works effectively for teams maintaining numerous reference codebases. It scales by reading a single JSON configuration file to track all repositories, cloning missing ones, and updating existing clones while generating a clear status report for each managed repository.

Tracking reference repositories manually causes problems because it is time-consuming and prone to human error as the number of reference codebases grows. Automating the sync process eliminates hours of manual git operations per sprint and ensures architecture and UI pattern guidance is current.

A JSON configuration file for repository tracking defines all reference codebases in a single location, supporting custom branches, URLs, and descriptions for each repo. It enables automated sync workflows to read the configuration, clone missing repositories, and generate explicit status reports.