Retrieve the issue details at the start Always use first to get the full issue content Get additional context and requirements Always use after get_issue to see full discussion Find recent changes to affected files Use during codebase exploration Find code patterns on GitHub Use to supplement local codebase_search Add progress updates or ask questions Use if clarification needed or to show progress Find related or similar PRs Use to understand similar changes Get details of related PRs Use when issue references specific PRs Create a pull request to RooCodeInc/Roo-Code Use in step 10 after user approval - Always target RooCodeInc/Roo-Code repository - Use "main" as the base branch unless specified otherwise - Include issue number in PR title - Set maintainer_can_modify to true github create_pull_request { "owner": "RooCodeInc", "repo": "Roo-Code", "title": "fix: Resolve dark theme button visibility (#123)", "head": "username:fix/issue-123-dark-theme-button", "base": "main", "body": "## Description\n\nFixes #123\n\n[Full PR description]", "draft": false, "maintainer_can_modify": true } Fork the repository if user doesn't have push access Use if user needs to work from a fork github fork_repository { "owner": "RooCodeInc", "repo": "Roo-Code" }