[TASK] Phase 1: Core Infrastructure - Auto-Remediation Workflow
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
Implement the core infrastructure for automated CI/CD failure detection and remediation:
- Create main GitHub Actions workflow (cicd_auto-remediation.yml)
- Integrate Claude Code CLI with cicd-diagnostics skill
- Set up diagnostic cache management
- Configure workflow to trigger on merge queue failures
This is Phase 1 of the Auto-Remediation EPIC (#34656).
Acceptance Criteria
- created with all jobs (detect-failure, diagnose, issue-management, notify)
- Claude Code CLI properly invoked with cicd-diagnostics skill
- Diagnostic cache (GitHub Actions Cache) configured for state management
- Workflow triggers on merge queue completion events
- ANTHROPIC_API_KEY secret configured in repository
- Repository variables set (AUTO_REMEDIATION_ENABLED, AUTO_REMEDIATION_WORKFLOWS, AUTO_CREATE_ISSUES)
- Test run completes successfully with mock failure
- Diagnostic outputs both diagnosis.json and DIAGNOSIS.md
Priority
High
Additional Context
Files to Create:
Dependencies: Requires ANTHROPIC_API_KEY secret to be configured
Related: Parent EPIC #34656
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with parent EPIC #34656 and map the requirements to the planned cicd_auto-remediation.yml workflow, including detect-failure, diagnose, issue-management, and notify. Verify how Claude Code CLI, the GitHub Actions diagnostic cache, merge queue completion events, repository settings, and mock failure testing should connect; done includes diagnosis.json and DIAGNOSIS.md from a successful test run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100