Skip to content

Conversation

@ajrobertsonio
Copy link

Summary

  • Replace references to bin/get-pr-comments and bin/resolve-pr-thread with standard gh CLI commands
  • These scripts were never created and don't exist in the plugin or user projects
  • Commands now work in any repository without custom scripts

Test plan

  • Run /resolve_pr_parallel on a PR and verify it fetches comments without errors
  • Verify the command uses gh api and gh pr view instead of missing scripts

Fixes #147

🤖 Generated with Claude Code

Replace references to bin/get-pr-comments and bin/resolve-pr-thread
with standard gh CLI commands that work in any repository.

Fixes EveryInc#147

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@kieranklaassen kieranklaassen added the bug Something isn't working label Feb 8, 2026
@kieranklaassen
Copy link
Collaborator

Thanks for catching this! You were right that those bin/ scripts were missing from the plugin.

I've fixed this by converting resolve_pr_parallel from a command to a proper skill with the scripts bundled:

  • skills/resolve-pr-parallel/scripts/get-pr-comments — GraphQL query for unresolved threads (now auto-detects owner/repo instead of hardcoding)
  • skills/resolve-pr-parallel/scripts/resolve-pr-thread — GraphQL mutation to resolve threads

This keeps the GraphQL power (filtering unresolved/non-outdated threads, programmatic resolve) while making it portable across repos.

Closing this since the fix is included directly — thanks again for flagging it! 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[compound-engineering] Bug: resolve_pr_parallel command references non-existent scripts

2 participants