Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/smoke-claude.lock.yml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

18 changes: 12 additions & 6 deletions .github/workflows/smoke-claude.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ safe-outputs:
run-started: "💥 **WHOOSH!** [{workflow_name}]({run_url}) springs into action on this {event_type}! *[Panel 1 begins...]*"
run-success: "🎬 **THE END** — [{workflow_name}]({run_url}) **MISSION: ACCOMPLISHED!** The hero saves the day! ✨"
run-failure: "💫 **TO BE CONTINUED...** [{workflow_name}]({run_url}) {status}! Our hero faces unexpected challenges..."
timeout-minutes: 15
timeout-minutes: 10
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot keep it 15

---

# Smoke Test: Claude Engine Validation.
Expand All @@ -91,26 +91,32 @@ timeout-minutes: 15
- Extract the discussion number from the result (e.g., if the result is `{"number": 123, "title": "...", ...}`, extract 123)
- Use the `add_comment` tool with `discussion_number: <extracted_number>` to add a fun, comic-book style comment stating that the smoke test agent was here
10. **Agentic Workflows MCP Testing**:
- Use the `agentic-workflows` MCP tool with the `status` method to query the status of the "smoke-claude" workflow in ${{ github.repository }}
- Extract key information: total runs, recent success/failure status, last run time
- Write a summary of the smoke-claude workflow status to `/tmp/gh-aw/agent/smoke-claude-status-${{ github.run_id }}.txt`
- Use bash to display the file contents
- Call the `agentic-workflows` MCP tool using the `status` method with workflow name `smoke-claude` to query workflow status
- If the tool returns an error or no results, mark this test as ❌ and note "Tool unavailable or workflow not found" but continue to the Output section
- If the tool succeeds, extract key information from the response: total runs, success/failure counts, last run timestamp
- Write a summary of the results to `/tmp/gh-aw/agent/smoke-claude-status-${{ github.run_id }}.txt` (create directory if needed)
- Use bash to verify the file was created and display its contents

## Output

1. **Create an issue** with a summary of the smoke test run:
**CRITICAL: You MUST create an issue regardless of test results - this is a required safe output.**

1. **ALWAYS create an issue** with a summary of the smoke test run:
- Title: "Smoke Test: Claude - ${{ github.run_id }}"
- Body should include:
- Test results (✅ or ❌ for each test)
- Overall status: PASS or FAIL
- Run URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
- Timestamp
- If ANY test fails, include error details in the issue body
- This issue MUST be created before any other safe output operations

2. **Only if this workflow was triggered by a pull_request event**: Use the `add_comment` tool to add a **very brief** comment (max 5-10 lines) to the triggering pull request (omit the `item_number` parameter to auto-target the triggering PR) with:
- PR titles only (no descriptions)
- ✅ or ❌ for each test result
- Overall status: PASS or FAIL

3. Use the `add_comment` tool with `item_number` set to the discussion number you extracted in step 9 to add a **fun comic-book style comment** to that discussion - be playful and use comic-book language like "💥 WHOOSH!"
Copy link

Copilot AI Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In Output step 3, the instructions say to call add_comment with item_number set to the extracted discussion number. Elsewhere in this workflow (step 9) and in other smoke workflows, discussions are targeted via discussion_number, and using item_number risks posting to an issue/PR with the same number instead of the discussion. Consider switching this to discussion_number: <extracted_number> for consistency and correctness.

Suggested change
3. Use the `add_comment` tool with `item_number` set to the discussion number you extracted in step 9 to add a **fun comic-book style comment** to that discussion - be playful and use comic-book language like "💥 WHOOSH!"
3. Use the `add_comment` tool with `discussion_number` set to the discussion number you extracted in step 9 to add a **fun comic-book style comment** to that discussion - be playful and use comic-book language like "💥 WHOOSH!"

Copilot uses AI. Check for mistakes.
- If step 9 failed to extract a discussion number, skip this step

If all tests pass, use the `add_labels` tool to add the label `smoke-claude` to the pull request (omit the `item_number` parameter to auto-target the triggering PR if this workflow was triggered by a pull_request event).
1 change: 0 additions & 1 deletion docs/src/content/docs/agent-factory-status.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,6 @@ These are experimental agentic workflows used by the GitHub Next team to learn,
| [Schema Consistency Checker](https://github.com/github/gh-aw/blob/main/.github/workflows/schema-consistency-checker.md) | claude | [![Schema Consistency Checker](https://github.com/github/gh-aw/actions/workflows/schema-consistency-checker.lock.yml/badge.svg)](https://github.com/github/gh-aw/actions/workflows/schema-consistency-checker.lock.yml) | - | - |
| [Scout](https://github.com/github/gh-aw/blob/main/.github/workflows/scout.md) | claude | [![Scout](https://github.com/github/gh-aw/actions/workflows/scout.lock.yml/badge.svg)](https://github.com/github/gh-aw/actions/workflows/scout.lock.yml) | - | `/scout` |
| [Security Compliance Campaign](https://github.com/github/gh-aw/blob/main/.github/workflows/security-compliance.md) | copilot | [![Security Compliance Campaign](https://github.com/github/gh-aw/actions/workflows/security-compliance.lock.yml/badge.svg)](https://github.com/github/gh-aw/actions/workflows/security-compliance.lock.yml) | - | - |
| [Security Fix PR](https://github.com/github/gh-aw/blob/main/.github/workflows/security-fix-pr.md) | copilot | [![Security Fix PR](https://github.com/github/gh-aw/actions/workflows/security-fix-pr.lock.yml/badge.svg)](https://github.com/github/gh-aw/actions/workflows/security-fix-pr.lock.yml) | - | - |
| [Security Guard Agent 🛡️](https://github.com/github/gh-aw/blob/main/.github/workflows/security-guard.md) | copilot | [![Security Guard Agent 🛡️](https://github.com/github/gh-aw/actions/workflows/security-guard.lock.yml/badge.svg)](https://github.com/github/gh-aw/actions/workflows/security-guard.lock.yml) | - | - |
| [Security Review Agent 🔒](https://github.com/github/gh-aw/blob/main/.github/workflows/security-review.md) | copilot | [![Security Review Agent 🔒](https://github.com/github/gh-aw/actions/workflows/security-review.lock.yml/badge.svg)](https://github.com/github/gh-aw/actions/workflows/security-review.lock.yml) | - | `/security` |
| [Semantic Function Refactoring](https://github.com/github/gh-aw/blob/main/.github/workflows/semantic-function-refactor.md) | claude | [![Semantic Function Refactoring](https://github.com/github/gh-aw/actions/workflows/semantic-function-refactor.lock.yml/badge.svg)](https://github.com/github/gh-aw/actions/workflows/semantic-function-refactor.lock.yml) | - | - |
Expand Down
Loading