reply-comments skillA
reply-comments is agent-read markdown (skill) from flurdy/agent-skills: 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..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# 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, …
Read the whole file at its exact version.
How to install
mdr add flurdy/agent-skills/reply-comments@v1.2.1mdr add flurdy/agent-skills/reply-comments@sha256:a510a3d988883a6fPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_gvlg7347loxrjieq)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.2.1 latest | 2026-08-29 | e37f4db | 9,452 B | A | view · diff |
| v1.2.0 | 2026-07-31 | 9c7633c | 9,317 B | A | view · diff |
| v1.1.0 | 2026-07-30 | e85d284 | 5,488 B | A | view · diff |
| v1.0.0 | 2026-07-20 | bfcc6f6 | 4,640 B | A | view · diff |
| v1.0.0 | 2026-07-18 | 38882a2 | 4,640 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9452 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
flurdy/agent-skills · 9 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gvlg7347loxrjieq GET https://markdownregistry.com/api/v1/resolve?ref=flurdy/agent-skills/reply-comments GET https://markdownregistry.com/api/v1/blob/a510a3d988883a6f6cecb3c0a889a27377595a46f06c0e4d097de9ef79ce65de
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.