基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/DataDog/datadog-agent --skill create-go-module命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | create-go-module |
| description | Create a new Go module in the agent repository |
| allowed-tools | Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion |
| argument-hint | [module-path] |
| model | sonnet |
Create a new Go module in the datadog-agent multi-module repository. This repo has 100+ Go modules managed via modules.yml and inter-module replace directives.
Use AskUserQuestion to collect the following. If $ARGUMENTS provides the path, skip that question.
Module path: The path relative to the repo root (e.g. comp/core/mything/def, pkg/util/mypkg). This becomes github.com/DataDog/datadog-agent/<path>.
Does the directory already contain Go code?: If yes, the tool will also update dependent modules. If no, it just creates the go.mod and registers the module.
The create-module task requires all changes to be committed. Check with git status and warn the user if there are uncommitted changes.
dda inv create-module --path=<module-path>
This task automatically:
go.mod with the correct module path and Go versionreplace directives for inter-module dependenciesmodules.yml as independent: truetidy across all modulesinternal-deps-checker, check-mod-tidy, check-go-mod-replaces)Read modules.yml and review the new entry. The task sets independent: true by default. Adjust if needed:
| Field | Values | Notes |
|---|---|---|
independent | true/false | true = tagged and tested independently |
used_by_otel | true | Set if the module is used by the OTel agent build |
should_tag | false | Set for internal tooling modules that shouldn't be tagged |
should_test_condition | never/always | Override test behavior |
lint_targets / test_targets | list of paths | Override default targets |
Most modules use default (no special config) or just set used_by_otel: true.
Report whether the task succeeded or failed. If it failed, read the error output and help fix the issue.
create-module — the task may restore files on failure.go.work and all necessary replace directives are set up.modules.yml or dda inv modules.show./create-go-module — Interactive: prompts for the module path/create-go-module comp/core/mything/def — Pre-fills the pathMonitor 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.
Classify 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.
Write 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).