Menu
Post a reply comment on a GitHub issue in English with a natural, concise writing style, based on the intent passed as arguments
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Approve a pull request using gh pr review --approve
Batch-triage open pull requests: list PRs with prs-awaiting-maintainer, review each with review-pr, then post-review-comments when there are merge-blocker findings, or create-scrap-issue for non-blocking findings and merge-pr when there are none. Use when the user wants to review and resolve a batch of PRs in one pass.
Clean up unnecessary local branches and prune stale remote-tracking branches
Clean git worktrees created by git-worktree-runner
Commit current changes, push to remote, and create or update a pull request. Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.
Analyze the differences between the current branch and origin/main, and summarize the current work progress
| name | post-issue-comment |
| description | Post a reply comment on a GitHub issue in English with a natural, concise writing style, based on the intent passed as arguments |
arguments = $ARGUMENTS
Parse arguments as:
target_issue: the issue number (or URL) to reply tointent: the gist of the reply the user wants to post (what to say, the stance to take, the points to cover)If target_issue is not provided, ask the user which issue to comment on.
If intent is not provided, ask the user what the reply should convey.
Run the following in parallel:
gh issue view <issue_number>gh issue view <issue_number> --commentsIf the issue references related pull requests, commits, or files that are needed to craft an informed reply, gather that context as well.
Based on the issue content and the user's intent, draft a reply comment.
intent faithfully; do not add positions the user did not ask for.Post the drafted reply using:
gh issue comment <issue_number> --body "<reply body>"
Write in English only.
Style guidelines โ write like a human teammate, not a bot:
##), horizontal rules (---), and excessive bullet lists.Output the issue number and a brief summary of the comment that was posted.