This PR implements the output.comment output type that creates issue or pull request comments from agent output, following the same patterns as the existing output.issue functionality. Additionally, it enables workflows to support multiple output types simultaneously.

What's New

Users can now configure workflows to automatically post agent output as comments on issues or pull requests, and can combine multiple output types in a single workflow:

---
on:
  issues:
    types: [opened, labeled]
  pull_request:
    types: [opened, synchronize]
permissions:
  contents: read
  actions: read
engine: claude
output:
  issue:
    title-prefix: "[claude-test] "
    labels: [claude, automation, haiku]
  comment: {}
---

# Issue/PR Analysis Agent

Analyze the issue or pull request and provide feedback.
Write your analysis to ${{ env.GITHUB_AW_OUTPUT }} at the end.

Key Features

• Smart Context Detection: Automatically detects whether the workflow is running in an issue or pull request context
• Conditional Execution: The comment job only runs when github.event.issue.number or github.event.pull_request.number is present, gracefully skipping for other event types
• Proper Permissions: Separate job with issues: write and pull-requests: write permissions, keeping the main job minimal
• Full Agent Output: Posts the entire agent output as comment content without parsing (unlike issue creation which splits title/body)
• Multiple Output Support: Workflows can now have both issue and comment outputs simultaneously, enabling rich automation workflows

Implementation Details

• Job Name: create_issue_comment with 10-minute timeout
• Dependencies: Runs after the main agent job completes
• API: Uses GitHub Issues API (works for both issues and PRs)
• Outputs: Returns comment_id and comment_url for downstream jobs
• Schema: Updated to support the new output.comment configuration

Example Generated Workflow

The compiler generates a conditional job that:

1. Receives agent output from the main job via job outputs
2. Checks GitHub context to determine issue/PR number
3. Posts comment using github.rest.issues.createComment()
4. Skips execution if not in issue/PR context

This maintains the same separation of concerns as output.issue where the main job doesn't need write permissions, improving security and following the principle of least privilege.

The test workflow test-claude.md has been updated to demonstrate this functionality by both creating issues AND posting analysis results as PR comments, showcasing the multiple output support capability.

Fixes #129.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.