Agent skill

github-pr-unresolved-review-fetcher

Fetch unresolved PR review comments from GitHub. Use when working with pull request reviews, addressing review feedback, or checking outstanding review comments on a PR. Triggers on requests like "get PR reviews", "fetch review comments", "show unresolved comments", or "what feedback is pending on this PR".

Stars 3
Forks 0

Install this agent skill to your Project

npx add-skill https://github.com/yaakaito/env/tree/main/dotfiles/.claude/skills/github-pr-unresolved-review-fetcher

SKILL.md

PR Review Fetcher

Fetch unresolved review comments from GitHub pull requests using GraphQL API.

Usage

Run the script with owner, repo, and PR number:

bash
bash scripts/fetch_unresolved_reviews.sh <owner> <repo> <pr_number>

Example:

bash
bash scripts/fetch_unresolved_reviews.sh yaakaito aiblio 123

Auto-detect from Current Branch

When working in a git repository with an open PR:

bash
# Get current repo info
REPO_INFO=$(gh repo view --json owner,name -q '"\(.owner.login) \(.name)"')
OWNER=$(echo $REPO_INFO | cut -d' ' -f1)
REPO=$(echo $REPO_INFO | cut -d' ' -f2)

# Get PR number for current branch
PR_NUMBER=$(gh pr view --json number -q '.number')

# Fetch reviews
bash scripts/fetch_unresolved_reviews.sh "$OWNER" "$REPO" "$PR_NUMBER"

Output Format

Returns XML-formatted review comments:

xml
<review-comment>
  <file>src/example.ts</file>
  <line>42</line>
  <author>reviewer</author>
  <body>Consider using a more descriptive variable name here.</body>
</review-comment>

Requirements

  • gh CLI authenticated with GitHub
  • jq for JSON processing

Expand your agent's capabilities with these related and highly-rated skills.

yaakaito/env

spec-file-manager

Manage specification files. Use when creating, reading, updating, or listing spec files. Triggers on requests like "create spec", "update spec", "list specs", or "show spec status".

3 0
Explore
yaakaito/env

adr-writer

Skill for creating and editing Architecture Decision Records (ADRs). Use when requests involve "create ADR", "record architecture decision", or "document design decisions". Supports creating new ADRs, updating existing ADRs, and reviewing ADR format.

3 0
Explore
yaakaito/env

github-workflow

Write and edit GitHub Actions workflow files. Use when creating new workflows, editing existing .github/workflows/*.yml files, or setting up CI/CD pipelines. Triggers on requests like "create a workflow", "add GitHub Actions", "set up CI", or "edit the workflow file".

3 0
Explore
yaakaito/env

github-workflow-fixer

Analyze and fix GitHub Actions workflow failures. Use when workflows fail, CI/CD issues occur, or when debugging GitHub Actions runs. Triggers on requests like "fix workflow", "why did the build fail", "check CI status", "debug GitHub Actions", or "workflow failed".

3 0
Explore
yaakaito/env

codex-review

Codex CLI を使って現在のコード変更を5つの観点(セキュリティ・パフォーマンス・バグ・テスト・アーキテクチャ)から並列レビューし、指摘に基づいてコードを修正するスキル。ユーザーが「codex でレビュー」「codex review」「コードレビューして」「レビュー実行」「codex にレビューさせて」「変更をチェック」などと言った場合や、コード品質チェック・多角的なレビューを求められた場合に使用する。明示的に codex に言及していなくても、包括的なコードレビューを求められたらこのスキルの使用を検討すること。

3 0
Explore
yaakaito/env

research

Research a topic using WebSearch based on the current context. Use when the user needs best practices, external guidance, or wants to investigate approaches. Triggers on "research", "search best practices", "find examples".

3 0
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results