[jsweep] Clean close_entity_helpers.cjs

[github-actions]

Summary

Cleaned and modernized close_entity_helpers.cjs to use modern JavaScript patterns while maintaining all functionality.

Changes Made

Modernized Loops:

• Replaced for (let i = 0; i < items.length; i++) with items.forEach() in generateCloseEntityStagedPreview
• Replaced traditional for loop with for...of and Array.entries() in processCloseEntityItems

Improved Readability:

• Used destructuring in resolveEntityNumber to extract config properties once at the top
• Simplified parseEntityConfig by removing intermediate variables for env var names
• Extracted owner and repo from context.repo once in processCloseEntityItems

Code Reduction:

• Removed unnecessary comments that described obvious code behavior
• Reduced from 356 lines to 312 lines (12% reduction)

Context

Execution Context: github-script (uses core, context, github globals)

Test Coverage

✅ All 40 existing tests pass - comprehensive test suite already exists covering:

• Label filtering logic
• Title prefix filtering
• Environment variable parsing
• Entity number resolution (multiple scenarios)
• Markdown title escaping
• Configuration constants

Validation Checks Completed

✅ Formatting: npm run format:cjs ✓
✅ Linting: npm run lint:cjs ✓
✅ Type checking: npm run typecheck ✓
✅ Tests: npm run test:js ✓ (40 tests passed)

Files Changed

• actions/setup/js/close_entity_helpers.cjs (356 → 312 lines, -44 lines)

---

Part of the jsweep unbloat automation initiative to create solid, simple, and lean CommonJS code.

AI generated by jsweep - JavaScript Unbloater

• expires on Feb 14, 2026, 7:39 AM UTC

[pelikhan]

/q modify agentic workflow to create issue and assign to agent

[github-actions]

🎩 Mission equipment ready! Q has optimized your workflow. Use wisely, 007! 🔫

[github-actions]

Q Mission Complete 🎯

I've successfully analyzed and optimized the agentic workflows to support creating issues and assigning them to agents.

What I Discovered

The create-issue safe-output already supports the assignees field for assigning issues to agents like Copilot! However, this capability wasn't well-documented or demonstrated.

What I Created

1. Demo Workflow (demo-create-issue-assign-agent.md)

• Comprehensive demonstration showing how to create issues with agent assignment
• Creates 3 example issues (bug triage, documentation, feature implementation)
• Automatically assigns all issues to @copilot
• Includes detailed explanation and best practices

2. Enhanced Issue-Arborist

• Updated issue-arborist.md to assign parent issues to @copilot
• Now when it creates parent issues for orphan clusters, they're automatically assigned for follow-up

How To Use This Feature

Add assignees to your create-issue configuration:

safe-outputs:
  create-issue:
    title-prefix: "[Auto] "
    labels: ["automation"]
    assignees: ["copilot"]  # ← Automatically assign to agent
    expires: 7d

Then your workflow can create issues and they'll be automatically assigned:

{
  "type": "create_issue",
  "title": "Investigate test failures",
  "body": "Several tests are failing. `@copilot` please investigate."
}

Powerful Use Cases

• Automated Triage: Create bug issues and assign to @copilot for investigation
• Documentation Tasks: Create doc update issues and assign to @copilot
• Feature Implementation: Create feature issues and assign for implementation
• Workflow Chaining: Created issues can trigger follow-up workflows
• Task Delegation: Autonomous agents can delegate work to other agents

Pull Request Created

I've created a pull request with:

• ✅ New demo workflow showing the feature
• ✅ Enhanced issue-arborist with agent assignment
• ✅ All workflows compile successfully
• ✅ Comprehensive documentation and examples

This demonstrates one of the most powerful capabilities: autonomous task delegation between agents! 🚀

AI generated by Q