datadog
- 128 skills
- 0 followers
- 3.8k repo stars
- yesterday last updated
- ▌ Follow Pr · datadog bundleMonitor the current PR's GitLab pipeline to completion, then report success or investigate a failure. Use when the user asks to follow, babysit, watch, or wait on a PR/pipeline, or just after pushing to / creating a PR.
- ▌ Write E2e · datadog bundleWrite or extend Datadog Agent new-e2e tests, including fakeintake coverage and the GitLab wiring that runs them; derives scope from the current diff when no target is named. Not for running tests that already exist (run-e2e, run-windows-e2e), or for judging whether a behavior belongs in E2E at all (e2e-audit).
- ▌ Injector Dev · datadogBuild, deploy, and test Datadog Agent components (agent, cluster-agent, operator, CSI driver) on a local Kubernetes cluster using the injector-dev CLI. Use when the user wants to iterate on local Agent or Operator change, spin up a local k8s test environment.
- ▌ Cws Btfhub Sync · datadogSync CWS BTFHub constants after adding a new constantfetch offset, so pre-BTF kernels can resolve it. Use when KMT secagent jobs log "failed to fetch constant for <name>".
- ▌ Run Windows E2e · datadog bundleRun Windows E2E tests (MSI install tests or Fleet Automation/installer tests) locally against AWS-provisioned VMs
- ▌ Create Component · datadogCreate a new Fx component using the modern def/fx/impl pattern (NOT legacy)
- ▌
- ▌ Update Otel Deps · datadogUse when a user asks to update, bump, or troubleshoot OpenTelemetry Collector dependencies in datadog-agent, including OCB build failures, ddflareextension golden files, static quality gates, or OTel transitive dependency conflicts.
- ▌ Create Core Check · datadogCreate a new Go core check that collects metrics and sends them to Datadog
- ▌ Create Epic Recap · datadog bundleUse when an engineer or manager asks to recap, summarize, or post an update on a Jira Epic — a progress update for an in-progress Epic (how far along it is, what's shipped so far, what's next) or a resolution recap for a finished one. Gathers child-issue progress, merged GitHub PRs, release notes, and Epic/child comments, previews a stakeholder-ready recap, and posts only after approval.
- ▌ Create Subcommand · datadogAdd a new CLI subcommand to an agent binary (agent, cluster-agent, etc.)
- ▌ Triage CI Failure · datadog bundleClassify a failed CI as either caused by an active incident, flakiness, or a true code regression. Use when a PR's pipeline is red and it isn't obvious whether the PR's own changes are at fault. Trigger phrases include: - "investigate this CI failure" - "please fix CI" - "why did this job fail" - "is there an incident affecting CI" - "should I retry this" This should also be invoked whenever the user asks you to investigate _or fix_ a failing CI, to ensure we don't spend hours trying to fix something broken upstream.
- ▌
- ▌ Review Pr Comments · datadogReview and triage PR review comments on the current branch — groups threads by file, separates bots from humans, walks through unresolved comments interactively
- ▌ Create Config Field · datadogAdd a new configuration field to the Datadog Agent (datadog.yaml) by declaring it in the config schema
- ▌
- ▌ Elicit · datadog bundleRun 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.
- ▌ Cws Iouring Coverage · datadogAudit CWS (runtime-security) io_uring functional-test coverage and add a functional test for any io_uring opcode whose operation CWS observes but that is not exercised through io_uring. Test-driven — coverage is judged by tests, never by reading eBPF/hook internals. Use when auditing io_uring test coverage or after new IORING_OP_ opcodes appear.
- ▌ Distill · datadog bundleExtract 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.
- ▌ Explain Lading Config · datadog bundleExplains a lading.yaml config file from the regression test suite, using the lading Rust source as ground truth for field meanings and defaults.
- ▌ Locate Config Setting · datadogFind where an Agent config setting or section is defined in the YAML schemas, and print its schema node, using `dda inv schema.locate`
- ▌ Update 3rd Party Libs · datadogUpdate a C/C++ third-party library under deps/ — bump version, reconcile sources/copts/config.h/patches, and verify the build.
- ▌ Create Runtime Setting · datadogCreate a new RuntimeSetting that can be changed at runtime via `agent config set/get` and the config API
- ▌ Create Status Provider · datadogAdd a new section to the agent status output (agent status command)
- ▌ Propagate · datadogGenerate 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.
- ▌ Quality Gate Size Analysis · datadogAnalyze static quality gate on-disk size changes, correlate with Confluence exception records and GitHub PRs by milestone
- ▌ Agent Supply Chain Newsletter · datadogGenerate the Agent Supply Chain newsletter by researching team activity on GitHub and Confluence, then creating a Confluence draft and Gmail draft
- ▌ Write Agent Health E2e · datadogCreate an E2E lifecycle test for a new health platform issue in test/new-e2e/tests/agent-health/