菜单
Update a C/C++ third-party library under deps/ — bump version, reconcile sources/copts/config.h/patches, and verify the build.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate the Agent Supply Chain newsletter by researching team activity on GitHub and Confluence, then creating a Confluence draft and Gmail draft
Give your AI agents something more useful than a prompt. Velocity through clarity.
Extract an Allium specification from an existing codebase. Use when the user has existing code and wants to distil behaviour into a spec, reverse engineer a specification from implementation, generate a spec from code, turn implementation into a behavioural specification, or document what a codebase does in Allium terms.
Run a structured discovery session to build an Allium specification through conversation. Use when the user wants to create a new spec from scratch, elicit or gather requirements, capture domain behaviour, specify a feature or system, define what a system should do, or is describing functionality and needs help shaping it into a specification.
Generate tests from Allium specifications. Use when the user wants to propagate tests, generate test files from a spec, write tests for a specification, create property-based tests, produce state machine tests, check test coverage against spec obligations, or understand what tests a specification requires.
Autonomously work on Jira backlog tickets, creating PRs and shepherding them to merge
| 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).
