Reply Comments

Safely publish prepared PR-feedback outcomes through separately confirmed push, reply, and inline-thread resolution gates. Re-fetches normalized identities before every mutation and keeps retries idempotent.

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add flurdy/agent-skills --skill reply-comments
Manual install
git clone --depth 1 https://github.com/flurdy/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/reply-comments ~/.claude/skills/reply-comments

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Reply to Review Comments

Publish selected, validated feedback outcomes after `/review-comments`. Push, reply posting, and
thread resolution are three separate visible actions, each requiring fresh current-run
confirmation. Never infer remote permission from item selection, validation, a local commit, a
previous run, or approval of another action.

## Usage

```text
/reply-comments                         # PR for the current branch; select eligible items
/reply-comments 123                     # backward-compatible current-repository selector
/reply-comments owner/repo#123          # repository-qualified selector
/reply-comments owner/repo#123 inline:C1 conversation:I2
```

Arguments identify candidates only. They are not permission to push, post, or resolve.

## Instructions

### 1. Resolve the PR and Checkout

Accept `owner/repo#number` or a numeric PR. With no selector, resolve the current branch through:

```bash
~/.agents/skills/reply-comments/scripts/gh-pr-current-info.sh
```

Use the selected owner/repository for every GitHub call. Before offering a push, prove the current
checkout's `origin`, branch, and HEAD correspond to that PR. Do not switch, fetch, reset, clean,
merge, rebase, or overwrite work. A repository mismatch disables the push gate but does not prevent
a separately validated answer/rationale from being prepared.

### 2. Restore Bounded Handled State

Carry forward `/review-comments` state when it exists. Otherwise reconstruct validation and prepared
Read the full skill on GitHub

Details

Skill name
reply-comments
Path
skills/reply-comments/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Reply Comments skill do?

Safely publish prepared PR-feedback outcomes through separately confirmed push, reply, and inline-thread resolution gates. Re-fetches normalized identities before every mutation and keeps retries idempotent.

How do I install the Reply Comments skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add flurdy/agent-skills --skill reply-comments. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Reply Comments popular?

It lives in flurdy/agent-skills, which has 9 GitHub stars and 0 forks.

Related skills

Architect

9

flurdy/agent-skills

Architecture and implementation planning gate for complex or high-blast-radius work. Produces evidence-backed decisions, reviewable slices, acceptance evidence, and conditional human review ownership without editing code.

Software Development

Artifact Hygiene

9

flurdy/agent-skills

Run a local-only, read-only advisory audit of publishable working-tree files and unpublished branch history with redaction-safe findings.

Git & Code Review

Backlog Groom

9

flurdy/agent-skills

Auto-detects workspace unfinished backlogs across unique stores; otherwise local open beads. Flags thin prose, missing labels, drift, lifecycle and duplicates. Report-only; mutations need approval, destructive ones individually.

Other

Review Comments

9

flurdy/agent-skills

Address PR review feedback through explicit item selection, independent validation, focused local fixes, verification, and a local commit. Never publishes remote actions; use reply-comments for separately confirmed push, reply, and resolution gates.

Git & Code Review

Rebase

9

flurdy/agent-skills

Rebase feature or stacked branches, or explicitly integrate a fetched upstream into local main/master. Separate trunk mode proves local replay scope and never enters force-push or PR flows; its mutations require fresh confirmation.

Git & Code Review

Review PR

9

flurdy/agent-skills

Review a repository-qualified pull request at an immutable head, compare it with Jira requirements, and return a read-only verdict with explicit evidence completeness.

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.