Skip to content
Skills Library
Documents & office · Writing

reply

/reply

Review p11 document comments and replies, then post useful replies to visible threads that ask questions, are unclear, are indecisive, or need input. Use when Codex should answer reviewers on a p11 document.

Repository
p11-public ↗
Licence
MIT
Last repository change
22.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 22.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Review p11 document comments and replies, then post useful replies to visible threads that ask questions, are unclear, are indecisive, or need input. Use when Codex should answer reviewers on a p11 document.

Original author description

Review p11 document comments and replies, then post useful replies to visible threads that ask questions, are unclear, are indecisive, or need input. Use when Codex should answer reviewers on a p11 document.

How it works

  1. Target Resolution
  2. CLI Resolution
  3. Review Comments
  4. Posting Replies
Original SKILL.md headings · 69 lines, 465 words
SKILL.md preview
---
name: reply
description: Review p11 document comments and replies, then post useful replies to visible threads that ask questions, are unclear, are indecisive, or need input. Use when Codex should answer reviewers on a p11 document.
metadata:
  short-description: Reply to unclear p11 review comments
---

# p11:reply

Use this skill to inspect p11 comments/replies and post replies where a response is useful.

## Target Resolution

Resolve the p11 document target in this order:

1. Use the p11 read URL, edit URL, read ID, or edit ID provided by the user.
2. If none is provided, use the most recent p11 document mentioned or created in the current chat conversation.
3. Only if the current chat has no usable p11 target, run `p11 history` and use the most recent relevant entry.

Do not use `p11 history` when the current chat already contains a usable p11 target.

## CLI Resolution

Prefer the global `p11` CLI. If missing, install `@p11-core/cli` globally. Use `npx -y @p11-core/cli@latest` only when global install is not possible. Never install p11 into the project.

Check availability with `command -v p11` and `p11 --help`.

Install or upgrade with `npm install -g @p11-core/cli@latest` when the command is missing or any `p11` command prints an update warning.

Use `--json` when structured comment fields are useful.

## Review Comments

Fetch all comments/replies:

```bash
p11 comments <target>
```

Use `--version <number>` only when the user asks for comments on a historical version.

Only consider comments/replies that are visible to reviewers. Do not reply to resolved or hidden comments; reviewers will not see those replies in the UI.

Review every visible thread before replying. Decide from the comment/reply content, not from an unresolved status field alone. Reply when a visible thread:

- asks a question
- requests clarification
- needs input or a decision
- is indecisive
- has conflicting replies
- is unclear to Codex
- needs a lightweight acknowledgement before the document can be revised

Do not equate an unresolved or visible status with needing a reply. If the thread already gives a clear action, such as "change this to...", "remove this...", "use this wording", or another settled decision, do not reply; those should be handled by `p11:revise`.

If no threads need replies, say that clearly and summarize any clear decisions that should be handled by `p11:revise`.

When discussing comments with the user, refer to quoted text or thread content instead of line numbers unless the user asks for line numbers.

## Posting Replies

Post replies with:

```bash
p11 reply <readUrl|readId> <commentId> --name "Codex" --body <text>
```

If the user provided only an edit URL or edit ID, use the current chat context, `p11 comments`, or `p11 history` to recover the matching read URL or read ID before replying.

Use `--body-file <file>` or `--body-file -` for multi-line replies. Use the reply name `Codex` for replies from Codex.

Keep replies concise and specific. If the comment is unclear, ask one direct clarifying question and name the decision needed to proceed.

After posting replies, ask the user to refresh the p11 page to see them.
Files in this package (2)
  • SKILL.md 3 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · rarexlabs/p11-public100MIT
lexfrei/ccc100BSD-3-Clause
rarexlabs/p11-public100MIT
hhiroshell/gh-devflow-plugins84MIT

Database snapshot: 13.11.2026 · package version d85c366b12a5 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100th-reply
    Reply to comments under your Korean Threads posts so the conversation continues. Use when the user pastes replies/comments from Threads (or Instagram) and wants short human replies in Korean, or asks what to answer. Writes 1-2 line replies that pick up the commenter's own words,…
  • 100answer-pr-reviews
    Use when the user asks to answer, address, or reply to review comments on one or more GitHub pull requests — "answer the review on #12", "address the comments on my PRs", "reply to the review findings" — in Claude Code, Codex, or any other agent. Not for reviewing a pull…
  • 100acm-review
    Review a prose document in ACM (Agent CriticMarkup) — read the live .md, leave inline comments and threaded replies, and propose edits, all via CriticMarkup. Use when asked to review, comment on, reply in, or suggest edits to a document a human is editing in ACM.
  • 100revise
    Revise the most recent or provided p11 shareable document based on comments/replies and publish a new version. Use when Codex should apply clear reviewer decisions to a p11 document.
  • 100review-reply
    Help the author answer review comments on their open pull request in their own voice. Fetches unresolved review threads, groups them, works out what each reviewer is asking for, makes or proposes the code changes, and drafts short reply notes for the author to rewrite and post…
  • 90respond-to-review
    Work through the review comments on the user's own Bitbucket or GitHub pull request using the OmniDev tools - fix what needs fixing, draft replies, and resolve threads once the user approves. Use when the user asks to address review comments, reply to reviewers, or clear open…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.