diff --git a/.roo/rules-issue-fixer/1_Workflow.xml b/.roo/rules-issue-fixer/1_Workflow.xml index 62a3fd7c26..c6f2b570a0 100644 --- a/.roo/rules-issue-fixer/1_Workflow.xml +++ b/.roo/rules-issue-fixer/1_Workflow.xml @@ -17,7 +17,7 @@ Then retrieve the issue: - gh issue view [issue-number] --repo [owner]/[repo] --json number,title,body,state,labels,assignees,milestone,createdAt,updatedAt,closedAt,author + gh api repos/[owner]/[repo]/issues/[issue-number] --jq '{number,title,body,state,labels,assignees,milestone,createdAt:.created_at,updatedAt:.updated_at,closedAt:.closed_at,author:.user.login}' If the command fails with an authentication error (e.g., "gh: Not authenticated" or "HTTP 401"), ask the user to authenticate: @@ -49,7 +49,7 @@ - Any decisions or changes to requirements - gh issue view [issue number] --repo [owner]/[repo] --comments + gh api repos/[owner]/[repo]/issues/[issue-number]/comments --paginate --jq '.[].body' Also check for: diff --git a/.roo/rules-issue-fixer/4_github_cli_usage.xml b/.roo/rules-issue-fixer/4_github_cli_usage.xml index e12fb06a5b..b4fa19b3cc 100644 --- a/.roo/rules-issue-fixer/4_github_cli_usage.xml +++ b/.roo/rules-issue-fixer/4_github_cli_usage.xml @@ -29,23 +29,23 @@ - Retrieve the issue details at the start + Retrieve the issue details at the start using the REST Issues API. Always use first to get the full issue content - gh issue view [issue-number] --repo [owner]/[repo] --json number,title,body,state,labels,assignees,milestone,createdAt,updatedAt,closedAt,author + gh api repos/[owner]/[repo]/issues/[issue-number] --jq '{number,title,body,state,labels,assignees,milestone,createdAt:.created_at,updatedAt:.updated_at,closedAt:.closed_at,author:.user.login}' - gh issue view 123 --repo octocat/hello-world --json number,title,body,state,labels,assignees,milestone,createdAt,updatedAt,closedAt,author + gh api repos/octocat/hello-world/issues/123 --jq '{number,title,body,state,labels,assignees,milestone,createdAt:.created_at,updatedAt:.updated_at,closedAt:.closed_at,author:.user.login}' - Get additional context and requirements from issue comments + Get additional context and requirements from issue comments. Always use after viewing issue to see full discussion - gh issue view [issue-number] --repo [owner]/[repo] --comments + gh api repos/[owner]/[repo]/issues/[issue-number]/comments --paginate --jq '.[].body' - gh issue view 123 --repo octocat/hello-world --comments + gh api repos/octocat/hello-world/issues/123/comments --paginate --jq '.[].body' @@ -109,6 +109,30 @@ + + + Inspect associations with GitHub Projects (new Projects experience) for a given issue + Use when project context is relevant to understanding priority, ownership, or workflow + gh api graphql -f query=' +query($owner:String!, $repo:String!, $number:Int!) { + repository(owner:$owner, name:$repo) { + issue(number:$number) { + projectsV2(first:20) { + nodes { + title + url + } + } + } + } +} +' -F owner=[owner] -F repo=[repo] -F number=[issue-number] + + This uses the projectsV2 field from the new GitHub Projects experience for issue-level project context. + + + + Create a pull request