Skip to content

Conversation

@david-fraley
Copy link
Collaborator

Summary

Refactors the classify-issue-severity.yml workflow to use the create-task-action pattern instead of the previous claude-code-action with complex JSON parsing.

Changes

  • Simplified architecture: Reduced from 2 jobs to 1 job
  • Uses create-task-action: Follows the same pattern as doc-check.yaml
  • Removed JSON parsing complexity: No more structured output extraction, validation, or parsing steps
  • Added workflow_dispatch: Can now be manually triggered with an issue URL
  • Task handles commenting: The Coder Task uses GitHub MCP tools to fetch issue details and post comments directly

What's preserved

  • Triggered by the 'triage-check' label on issues
  • Same severity level definitions (s0-s4)
  • Same analysis framework with 5 key questions
  • Same fail-safe for insufficient information
  • Comments are still posted to the issue with the same format

Testing

  • YAML syntax validated
  • Manual test with an issue (can use workflow_dispatch)

Diff stats

  • 194 insertions, 245 deletions (net -51 lines)

🤖 Generated with Claude Code

This simplifies the workflow by using the create-task-action pattern instead of the previous claude-code-action with JSON parsing.

Key changes:
- Uses create-task-action to create a Coder Task for severity classification
- Removes complex JSON output parsing and validation steps
- Simplifies from 2 jobs to 1 job
- Adds workflow_dispatch trigger for manual execution
- Task automatically posts comments using GitHub MCP tools

The same severity classification logic and prompts are preserved, but now executed through a Coder Task which provides better reliability and follows the established pattern from doc-check.yaml.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@david-fraley david-fraley changed the title Refactor classify-issue-severity workflow to use create-task-action chore: refactor classify-issue-severity workflow to use create-task-action Dec 11, 2025
@david-fraley david-fraley merged commit 36289d8 into main Dec 11, 2025
32 checks passed
@david-fraley david-fraley deleted the refactor/classify-severity-use-create-task-action branch December 11, 2025 23:19
@github-actions github-actions bot locked and limited conversation to collaborators Dec 11, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants