skills.rest
netdata
netdataOFFICIAL
Explore all skills by this author →
WebsiteGitHub

project-netdata-vendoring

Analyze plugin-ipc changes and plan migration into Netdata's vendored source.

1|1|Updated Mar 8, 2026
Search Tags:#vendor management#migration planning#preflight#change analysis#Netdata
One-click install
npx skills add https://github.com/netdata/plugin-ipc --skill project-netdata-vendoring
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-netdata-vendoring
Source: https://github.com/netdata/plugin-ipc/tree/main/.agents/skills/project-netdata-vendoring
Command: npx skills add https://github.com/netdata/plugin-ipc --skill project-netdata-vendoring

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the complexities and risks associated with vendor changes to the NetIPC source, providing a mandatory preflight workflow to ensure compatibility and safety before updating Netdata's vendored NetIPC source.

Core Features & Use Cases

  • Vendor Change Preflight: Ensures compatibility of plugin-ipc changes before vendoring into Netdata.
  • Change Analysis: Identifies and categorizes changes in both plugin-ipc and Netdata's vendored copy.
  • Migration Planning: Helps in creating a migration plan for handling drift and conflicts.
  • Use Case: For instance, when a new commit in the plugin-ipc repository is identified, this Skill will analyze the changes, check for CI/status, and assist in planning the update to the Netdata vendored source.

Quick Start

Run the skill to preflight changes from the latest plugin-ipc commit before updating Netdata's vendored source.

Frequently Asked Questions about project-netdata-vendoring

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

FAQPage Schema
How do I automate Netdata vendoring for NetIPC source changes?▼

Analyze vendor changes by identifying and categorizing modifications in both the plugin-ipc repository and Netdata's vendored copy, then generating a migration plan to handle drift and conflicts before updating the source.

Do I need GitHub access and a Netdata checkout to preflight plugin-ipc changes?▼

Yes, GitHub access and a Netdata checkout are required to check CI status, analyze plugin-ipc commits, and plan the migration of changes into the vendored source.

How does the vendor change preflight process handle drift and conflicts?▼

It identifies and categorizes changes in both plugin-ipc and Netdata's vendored copy, then creates a migration plan to resolve drift and conflicts before updating the vendored source.

What is the best way to update Netdata's vendored source from a new plugin-ipc commit?▼

Run the preflight workflow to analyze the new plugin-ipc commit, verify CI status, and generate a migration plan to safely update the Netdata vendored source.

Are there limitations when migrating plugin-ipc changes into Netdata's vendored source?▼

The preflight workflow requires GitHub access and a Netdata checkout to analyze plugin-ipc changes and check CI status, limiting its use without these dependencies.

Related Skills

Explore More Software Engineering Skills→
AllBeingsFutureAllBeingsFuture
9

allbeingsfuture/skills@code-review

Reviews local git diffs and remote Pull Requests for correctness, security, and maintainability issues.

Community
Intermediate
adiomasadiomas

session-handoff

Save session state and generate next-session.md for continuation.

Community
Basic
NVIDIA-NeMoNVIDIA-NeMo
58

refresh-data-designer-skill

Synchronize vendored Data Designer skill bundles and adapt CLI commands for NeMo Platform.

Official
Advanced
otographyotography
1

but

Automate and govern Git operations with a workspace-aware CLI.

Official
Advanced