From 821db18a51e18f6ccf0bddb3e263816c81e2547c Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 19 May 2026 15:49:58 +0000 Subject: [PATCH 1/4] Initial plan From 768f0ce2374b8d3188fc448d8d091032fad5512e Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 19 May 2026 15:59:20 +0000 Subject: [PATCH 2/4] chore: outline plan for workflow report formatting normalization Agent-Logs-Url: https://github.com/github/gh-aw/sessions/5fb4c2b1-31e6-4b26-b054-27602b985ce3 Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com> --- .github/workflows/smoke-otel-backends.lock.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/smoke-otel-backends.lock.yml b/.github/workflows/smoke-otel-backends.lock.yml index a581ff20194..c5f41ee2366 100644 --- a/.github/workflows/smoke-otel-backends.lock.yml +++ b/.github/workflows/smoke-otel-backends.lock.yml @@ -773,7 +773,7 @@ jobs: "url": "https://mcp.datadoghq.com/api/unstable/mcp-server/mcp?toolsets=core", "headers": { "DD_API_KEY": "\${DD_API_KEY}", - "DD_APPLICATION_KEY": "\${DD_APP_KEY}", + "DD_APPLICATION_KEY": "\${DD_APPLICATION_KEY}", "DD_SITE": "\${DD_SITE}" }, "tools": [ From c57d63425219a59e69610d97412424a5903b44ea Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 19 May 2026 16:02:41 +0000 Subject: [PATCH 3/4] docs(workflows): add report formatting requirements to reporting prompts Agent-Logs-Url: https://github.com/github/gh-aw/sessions/5fb4c2b1-31e6-4b26-b054-27602b985ce3 Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com> --- .github/workflows/issue-monster.md | 13 +++++++++++++ .github/workflows/pr-sous-chef.md | 13 +++++++++++++ .github/workflows/smoke-ci.md | 13 +++++++++++++ 3 files changed, 39 insertions(+) diff --git a/.github/workflows/issue-monster.md b/.github/workflows/issue-monster.md index 4ebc54b59cf..7ec7a7418b2 100644 --- a/.github/workflows/issue-monster.md +++ b/.github/workflows/issue-monster.md @@ -631,6 +631,19 @@ Issue Monster runs frequently (every 30 minutes), so keeping each run lean is cr - ✅ **Skip integrity-blocked issues**: If `issue_read` is blocked by integrity policy, skip that issue and continue — never call `missing_data` for integrity errors - ❌ **Don't force batching**: If only 1-2 clearly separate issues exist, assign only those +## Formatting Requirements + +- **Header Levels**: Use h3 (`###`) or lower for all headers in your report to maintain proper document hierarchy. Never use h1 (`#`) or h2 (`##`) headers. +- **Progressive Disclosure**: Wrap long sections or verbose details in `
Section Name` tags to improve readability and reduce scrolling. +- Keep critical information visible (summary, key outcomes, and recommendations) and use collapsible sections for secondary details. + +### Recommended Report Structure + +1. **Overview**: 1-2 paragraphs summarizing key findings (always visible) +2. **Critical Information**: Key metrics, status, critical issues (always visible) +3. **Details**: Use `
Section Name` for expanded content +4. **Recommendations**: Actionable next steps (always visible) + ## Success Criteria A successful run means: diff --git a/.github/workflows/pr-sous-chef.md b/.github/workflows/pr-sous-chef.md index 08713a5be97..0967f808e41 100644 --- a/.github/workflows/pr-sous-chef.md +++ b/.github/workflows/pr-sous-chef.md @@ -234,6 +234,19 @@ At the end, call **exactly one** `noop` with a compact summary including counts - branch_update_attempts - formatter_pushes (number of PRs that had formatting fixes committed and pushed) +## Formatting Requirements + +- **Header Levels**: Use h3 (`###`) or lower for all headers in your report to maintain proper document hierarchy. Never use h1 (`#`) or h2 (`##`) headers. +- **Progressive Disclosure**: Wrap long sections or verbose details in `
Section Name` tags to improve readability and reduce scrolling. +- Keep critical information visible (summary, key outcomes, and recommendations) and use collapsible sections for secondary details. + +### Recommended Report Structure + +1. **Overview**: 1-2 paragraphs summarizing key findings (always visible) +2. **Critical Information**: Key metrics, status, critical issues (always visible) +3. **Details**: Use `
Section Name` for expanded content +4. **Recommendations**: Actionable next steps (always visible) + ## agent: `pr-processor` --- description: Processes one PR with minimal API calls and returns skip/nudge decisions diff --git a/.github/workflows/smoke-ci.md b/.github/workflows/smoke-ci.md index 01bdeb9db0b..9a7d20af55e 100644 --- a/.github/workflows/smoke-ci.md +++ b/.github/workflows/smoke-ci.md @@ -89,5 +89,18 @@ For scheduled runs (non-pull_request), use GitHub MCP to find the newest open pu - If one exists, call `update_pull_request` for that PR number with `operation: "append"` and a short body line including the run URL. - If none exists, call `noop` with a short message indicating no PR was available. +## Formatting Requirements + +- **Header Levels**: Use h3 (`###`) or lower for all headers in your report to maintain proper document hierarchy. Never use h1 (`#`) or h2 (`##`) headers. +- **Progressive Disclosure**: Wrap long sections or verbose details in `
Section Name` tags to improve readability and reduce scrolling. +- Keep critical information visible (summary, key outcomes, and recommendations) and use collapsible sections for secondary details. + +### Recommended Report Structure + +1. **Overview**: 1-2 paragraphs summarizing key findings (always visible) +2. **Critical Information**: Key metrics, status, critical issues (always visible) +3. **Details**: Use `
Section Name` for expanded content +4. **Recommendations**: Actionable next steps (always visible) + Do not run any shell commands. Do not call any tools other than `cache-memory`, `repo-memory`, `github`, `create_issue`, `update_issue`, `add_comment`, `add_labels`, `remove_labels`, `update_pull_request`, or `noop`. From fde222327cd3a20bea52b6e133cf74e1358cd62e Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 19 May 2026 16:08:05 +0000 Subject: [PATCH 4/4] chore: revert unintended smoke-otel lockfile change Agent-Logs-Url: https://github.com/github/gh-aw/sessions/5fb4c2b1-31e6-4b26-b054-27602b985ce3 Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com> --- .github/workflows/smoke-otel-backends.lock.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/smoke-otel-backends.lock.yml b/.github/workflows/smoke-otel-backends.lock.yml index c5f41ee2366..a581ff20194 100644 --- a/.github/workflows/smoke-otel-backends.lock.yml +++ b/.github/workflows/smoke-otel-backends.lock.yml @@ -773,7 +773,7 @@ jobs: "url": "https://mcp.datadoghq.com/api/unstable/mcp-server/mcp?toolsets=core", "headers": { "DD_API_KEY": "\${DD_API_KEY}", - "DD_APPLICATION_KEY": "\${DD_APPLICATION_KEY}", + "DD_APPLICATION_KEY": "\${DD_APP_KEY}", "DD_SITE": "\${DD_SITE}" }, "tools": [