Skip to content

Remove redundant prompt instruction in conversation history flow#149

Merged
DimaBir merged 2 commits into
dimabir/github_bot_respond_wikifrom
copilot/sub-pr-144-one-more-time
Feb 11, 2026
Merged

Remove redundant prompt instruction in conversation history flow#149
DimaBir merged 2 commits into
dimabir/github_bot_respond_wikifrom
copilot/sub-pr-144-one-more-time

Conversation

Copilot AI commented Feb 11, 2026

Copy link
Copy Markdown
Contributor

The AI prompt instructed "Respond to the user's latest message" while that message was already included in the conversation history, creating token waste and potential confusion.

Changes:

  • Updated prompt instruction from "Respond to the user's latest message" to "Continue the conversation based on the history above"

The conversation history builder (lines 139-169) already includes all messages in chronological order:

  1. Issue body with title
  2. All comments (user and bot) in sequence

The new instruction correctly references this complete history without implying the latest message is separate.

# Before
userPrompt += `--- YOUR TASK ---\n`;
userPrompt += `Respond to the user's latest message. `;

# After  
userPrompt += `--- YOUR TASK ---\n`;
userPrompt += `Continue the conversation based on the history above. `;

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Co-authored-by: DimaBir <28827735+DimaBir@users.noreply.github.com>
Copilot AI changed the title [WIP] Address feedback on issue assistant workflow updates Remove redundant prompt instruction in conversation history flow Feb 11, 2026
Copilot AI requested a review from DimaBir February 11, 2026 07:17
@DimaBir DimaBir marked this pull request as ready for review February 11, 2026 07:19
@DimaBir DimaBir merged commit 535ea4d into dimabir/github_bot_respond_wiki Feb 11, 2026
1 check passed
@DimaBir DimaBir deleted the copilot/sub-pr-144-one-more-time branch February 11, 2026 07:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants