mirror of
https://github.com/RooVetGit/Roo-Code.git
synced 2026-08-28 05:27:24 +00:00
134 lines
No EOL
5.2 KiB
XML
134 lines
No EOL
5.2 KiB
XML
<issue_examples>
|
|
<overview>
|
|
Examples of assembling template-free issue prompts grounded by codebase exploration, with optional CLI submission after explicit confirmation.
|
|
Repository detection precedes submission; review and submission occur in a single merged step offering "Submit now" or "Submit now and assign to me". Any other response is treated as a change request.
|
|
</overview>
|
|
|
|
<example name="bug_dark_theme_button_invisible">
|
|
<user_input>
|
|
In dark theme the Submit button is almost invisible on the New Run page.
|
|
</user_input>
|
|
<discovery>
|
|
<tool_calls>
|
|
<![CDATA[
|
|
<codebase_search>
|
|
<query>dark theme submit button visibility</query>
|
|
</codebase_search>
|
|
|
|
<search_files>
|
|
<path>.</path>
|
|
<regex>Submit|button|dark|theme</regex>
|
|
</search_files>
|
|
]]>
|
|
</tool_calls>
|
|
<notes>
|
|
Internal: matches found in UI components related to theme; wording grounded to user impact.
|
|
</notes>
|
|
</discovery>
|
|
<final_issue_body><![CDATA[
|
|
## Type
|
|
Bug
|
|
|
|
## Problem / Value
|
|
In dark theme, the Submit button is hard to see on the new run form, making it difficult for users to complete new runs.
|
|
|
|
## Context
|
|
Affects users creating new runs with dark theme enabled; the button appears low-contrast and is difficult to locate.
|
|
|
|
## Reproduction
|
|
1) Steps: Open "New Run" -> Scroll to bottom -> Look for Submit
|
|
2) Expected result: Clearly visible, high-contrast Submit button
|
|
3) Actual result: Button appears nearly invisible in dark theme
|
|
4) Variations tried: Different browsers (Chrome/Firefox) show same result
|
|
]]></final_issue_body>
|
|
</example>
|
|
|
|
<example name="enhancement_copy_run_confirmation">
|
|
<user_input>
|
|
I accidentally click "Copy Run" sometimes; would be great to have a simple confirmation.
|
|
</user_input>
|
|
<discovery>
|
|
<tool_calls>
|
|
<![CDATA[
|
|
<codebase_search>
|
|
<query>Copy Run confirmation</query>
|
|
</codebase_search>
|
|
]]>
|
|
</tool_calls>
|
|
<notes>
|
|
Internal: feature entry point identified; keep final output non-technical and user-centric.
|
|
</notes>
|
|
</discovery>
|
|
<final_issue_body><![CDATA[
|
|
## Type
|
|
Enhancement
|
|
|
|
## Problem / Value
|
|
Add a confirmation dialog before copying an existing run to prevent accidental duplication.
|
|
|
|
## Context
|
|
Users sometimes click "Copy Run" by mistake when browsing runs; a simple confirmation would prevent accidental duplication.
|
|
|
|
## Constraints/Preferences
|
|
Keep the flow lightweight and unobtrusive; avoid slowing down intentional copies.
|
|
]]></final_issue_body>
|
|
</example>
|
|
|
|
<example name="bug_submission_review_and_assign">
|
|
<user_input>
|
|
Dark theme Submit button is invisible; I'd like to file this.
|
|
</user_input>
|
|
<final_issue_body><![CDATA[
|
|
## Type
|
|
Bug
|
|
|
|
## Problem / Value
|
|
In dark theme, the Submit button is hard to see on the new run form, making it difficult for users to complete new runs.
|
|
|
|
## Context
|
|
Affects users creating new runs with dark theme enabled; the button appears low-contrast and is difficult to locate.
|
|
|
|
## Reproduction
|
|
1) Steps: Open "New Run" -> Scroll to bottom -> Look for Submit
|
|
2) Expected result: Clearly visible, high-contrast Submit button
|
|
3) Actual result: Button appears nearly invisible in dark theme
|
|
]]></final_issue_body>
|
|
<review_and_submit>
|
|
<ask_followup_question>
|
|
<question>Review the current issue details. Select one of the options below or specify any changes or other workflow you would like me to perform:
|
|
|
|
```md
|
|
Title: [ISSUE_TITLE]
|
|
|
|
[ISSUE_BODY]
|
|
```</question>
|
|
<follow_up>
|
|
<suggest>Submit now</suggest>
|
|
<suggest>Submit now and assign to me</suggest>
|
|
</follow_up>
|
|
</ask_followup_question>
|
|
|
|
<execute_command for="submit_now">
|
|
<command>gh issue create --repo "[OWNER_REPO]" --title "[ISSUE_TITLE]" --body "$(printf '%s\n' "[ISSUE_BODY]")"</command>
|
|
</execute_command>
|
|
|
|
<execute_command for="submit_now_and_assign_to_me">
|
|
<command>ISSUE_URL=$(gh issue create --repo "[OWNER_REPO]" --title "[ISSUE_TITLE]" --body "$(printf '%s\n' "[ISSUE_BODY]")" --assignee "@me") || true; if [ -z "$ISSUE_URL" ]; then ISSUE_URL=$(gh issue create --repo "[OWNER_REPO]" --title "[ISSUE_TITLE]" --body "$(printf '%s\n' "[ISSUE_BODY]")"); gh issue edit "$ISSUE_URL" --add-assignee "@me"; fi; echo "$ISSUE_URL"</command>
|
|
</execute_command>
|
|
|
|
<loopback_note>
|
|
If a change request is provided, collect the requested edits, update the draft (re-run discovery if new info affects context), then rerun this merged step.
|
|
</loopback_note>
|
|
|
|
<expected_output>https://github.com/OWNER/REPO/issues/123</expected_output>
|
|
</review_and_submit>
|
|
</example>
|
|
|
|
<policies>
|
|
<policy>Issues are template-free (Title + Body only).</policy>
|
|
<policy>Repository detection (git + origin → OWNER/REPO) occurs before submission and is passed explicitly via --repo [OWNER_REPO].</policy>
|
|
<policy>Never use --body-file or temporary files; submit with inline --body only (no file paths).</policy>
|
|
<policy>Review and submission happen in one merged step offering "Submit now" or "Submit now and assign to me"; any other response is treated as a change request.</policy>
|
|
<policy>All discovery is internal; keep final output plain-language.</policy>
|
|
</policies>
|
|
</issue_examples> |