Skip to content

Update implement prompt to update PR #203

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MariusStorhaug merged 7 commits into from
Oct 2, 2025
Merged

Update implement prompt to update PR #203

Changes from 6 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
76532bf
docs: Add implementation plan for unified CI/CD workflow
MariusStorhaug Oct 2, 2025
45115ca
feat(workflow)!: unified CI/CD workflow configuration
MariusStorhaug Oct 2, 2025
95784c6
enhance: clarify task completion and PR description update process
MariusStorhaug Oct 2, 2025
4567217
Delete obsolete research, specification, tasks, and test plan documen…
MariusStorhaug Oct 2, 2025
81efd45
chore: remove obsolete integration tests for unified workflow
MariusStorhaug Oct 2, 2025
b65fd9a
feat: consolidate CI/CD workflows into a single configuration file an…
MariusStorhaug Oct 2, 2025
91de5d9
chore: streamline implementation prompt by removing redundant steps a…
MariusStorhaug Oct 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 11 additions & 3 deletions .github/prompts/implement.prompt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,13 @@ $ARGUMENTS
- For parallel tasks [P], continue with successful tasks and report failed ones
- Provide clear error messages with context for debugging
- Suggest next steps if implementation cannot proceed
- **IMPORTANT**: For completed tasks, make sure to mark the task as [X] in the tasks file.
- **CRITICAL - Update task status immediately after completion**:
* After completing each task, mark it as [X] in tasks.md
* Update the PR description to mark the corresponding task checkbox from `- [ ] T###:` to `- [X] T###:`
* This MUST be done task-by-task as you progress, not at the end
* If GitHub tools are available, use them to update the PR description
* If not available, use: `gh pr edit <PR-number> --body "<updated-description>"`
* Ensure task progress is visible in real-time to users watching the PR

8. Completion validation:
- Verify all required tasks are completed
Expand Down Expand Up @@ -152,7 +158,9 @@ $ARGUMENTS
| Breaking change | 🌟 | Major |

- Fallback PR title format (if issue title unavailable): `<Icon> [Type of change]: <Short description>`
- **Write PR description as a release note**:
- **REPLACE the entire PR description with release notes**:
* **IMPORTANT**: Clear the existing PR description completely (including task list) and replace it with the release notes
* This ensures the PR description is ready to be used as GitHub Release notes when merged to main
* **Opening summary** (1-2 paragraphs):
- Start with what was accomplished in user-focused language
- Write in past tense: "Added...", "Improved...", "Fixed..."
Expand Down Expand Up @@ -186,7 +194,7 @@ $ARGUMENTS

**GitHub Integration**: If GitHub tools or integrations are available (such as GitHub MCP Server or other GitHub integrations), use them to update the PR description in the target repository. If not available, provide this fallback command:
```bash
# Update PR description
# Replace PR description with release notes
# If fork: gh pr edit <PR-number> --repo <upstream_owner>/<upstream_repo> --body "<release-note-description>"
# If local: gh pr edit <PR-number> --body "<release-note-description>"
gh pr edit <PR-number> --body "<release-note-description>"
Expand Down
Loading