Some checks are pending
Go Benchmark / Performance Regression Check (push) Waiting to run
Cerberus Integration / Cerberus Security Stack Integration (push) Waiting to run
Upload Coverage to Codecov / Backend Codecov Upload (push) Waiting to run
Upload Coverage to Codecov / Frontend Codecov Upload (push) Waiting to run
CodeQL - Analyze / CodeQL analysis (go) (push) Waiting to run
CodeQL - Analyze / CodeQL analysis (javascript-typescript) (push) Waiting to run
CrowdSec Integration / CrowdSec Bouncer Integration (push) Waiting to run
Docker Build, Publish & Test / build-and-push (push) Waiting to run
Docker Build, Publish & Test / Security Scan PR Image (push) Blocked by required conditions
Quality Checks / Auth Route Protection Contract (push) Waiting to run
Quality Checks / Codecov Trigger/Comment Parity Guard (push) Waiting to run
Quality Checks / Backend (Go) (push) Waiting to run
Quality Checks / Frontend (React) (push) Waiting to run
Rate Limit integration / Rate Limiting Integration (push) Waiting to run
Security Scan (PR) / Trivy Binary Scan (push) Waiting to run
Supply Chain Verification (PR) / Verify Supply Chain (push) Waiting to run
WAF integration / Coraza WAF Integration (push) Waiting to run
29 lines
994 B
Markdown
Executable File
29 lines
994 B
Markdown
Executable File
---
|
|
mode: 'agent'
|
|
description: 'Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.'
|
|
tools: ['search/codebase', 'search', 'github', 'create_issue', 'search_issues', 'update_issue']
|
|
---
|
|
# Create GitHub Issue from Implementation Plan
|
|
|
|
Create GitHub Issues for the implementation plan at `${file}`.
|
|
|
|
## Process
|
|
|
|
1. Analyze plan file to identify phases
|
|
2. Check existing issues using `search_issues`
|
|
3. Create new issue per phase using `create_issue` or update existing with `update_issue`
|
|
4. Use `feature_request.yml` or `chore_request.yml` templates (fallback to default)
|
|
|
|
## Requirements
|
|
|
|
- One issue per implementation phase
|
|
- Clear, structured titles and descriptions
|
|
- Include only changes required by the plan
|
|
- Verify against existing issues before creation
|
|
|
|
## Issue Content
|
|
|
|
- Title: Phase name from implementation plan
|
|
- Description: Phase details, requirements, and context
|
|
- Labels: Appropriate for issue type (feature/chore)
|