GitHub Conversation

Use this skill when

1. You need to read a PR/issue before replying.
2. You need to reply to comments or review threads.
3. You need to submit a review.
4. You need to post a status update that closes loops.

Tool split

1. Use gh-llm for reading context (timeline, collapsed items, review threads, checks).
2. Use gh for simple write actions (comment, labels, assignees, reviewers, close/reopen, merge).
3. If context is incomplete, do not reply yet; expand first.

Install gh-llm

Prerequisites:

1. gh is installed and authenticated (gh auth status).
2. Python 3.14+ is available if installing via uv.

Install option A (recommended for CLI tool use):

uv tool install gh-llm
gh-llm --version

Install option B (GitHub CLI extension):

gh extension install ShigureLab/gh-llm
gh llm --version

Command prefix mapping:

1. If installed via uv tool, use gh-llm ....
2. If installed as gh extension, use gh llm ....

Fast start

Read a PR

gh-llm pr view <pr> --repo <owner/repo>
gh-llm pr timeline-expand <page> --pr <pr> --repo <owner/repo>
gh-llm pr review-expand <PRR_id[,PRR_id...]> --pr <pr> --repo <owner/repo>
gh-llm pr checks --pr <pr> --repo <owner/repo>

Read an issue

gh-llm issue view <issue> --repo <owner/repo>
gh-llm issue timeline-expand <page> --issue <issue> --repo <owner/repo>

Write simple updates

gh pr comment <pr> --repo <owner/repo> --body '<comment>'
gh issue comment <issue> --repo <owner/repo> --body '<comment>'
gh pr edit <pr> --repo <owner/repo> --add-label '<label1>,<label2>'
gh pr edit <pr> --repo <owner/repo> --remove-label '<label1>,<label2>'
gh pr edit <pr> --repo <owner/repo> --add-reviewer '<reviewer1>,<reviewer2>'
gh pr edit <pr> --repo <owner/repo> --add-assignee '<assignee1>,<assignee2>'

Reading workflow (required before replying)

1) Build context map

Identify:

1. Current goal of this PR/issue.
2. Open requests not yet addressed.
3. Decisions already made.
4. Linked PRs/issues that affect this thread.

2) Expand hidden context

Expand collapsed timeline pages and relevant review threads before replying.

3) Check delivery state

For PRs, check:

1. CI/check failures.
2. Mergeability/conflicts.
3. Unresolved review threads.

Reply workflow

1) Reply to one thread with one intent

A single reply should answer the target point only. Do not mix unrelated updates.

2) Be verifiable

When making technical claims, include at least one concrete reference:

1. path:line
2. commit hash
3. check/log link
4. reproduction command

3) Quote only when needed

Use > when:

1. the original comment has multiple points
2. the thread is long and reference is ambiguous
3. you are answering a specific sentence fragment

For short one-to-one replies, no quote is needed.

4) State status clearly

Use plain status language:

1. fixed
2. partially fixed
3. not fixed yet
4. intentionally unchanged

If partially fixed or unchanged, include reason and next step.

Review workflow

As reviewer

1. Separate blocking vs non-blocking points.
2. Give actionable suggestions.
3. Point to exact location when possible.
4. Avoid generic criticism without concrete evidence.

As PR author

1. Expand and read all relevant review content.
2. Address items one by one.
3. Reply to each addressed thread.
4. Resolve a thread only after fix/decision is actually complete.
5. Post one concise round-up after a batch of fixes.

Issue workflow

Opening an issue

Include:

1. Problem statement.
2. Minimal reproduction.
3. Expected vs actual behavior.
4. Environment details.
5. Logs/traceback/screenshots.
6. Related links.

Maintaining a busy issue

1. Ask for missing repro info instead of guessing.
2. Link duplicates to the canonical thread.
3. Keep one canonical status update comment.

Quality gates before posting

1. Is context complete (including expanded hidden/collapsed content)?
2. Does the message move the thread forward?
3. Are key claims backed by verifiable evidence?
4. Does tone and granularity match this repository?

Co-author and credit

When a reviewer’s concrete code change is substantially adopted, add:

Co-authored-by: <Reviewer Name> <reviewer_email>

Use GitHub-linked email if attribution on GitHub is desired.