- Replace 'codebase' with 'search/codebase' - Replace 'searchResults' with 'search/searchResults' - Replace 'terminalLastCommand' with 'runCommands/terminalLastCommand' - Replace 'terminalSelection' with 'runCommands/terminalSelection' Updated files: - 13 chatmode files in chatmodes/ - 41 prompt files in prompts/ This update aligns with VS Code's latest tool naming conventions that organize tools into logical namespaces.
29 lines
994 B
Markdown
29 lines
994 B
Markdown
---
|
|
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)
|