Update 3rd Party Libs

Name: Update 3rd Party Libs
Author: DataDog

ASecurity

Update a C/C++ third-party library under deps/ — bump version, reconcile sources/copts/config.h/patches, and verify the build.

3,754 stars
0 votes
0 copies
0 views
Added September 3, 2026

devopsc++bash

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add DataDog/datadog-agent --skill update-3rd-party-libs --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Update 3rd Party Libs?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Update 3rd Party Libs

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/datadog-update-3rd-party-libs/badge)](https://www.skillsdirectory.com/skills/datadog-update-3rd-party-libs)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: update-3rd-party-libs
description: Update a C/C++ third-party library under deps/ — bump version, reconcile sources/copts/config.h/patches, and verify the build.
argument-hint: "<dep-name> [target-version]"
allowed-tools: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion
---

To update a C/C++ third-party library under `deps/`, read **`deps/docs/updating_deps.md`** and follow it end-to-end. That file is the authoritative procedure; its supporting docs (`bump-version.md`, `config-h-refresh.md`, `patches.md`, `verification.md`) live alongside it under `deps/docs/`.

**Arguments:** `$ARGUMENTS` — `<dep-name>` (required), `<target-version>` (optional; ask the user if not supplied). Pass these through to the procedure as its inputs.

The workflow lives under `deps/docs/` (not inline here) so it stays discoverable by humans and non-Claude agents, and is owned alongside the code it touches (`@DataDog/agent-build`).