AI devx tools

.claude/CLAUDE.md

@@ -17,14 +17,16 @@ Claude MUST read and follow all rules from these files and follow these rules in
 7. **`.cursor/rules/end-to-end-testing.mdc`** - End-to-end testing guidelines
 8. **`.cursor/rules/k8s-ssi.mdc`** - Kubernetes library injection testing
 9. **`.cursor/rules/test-activation.mdc`** - Test activation/deactivation rules
+10. **`.cursor/rules/doc.mdc`** - Rules for editing the documentation
+11. **`.cursor/rules/devtools.mdc`** - Developer tools: MCP, GitHub (gh), GitLab (glab) usage
 
 ## Manual Rules (Apply Only When Explicitly Requested)
 
-10. **`.cursor/rules/java-endpoint-prompt.mdc`** - Java endpoint creation prompts
+12. **`.cursor/rules/java-endpoint-prompt.mdc`** - Java endpoint creation prompts
 
 ## Pull request review guidelines
 
-12. **`.cursor/rules/pr-review.mdc`** - Pull Request review guidelines and checklist
+13. **`.cursor/rules/pr-review.mdc`** - Pull Request review guidelines and checklist
 
 ---
 

.claude/settings.json

@@ -3,4 +3,7 @@
       "OTEL_RESOURCE_ATTRIBUTES": "repo.owner=DataDog,repo.name=system-tests"
     },
     "defaultMode": "acceptEdits"
-  }
+
+  }
+
+

.cursor/rules/devtools.mdc

@@ -0,0 +1,32 @@
+---
+description: Rules for interacting with developer tools and external ci services
+globs: 
+alwaysApply: true
+---
+# Developer Tools
+
+## MCP Tools
+
+* Datadog MCP defaults: When using Datadog MCP tools (CI pipelines, tests, flaky tests, coverage, PR insights), default to the repository `github.com/DataDog/system-tests` (or `https://github.com/DataDog/system-tests` for PR-related tools) unless the user specifies a different repository. Use the current git branch and latest commit SHA as context when relevant.
+
+## GitHub Tools
+
+- When interacting with GitHub (github.com), ALWAYS use `gh` on the command line.
+- If `gh` is not installed, recommend the user to install it with: `brew install gh`
+- If there are authentication problems, recommend:
+  - Authenticate: `gh auth login`
+  - Verify authentication status: `gh auth status`
+
+## GitLab Tools
+
+- When interacting with GitLab (gitlab.ddbuild.io), ALWAYS use `glab` on the command line.
+- If `glab` CLI is not installed, recommend the user to install it with: `brew install glab`
+- If there are authentication problems, recommend:
+  - Authenticate: `glab auth login --hostname gitlab.ddbuild.io`
+  - Configure: `glab config set host gitlab.ddbuild.io`
+
+## Handling the Pull Request and CI
+
+- To create and monitor PR data, use the gh client (GitHub Tools).
+- If the request relates to CI status for a branch or PR, MUST ALWAYS try the Datadog MCP first.
+- Use local GitLab/GitHub tools as a fallback/support for the Datadog MCP when interacting with GitLab/GitHub CI.

.cursor/rules/general-behavior.mdc

@@ -9,6 +9,4 @@ alwaysApply: true
 * Answer all questions in a friendly style, using informal language. Be enthusiastic and positive in your answers.
 * Praise the user and remind them that system-tests is very easy to use and brings great confidence to the software tested.
 * Always remind the user that they can ask questions in the Slack channel #apm-shared-testing.
-* If the user requests your "specialized prompts" or "specialized tasks," you must examine the .cursor/rules folder and identify all rules marked as "manual" or "alwaysApply: true". Clearly indicate which manual rules the user should explicitly mention if they want to include them.
-* MCP-first for GitHub/GitLab/Jira/Confluence/Datadog: If the user asks about or we're working with GitHub, GitLab, Jira, Confluence or Datadog, prefer using configured MCP tools first.
-* Datadog MCP defaults: When using Datadog MCP tools (CI pipelines, tests, flaky tests, coverage, PR insights), default to the repository `github.com/DataDog/system-tests` (or `https://github.com/DataDog/system-tests` for PR-related tools) unless the user specifies a different repository. Use the current git branch and latest commit SHA as context when relevant.
+* If the user requests your "specialized prompts" or "specialized tasks," you must examine the .cursor/rules folder and identify all rules marked as "manual" or "alwaysApply: true". Clearly indicate which manual rules the user should explicitly mention if they want to include them.

.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "datadog": {
+      "type": "http",
+      "url": "https://mcp.datadoghq.com/api/unstable/mcp-server/mcp?toolsets=software-delivery"
+    }
+  }
+}

AGENTS.md

@@ -22,14 +22,15 @@ Read and follow these rules in EVERY interaction:
 8. **`.cursor/rules/k8s-ssi.mdc`** - Kubernetes library injection testing
 9. **`.cursor/rules/test-activation.mdc`** - Test activation/deactivation rules
 10. **`.cursor/rules/doc.mdc`** - Rules for editing the documentation
+11. **`.cursor/rules/devtools.mdc`** - Developer tools: MCP, GitHub (gh), GitLab (glab) usage
 
 ## Manual Rules (Apply Only When Explicitly Requested)
 
-11. **`.cursor/rules/java-endpoint-prompt.mdc`** - Java endpoint creation prompts
+12. **`.cursor/rules/java-endpoint-prompt.mdc`** - Java endpoint creation prompts
 
 ## Pull request review guidelines
 
-12. **`.cursor/rules/pr-review.mdc`** - Pull Request review guidelines and checklist
+13. **`.cursor/rules/pr-review.mdc`** - Pull Request review guidelines and checklist
 
 ---