new ci

[ampelectrecuted]

add new feature to issue assistant called poem generator that generate a poem for every issue and pr

[traycerai]

Plan

Observations

The repository uses GitHub Actions for CI/CD automation with a sophisticated issue assistant in file:.github/workflows/ulti.yaml that handles issue summarization, categorization, and duplicate detection using AI inference. The workflow uses actions/ai-inference@v1 with models like gpt-4o-mini and mistral-ai/Ministral-3B. There's a separate PR testing workflow in file:.github/workflows/prtest.yml and examples of AI-powered features in file:.github/workflows/stale-pr-checker.yml and file:.github/workflows/spam-guard.yml. Currently, no poem generation feature exists.

Approach

The implementation will add a poem generator feature to both issue and PR workflows by creating new steps that use AI inference to generate creative poems based on the issue/PR content. For issues, the poem generator will be integrated into the existing file:.github/workflows/ulti.yaml workflow as a new step after the summary generation. For PRs, a new lightweight workflow will be created that triggers on PR open/edit events. Both will use the actions/ai-inference@v1 action with an appropriate model and post the generated poem as a comment.

Implementation Steps

1. Add Poem Generator to Issue Workflow

File: file:.github/workflows/ulti.yaml

Add a new job step after the "NORMAL SUMMARY" section (around line 737) to generate and post poems for issues:

# ------------------------------------------------------
# 🎭 POEM GENERATOR: Generate creative poem for issue
# ------------------------------------------------------
- name: Generate Issue Poem with AI
  id: generate-poem
  uses: actions/ai-inference@v1
  with:
    model: 'gpt-4o-mini'
    prompt: |
      You are a creative poet for the OmniBlocks scratch-gui project.
      
      Write a short, playful poem (4-8 lines) about this issue:
      
      **Issue Title:** ${{ github.event.issue.title }}
      **Issue Body:**
      ${{ github.event.issue.body }}
      
      Guidelines:
      - Keep it fun, lighthearted, and encouraging
      - Reference the issue topic creatively
      - Use emojis sparingly (1-2 max)
      - Make it rhyme or have rhythm
      - Keep it under 100 words
      - Be respectful and professional
      
      Output only the poem, no explanations or metadata.

- name: Post Poem Comment
  if: steps.generate-poem.outputs.response != ''
  env:
    GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    POEM: ${{ steps.generate-poem.outputs.response }}
  run: |
    COMMENT="## 🎭 Issue Poem

    $POEM

    ---
    _Generated with ❤️ by the OmniBlocks Poetry Bot_"
    
    echo "$COMMENT" | gh issue comment ${{ github.event.issue.number }} --body-file -

Integration Points:

• Add these steps after line 736 (after the "NORMAL SUMMARY" step)
• Ensure the step runs only when no special keywords (security, spam, close) are triggered
• Use the same conditional logic as the "NORMAL SUMMARY" step: if: steps.parse-response.outputs.keyword == 'none'

2. Create PR Poem Generator Workflow

File: file:.github/workflows/pr-poem-generator.yml (new file)

Create a new workflow specifically for generating poems on pull requests:

name: PR Poem Generator 🎭

on:
  pull_request:
    types: [opened, edited]
  pull_request_target:
    types: [opened, edited]

permissions:
  pull-requests: write
  contents: read

jobs:
  generate-pr-poem:
    runs-on: ubuntu-latest
    # Skip for bot PRs
    if: github.event.pull_request.user.type != 'Bot'
    
    steps:
      - name: Add Initial Reaction
        uses: actions/github-script@v7
        with:
          script: |
            await github.rest.reactions.createForIssue({
              owner: context.repo.owner,
              repo: context.repo.repo,
              issue_number: context.issue.number,
              content: 'rocket'
            });
      
      - name: Generate PR Poem with AI
        id: generate-poem
        uses: actions/ai-inference@v1
        with:
          model: 'gpt-4o-mini'
          prompt: |
            You are a creative poet for the OmniBlocks scratch-gui project.
            
            Write a short, playful poem (4-8 lines) about this pull request:
            
            **PR Title:** ${{ github.event.pull_request.title }}
            **PR Description:**
            ${{ github.event.pull_request.body }}
            **Author:** @${{ github.event.pull_request.user.login }}
            
            Guidelines:
            - Keep it fun, lighthearted, and encouraging
            - Reference the PR changes creatively
            - Celebrate the contributor's effort
            - Use emojis sparingly (1-2 max)
            - Make it rhyme or have rhythm
            - Keep it under 100 words
            - Be respectful and professional
            
            Output only the poem, no explanations or metadata.
      
      - name: Post Poem Comment
        uses: actions/github-script@v7
        env:
          POEM: ${{ steps.generate-poem.outputs.response }}
        with:
          script: |
            const poem = process.env.POEM || 
              `A contribution so fine,\nYour code will surely shine! ✨`;
            
            const comment = `## 🎭 Pull Request Poem

            ${poem}

            ---
            _Generated with ❤️ by the OmniBlocks Poetry Bot_`;
            
            await github.rest.issues.createComment({
              owner: context.repo.owner,
              repo: context.repo.repo,
              issue_number: context.issue.number,
              body: comment
            });
            
            console.log('✅ Posted poem to PR #' + context.issue.number);

Key Features:

• Triggers on PR opened and edited events
• Uses both pull_request and pull_request_target for fork PRs
• Skips bot-created PRs to avoid noise
• Adds a rocket reaction immediately for quick feedback
• Falls back to a default poem if AI generation fails
• Uses actions/github-script@v7 for posting comments (consistent with other workflows)

3. Workflow Architecture

sequenceDiagram
    participant User
    participant GitHub
    participant IssueWorkflow as ulti.yaml
    participant PRWorkflow as pr-poem-generator.yml
    participant AI as AI Inference
    
    User->>GitHub: Opens/Edits Issue
    GitHub->>IssueWorkflow: Trigger workflow
    IssueWorkflow->>IssueWorkflow: Run duplicate detection
    IssueWorkflow->>IssueWorkflow: Run summarization
    IssueWorkflow->>AI: Generate poem for issue
    AI-->>IssueWorkflow: Return poem
    IssueWorkflow->>GitHub: Post poem comment
    
    User->>GitHub: Opens/Edits PR
    GitHub->>PRWorkflow: Trigger workflow
    PRWorkflow->>GitHub: Add rocket reaction
    PRWorkflow->>AI: Generate poem for PR
    AI-->>PRWorkflow: Return poem
    PRWorkflow->>GitHub: Post poem comment

Loading

4. Testing Considerations

Manual Testing Steps:

1. Create a test issue with various content types (bug report, feature request, question)
2. Verify poem is generated and posted as a comment
3. Check that poem is relevant to issue content
4. Create a test PR with different change types
5. Verify PR poem is generated and posted
6. Test with bot-created PRs to ensure they're skipped
7. Test error handling when AI inference fails

Edge Cases to Handle:

• Empty issue/PR bodies
• Very long issue/PR descriptions (truncation may be needed)
• Special characters in titles/bodies
• Bot-created issues/PRs (should skip)
• Rate limiting on AI inference API
• Network failures during AI generation

5. Configuration Options

Model Selection:

• Current: gpt-4o-mini (balanced quality and speed)
• Alternative: mistral-ai/Ministral-3B (faster, lower cost)
• Can be configured per workflow based on requirements

Poem Style Customization:
The AI prompt can be adjusted to change poem characteristics:

• Length: Currently 4-8 lines, can be modified
• Style: Currently playful/lighthearted, can be formal/technical
• Rhyme scheme: Currently flexible, can enforce specific patterns
• Emoji usage: Currently minimal (1-2), can be increased/removed

6. Integration Checklist

Component	File	Action
Issue Poem Generator	file:.github/workflows/ulti.yaml	Add new steps after line 736
PR Poem Generator	file:.github/workflows/pr-poem-generator.yml	Create new file
Permissions	Both workflows	Verify issues: write and pull-requests: write
AI Model Access	Both workflows	Ensure models: read permission exists
Error Handling	Both workflows	Add fallback poems for AI failures
Bot Detection	Both workflows	Skip bot-created issues/PRs

7. Deployment Notes

Prerequisites:

• GitHub Actions must have access to actions/ai-inference@v1
• Repository must have AI inference enabled
• Appropriate permissions must be granted to workflows

Rollout Strategy:

1. Deploy PR poem generator first (lower risk, isolated workflow)
2. Monitor for 1-2 days to ensure stability
3. Deploy issue poem generator to ulti.yaml
4. Monitor both workflows for performance and quality

Monitoring:

• Check workflow run logs for AI inference errors
• Review generated poems for quality and appropriateness
• Monitor API rate limits and costs
• Collect user feedback on poem feature

Import In IDE

🤖 Prompt for AI Agents

## Observations

The repository uses GitHub Actions for CI/CD automation with a sophisticated issue assistant in `file:.github/workflows/ulti.yaml` that handles issue summarization, categorization, and duplicate detection using AI inference. The workflow uses `actions/ai-inference@v1` with models like `gpt-4o-mini` and `mistral-ai/Ministral-3B`. There's a separate PR testing workflow in `file:.github/workflows/prtest.yml` and examples of AI-powered features in `file:.github/workflows/stale-pr-checker.yml` and `file:.github/workflows/spam-guard.yml`. Currently, no poem generation feature exists.

## Approach

The implementation will add a poem generator feature to both issue and PR workflows by creating new steps that use AI inference to generate creative poems based on the issue/PR content. For issues, the poem generator will be integrated into the existing `file:.github/workflows/ulti.yaml` workflow as a new step after the summary generation. For PRs, a new lightweight workflow will be created that triggers on PR open/edit events. Both will use the `actions/ai-inference@v1` action with an appropriate model and post the generated poem as a comment.

## Implementation Steps

### 1. Add Poem Generator to Issue Workflow

**File**: `file:.github/workflows/ulti.yaml`

Add a new job step after the "NORMAL SUMMARY" section (around line 737) to generate and post poems for issues:

```yaml
# ------------------------------------------------------
# 🎭 POEM GENERATOR: Generate creative poem for issue
# ------------------------------------------------------
- name: Generate Issue Poem with AI
  id: generate-poem
  uses: actions/ai-inference@v1
  with:
    model: 'gpt-4o-mini'
    prompt: |
      You are a creative poet for the OmniBlocks scratch-gui project.
      
      Write a short, playful poem (4-8 lines) about this issue:
      
      **Issue Title:** ${{ github.event.issue.title }}
      **Issue Body:**
      ${{ github.event.issue.body }}
      
      Guidelines:
      - Keep it fun, lighthearted, and encouraging
      - Reference the issue topic creatively
      - Use emojis sparingly (1-2 max)
      - Make it rhyme or have rhythm
      - Keep it under 100 words
      - Be respectful and professional
      
      Output only the poem, no explanations or metadata.

- name: Post Poem Comment
  if: steps.generate-poem.outputs.response != ''
  env:
    GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    POEM: ${{ steps.generate-poem.outputs.response }}
  run: |
    COMMENT="## 🎭 Issue Poem

    $POEM

    ---
    _Generated with ❤️ by the OmniBlocks Poetry Bot_"
    
    echo "$COMMENT" | gh issue comment ${{ github.event.issue.number }} --body-file -
```

**Integration Points:**
- Add these steps after line 736 (after the "NORMAL SUMMARY" step)
- Ensure the step runs only when no special keywords (security, spam, close) are triggered
- Use the same conditional logic as the "NORMAL SUMMARY" step: `if: steps.parse-response.outputs.keyword == 'none'`

### 2. Create PR Poem Generator Workflow

**File**: `file:.github/workflows/pr-poem-generator.yml` (new file)

Create a new workflow specifically for generating poems on pull requests:

```yaml
name: PR Poem Generator 🎭

on:
  pull_request:
    types: [opened, edited]
  pull_request_target:
    types: [opened, edited]

permissions:
  pull-requests: write
  contents: read

jobs:
  generate-pr-poem:
    runs-on: ubuntu-latest
    # Skip for bot PRs
    if: github.event.pull_request.user.type != 'Bot'
    
    steps:
      - name: Add Initial Reaction
        uses: actions/github-script@v7
        with:
          script: |
            await github.rest.reactions.createForIssue({
              owner: context.repo.owner,
              repo: context.repo.repo,
              issue_number: context.issue.number,
              content: 'rocket'
            });
      
      - name: Generate PR Poem with AI
        id: generate-poem
        uses: actions/ai-inference@v1
        with:
          model: 'gpt-4o-mini'
          prompt: |
            You are a creative poet for the OmniBlocks scratch-gui project.
            
            Write a short, playful poem (4-8 lines) about this pull request:
            
            **PR Title:** ${{ github.event.pull_request.title }}
            **PR Description:**
            ${{ github.event.pull_request.body }}
            **Author:** @${{ github.event.pull_request.user.login }}
            
            Guidelines:
            - Keep it fun, lighthearted, and encouraging
            - Reference the PR changes creatively
            - Celebrate the contributor's effort
            - Use emojis sparingly (1-2 max)
            - Make it rhyme or have rhythm
            - Keep it under 100 words
            - Be respectful and professional
            
            Output only the poem, no explanations or metadata.
      
      - name: Post Poem Comment
        uses: actions/github-script@v7
        env:
          POEM: ${{ steps.generate-poem.outputs.response }}
        with:
          script: |
            const poem = process.env.POEM || 
              `A contribution so fine,\nYour code will surely shine! ✨`;
            
            const comment = `## 🎭 Pull Request Poem

            ${poem}

            ---
            _Generated with ❤️ by the OmniBlocks Poetry Bot_`;
            
            await github.rest.issues.createComment({
              owner: context.repo.owner,
              repo: context.repo.repo,
              issue_number: context.issue.number,
              body: comment
            });
            
            console.log('✅ Posted poem to PR #' + context.issue.number);
```

**Key Features:**
- Triggers on PR opened and edited events
- Uses both `pull_request` and `pull_request_target` for fork PRs
- Skips bot-created PRs to avoid noise
- Adds a rocket reaction immediately for quick feedback
- Falls back to a default poem if AI generation fails
- Uses `actions/github-script@v7` for posting comments (consistent with other workflows)

### 3. Workflow Architecture

```mermaid
sequenceDiagram
    participant User
    participant GitHub
    participant IssueWorkflow as ulti.yaml
    participant PRWorkflow as pr-poem-generator.yml
    participant AI as AI Inference
    
    User->>GitHub: Opens/Edits Issue
    GitHub->>IssueWorkflow: Trigger workflow
    IssueWorkflow->>IssueWorkflow: Run duplicate detection
    IssueWorkflow->>IssueWorkflow: Run summarization
    IssueWorkflow->>AI: Generate poem for issue
    AI-->>IssueWorkflow: Return poem
    IssueWorkflow->>GitHub: Post poem comment
    
    User->>GitHub: Opens/Edits PR
    GitHub->>PRWorkflow: Trigger workflow
    PRWorkflow->>GitHub: Add rocket reaction
    PRWorkflow->>AI: Generate poem for PR
    AI-->>PRWorkflow: Return poem
    PRWorkflow->>GitHub: Post poem comment
```

### 4. Testing Considerations

**Manual Testing Steps:**
1. Create a test issue with various content types (bug report, feature request, question)
2. Verify poem is generated and posted as a comment
3. Check that poem is relevant to issue content
4. Create a test PR with different change types
5. Verify PR poem is generated and posted
6. Test with bot-created PRs to ensure they're skipped
7. Test error handling when AI inference fails

**Edge Cases to Handle:**
- Empty issue/PR bodies
- Very long issue/PR descriptions (truncation may be needed)
- Special characters in titles/bodies
- Bot-created issues/PRs (should skip)
- Rate limiting on AI inference API
- Network failures during AI generation

### 5. Configuration Options

**Model Selection:**
- Current: `gpt-4o-mini` (balanced quality and speed)
- Alternative: `mistral-ai/Ministral-3B` (faster, lower cost)
- Can be configured per workflow based on requirements

**Poem Style Customization:**
The AI prompt can be adjusted to change poem characteristics:
- Length: Currently 4-8 lines, can be modified
- Style: Currently playful/lighthearted, can be formal/technical
- Rhyme scheme: Currently flexible, can enforce specific patterns
- Emoji usage: Currently minimal (1-2), can be increased/removed

### 6. Integration Checklist

| Component | File | Action |
|-----------|------|--------|
| Issue Poem Generator | `file:.github/workflows/ulti.yaml` | Add new steps after line 736 |
| PR Poem Generator | `file:.github/workflows/pr-poem-generator.yml` | Create new file |
| Permissions | Both workflows | Verify `issues: write` and `pull-requests: write` |
| AI Model Access | Both workflows | Ensure `models: read` permission exists |
| Error Handling | Both workflows | Add fallback poems for AI failures |
| Bot Detection | Both workflows | Skip bot-created issues/PRs |

### 7. Deployment Notes

**Prerequisites:**
- GitHub Actions must have access to `actions/ai-inference@v1`
- Repository must have AI inference enabled
- Appropriate permissions must be granted to workflows

**Rollout Strategy:**
1. Deploy PR poem generator first (lower risk, isolated workflow)
2. Monitor for 1-2 days to ensure stability
3. Deploy issue poem generator to ulti.yaml
4. Monitor both workflows for performance and quality

**Monitoring:**
- Check workflow run logs for AI inference errors
- Review generated poems for quality and appropriateness
- Monitor API rate limits and costs
- Collect user feedback on poem feature

---

Execution Information

Branch: main
Commit: 8fef08b

---

💡 Tips

Supported Commands (Inside Comments)

• Use @traycerai generate to iterate on the previous version of the implementation plan.

Supported Commands (Inside Description)

• Add @traycerai ignore anywhere in the ticket description to prevent this ticket from being processed.
• Add @traycerai branch:<branch-name> anywhere in the ticket description to specify the target branch for the implementation plan.

Community

• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Hi @traycerai! Thanks for the suggestion! Adding a poem generator sounds like a fun and creative idea. However, it feels a bit outside the scope of this repository's focus on being a multi-language IDE and issue assistant. If you'd like, you could open a discussion in the Discussions tab to see what others in the community think about it. That might be a more suitable place for ideas like this. Here's the link: https://github.com/orgs/OmniBlocks/discussions

Let us know if you have any feature ideas more aligned with OmniBlocks' goals!

[ampelectrecuted]

/q dev

[amazon-q-developer]

Something went wrong and I was unable to complete the development request. This may be because of content guidelines that I cannot comply with.

[ampelectrecuted]

/q dev

[amazon-q-developer]

Something went wrong and I was unable to complete the development request. This may be because of content guidelines that I cannot comply with.

[ampelectrecuted]

/q why do you hate having fun >:(

[ampelectrecuted]

@coderabbitai isn't amazon q being a bit too... corporate and boring

[ampelectrecuted]

@OmniBlocks/ai hi

[ampelectrecuted]

https://github.com/coderabbitai isn't amazon q being a bit too... corporate and boring, and you are being slow 🐇 =🐌