mirror-netdata-repos

Name: mirror-netdata-repos
Availability: InStock
Author: netdata

Maintain a local mirror of Netdata source repositories for efficient cross-repo code analysis.

80.4k|6.6k|Updated Jun 17, 2013

Search Tags:#Git #code-review #Automation #repository-management #mirror #Netdata

Ready to run

npx skills add https://github.com/netdata/netdata --skill mirror-netdata-repos

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mirror-netdata-repos
Source: https://github.com/netdata/netdata/tree/main/.agents/skills/mirror-netdata-repos
Command: npx skills add https://github.com/netdata/netdata --skill mirror-netdata-repos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates the latency and rate-limiting issues associated with performing cross-repository code reviews and greps against the large Netdata GitHub organization by maintaining a synchronized local mirror.

Core Features & Use Cases

Automated Synchronization: Updates ~150 repositories by resetting to default branches and pulling upstream changes.
Intelligent Discovery: Automatically detects and clones new Netdata-org repositories using the GitHub CLI.
Safety-First Design: Skips repositories with uncommitted changes to prevent data loss while ensuring the mirror remains a reliable source of truth for AI reasoning.

Quick Start

Run the sync script to update your local mirror of all Netdata repositories to their latest upstream state.

Frequently Asked Questions about mirror-netdata-repos

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

FAQPage Schema

How do I sync all Netdata repositories locally?▼

Execute the sync-netdata-repos.sh script within your configured mirror directory. The script automatically fetches updates for all existing repositories and discovers new ones if the GitHub CLI is authenticated.

Why does the script skip some repositories during sync?▼

The script skips repositories that contain staged or modified files to prevent overwriting your local work. You must commit or stash your changes in those specific repositories before the script can successfully update them.

Can I sync only a specific subset of repositories?▼

Yes, use the --repo flag followed by the repository name to limit the sync to specific projects. Note that using this flag disables the automatic discovery of new repositories.

What happens to my local feature branches during sync?▼

The script intentionally switches repositories to their default branch to ensure cross-repo reasoning is based on current code. Your local feature branches are preserved as git refs, but you should push your work before syncing to avoid confusion.

What are the system requirements for this skill?▼

You need git and jq installed on your system. For automatic discovery of new repositories, the GitHub CLI (gh) must be installed and authenticated via gh auth login.