Migrate shellescape from github.com/alessio/shellescape to al.essio.dev/pkg/shellescape v1.6.0

The module changed its canonical path in v1.6.0. Update the import in
unixOSCommand.go, go.mod files, go.sum checksums, and the Bazel module
mapping accordingly.

Author: chouetz

.agents/skills/agent-supply-chain-newsletter/SKILL.md

@@ -0,0 +1,107 @@
+---
+name: agent-supply-chain-newsletter
+description: Generate the Agent Supply Chain newsletter by researching team activity on GitHub and Confluence, then creating a Confluence draft and Gmail draft
+argument-hint: "<period e.g. 'February-March 2026'>"
+---
+
+Generate the Agent Supply Chain newsletter for the period **$ARGUMENTS** by researching what team members accomplished on GitHub and Confluence, then producing both a Confluence blog post draft and a Gmail draft.
+
+## Step 1: Gather team members
+
+Fetch the current list of agent-supply-chain team members from GitHub:
+
+```bash
+gh api orgs/DataDog/teams/agent-supply-chain/members --paginate --jq '.[].login'
+```
+
+Ask the user if any members should be excluded (e.g. people who moved teams).
+
+## Step 2: Read past newsletters for format reference
+
+1. Search for the latest blog posts in the ASC1 Confluence space:
+   - `mcp__claude_ai_Atlassian__searchConfluenceUsingCql` with `cql`: `type = "blogpost" AND space = "ASC1" ORDER BY created DESC` (limit 3)
+2. Read the most recent newsletter with `mcp__claude_ai_Atlassian__getConfluencePage` (contentFormat: `markdown`, contentType: `blog`) to match its structure and tone.
+
+The newsletter format is:
+- **Header**: greeting, team links (ASC1, ABLD, BARX, ADX spaces), OKR link, support channel link
+- **"What's new?"** section organized by sub-team (Agent Developer Experience, Agent Build, Agent Delivery)
+- Each item has: a short title, **quantified impact** (time saved, percentage improvement, count), and **links to PRs or docs**
+- **"Did you know?"** section with one fun/useful tip
+- **Footer**: link to all newsletters, support channel reminder
+
+## Step 3: Research GitHub activity
+
+For each team member, launch background agents (use `run_in_background: true`) to search merged PRs during the period. Split into batches of ~8 members per agent to parallelize.
+
+Each agent should run, for every user:
+
+```bash
+# PRs in datadog-agent
+gh pr list --repo DataDog/datadog-agent --author USERNAME --state merged --search "merged:START_DATE..END_DATE" --limit 50 --json title,url,mergedAt,labels
+
+# PRs across the DataDog org (catches buildimages, k8s-ops, integrations-core, etc.)
+gh search prs --author USERNAME --owner DataDog --merged --limit 20 --json repository,title,url -- "merged:START_DATE..END_DATE"
+```
+
+Each agent should return a summary per user, grouped thematically (build improvements, CI/CD, new features, bug fixes, etc.). Skip trivial PRs (version bumps, dependency updates). Focus on items that **impact teams outside Agent Supply Chain**.
+
+## Step 4: Research Confluence activity
+
+Launch a background agent to search for relevant documentation created during the period:
+
+```
+mcp__claude_ai_Atlassian__searchConfluenceUsingCql
+```
+
+With CQL queries:
+- `space = "ASC1" AND lastModified >= "START_DATE" AND lastModified <= "END_DATE" ORDER BY lastModified DESC` (limit 25)
+- `space = "ADX" AND lastModified >= "START_DATE" AND lastModified <= "END_DATE" ORDER BY lastModified DESC` (limit 25)
+
+Identify RFCs, design docs, operational reports, and guides that are newsletter-worthy.
+
+## Step 5: Synthesize and write the newsletter
+
+Apply the newsletter guide's filter: **"Is this information impacting a team outside of the Agent Supply Chain group?"** Only include items where the answer is yes.
+
+For each item:
+- Provide a **quantifiable improvement** (time saved, percentage change, cost reduction) when available
+- Link to the relevant **PR, Confluence page, or documentation**
+- Keep descriptions concise (2-4 sentences max per item)
+
+Group items under:
+1. **Agent Developer Experience** (CI speed, developer tools, workflows, open source)
+2. **Agent Build** (Bazel migration, build system, platform support)
+3. **Agent Delivery** (releases, deployments, registries, security)
+
+End with a **"Did you know?"** section highlighting one interesting tool, feature, or tip.
+
+## Step 6: Create outputs
+
+### 6a. Confluence blog post draft
+
+Use `mcp__claude_ai_Atlassian__createConfluencePage` with:
+- `cloudId`: `datadoghq.atlassian.net`
+- `spaceId`: `4662624793` (ASC1 space)
+- `title`: `<Period> - Agent Supply Chain Monthly Update`
+- `contentType`: `blog`
+- `status`: `draft`
+- `contentFormat`: `markdown`
+
+### 6b. Gmail draft
+
+Use `mcp__claude_ai_Gmail__gmail_create_draft` with:
+- `to`: `agent-community@datadoghq.com`
+- `subject`: `<Period> - Agent Supply Chain Monthly Update`
+- `contentType`: `text/html`
+- Rich HTML body matching the Confluence content
+
+## Step 7: Present results
+
+Return to the user:
+1. Links to both the Confluence draft and Gmail draft
+2. A bullet-point summary of the sections covered
+3. Remind them to:
+   - Review both outputs for accuracy
+   - Send the Gmail to themselves first to verify formatting
+   - Schedule the final send between **2-4pm CET**, not on a Friday
+   - Ask for review in `#agent-devx-private` / from Damien Desmarets before publishing

.agents/skills/auto-jira/README.md

@@ -0,0 +1,75 @@
+# auto-jira
+
+Autonomously scans a Jira board backlog for eligible tickets and implements fixes as draft PRs. Once a draft PR is open, the skill moves on to the next ticket — CI, review, and merge are left for humans.
+
+## Usage
+
+```
+/auto-jira <BOARD-KEY> [flags]
+```
+
+## Flags
+
+| Flag | Required | Default | Description |
+|------|----------|---------|-------------|
+| `BOARD-KEY` | yes | — | Jira project key (e.g. `ACTP`, `AGENTCFG`, `CONTINT`) |
+| `--max-cards N` | no | `3` | Maximum number of PRs to create in this run |
+| `--before-date YYYY-MM-DD` | no | 30 days ago | Only consider tickets created before this date |
+| `--exclude word1,word2` | no | none | Skip tickets whose title contains any of these words (case-insensitive, comma-separated) |
+
+## Examples
+
+```
+# Scan the AGENTCFG board, up to 3 PRs (defaults)
+/auto-jira AGENTCFG
+
+# Up to 5 PRs
+/auto-jira AGENTCFG --max-cards 5
+
+# Only older tickets
+/auto-jira AGENTCFG --before-date 2026-02-12
+
+# Skip planning/spike tickets
+/auto-jira CONTINT --max-cards 2 --exclude RFC,spike,design
+
+# Full example
+/auto-jira AGENTCFG --max-cards 5 --before-date 2026-02-12 --exclude nodetreemodel,viper
+```
+
+## What it does
+
+For each eligible ticket (up to `--max-cards`), the skill:
+
+1. Queries the board backlog for unassigned tickets in the initial status (first entry of `jira_statuses` in `.ddqa/config.toml`) with no parent issue
+2. Evaluates each ticket for feasibility — skips vague, docs-only, or already-fixed issues
+3. Claims the ticket (assigns to you)
+4. Implements the fix, runs lint and tests, creates a single commit
+5. Opens a **draft PR** against `main` titled `[auto-jira][KEY] ...`
+6. Posts the PR link as a comment on the Jira ticket
+
+Progress is tracked locally in `AUTO_JIRA.md` (gitignored, never committed).
+
+## Ticket eligibility
+
+A ticket is eligible only if ALL of the following are true:
+
+- Status is the first entry of `jira_statuses` for the team in `.ddqa/config.toml` (typically `To Do`)
+- Assignee is empty
+- No parent issue
+- Created before `--before-date`
+- Label `do-not-autosolve` is NOT set
+- Title contains none of the `--exclude` words
+- Solvable by a code PR (not docs-only, not infra, not cross-team)
+- Not already fixed in the codebase
+
+To permanently exclude a ticket from auto-jira, add the `do-not-autosolve` label on the Jira issue.
+
+## Running unattended
+
+For unattended/background operation, consider running Claude with `--dangerously-skip-permissions` to avoid permission prompts:
+
+```bash
+claude --dangerously-skip-permissions
+```
+
+Then invoke the skill normally: `/auto-jira AGENTCFG --max-cards 5`