Make 'please summarize my work' prompt customizable for GitHub resolver

[jpelletier1]

What problem or use case are you trying to solve?
When using the GitHub resolver, sometimes the request I make to OpenHands doesn't require it to summarize it's work. For example, I created a custom microagent for doing a code review. The 'Please summarize my work' prompt that automatically gets added to every GitHub request diluted some of the code review feedback.

Describe the UX or technical implementation you have in mind
The prompt should be customizable. Some users may want it to be trigger based, or customized to incorporate additional instructions.

Additional context

If you find this feature request or enhancement useful, make sure to add a 👍 to the issue

[Abeansits]

Some more context, this is also the case if you ask it to generate documentation or diagrams. You would need access to the specific thread to get the full details. Even if you ask it to ignore the following summary command, it still doesn't work. :)

[jpelletier1]

For this ticket, I think we ideally want to make the summary_prompt customizable. For the code review use case, I've experimented with this summary_prompt and it seems to work well for re-stating the answer to the original code review prompt. The addition of word for word seems to do the trick.

Please send a final message summarizing your work according to this logic:

IF: you simply answered a question, this final message should simply re-state, word for word, the answer to the question.

ELSE: If you made changes, please first double-check the git diff, think carefully about the user's request(s), and check:
- whether the request has been completely addressed and all of the instructions have been followed faithfully (in checklist format if appropriate).
- whether the changes are concise (if there are any extraneous changes not important to addressing the user's request they should be reverted). If the request has been addressed and the changes are concise, then push your changes to the remote branch and send a final message summarizing the changes.```

[malhotra5]

I think we have taken one step towards this direction by allowing for more customizable system prompts #9265. So we could swap out the system instructions to focus specifically on code review or other specialized workflows in general (for example automatically filing bugs as github issues with slack integration, etc)

Ideally we figured out what we should allow users to modify and when/where the modifications should be applied

[jpelletier1]

@malhotra5 @xingyaoww For this specific use case where the customer wants to customize the resolver prompt, how would they do this given #9265 is merged? Or is there more work we'd need to do to OpenHands to make this a bit more customizable?