菜单
Place PR/code-review comments as inline TODO markers in the file each comment is on, at its line, not in a centralized list. Use when asked to "write TODOs for PR comments", capture review feedback as TODOs, or turn review threads into actionable in-file notes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when drawing a diagram of an architecture change for review — a two-panel current-vs-planned (before/after) picture that lets a reviewer see what changed, what's removed, what's new, what held, and the one load-bearing why. Triggers: "arch diagram", "architecture diff", "before/after diagram", "diagram this refactor/migration/change", "visualize the change", "current vs planned", or any request to render an architectural change as a reviewable picture (HTML/SVG).
Use when asked to create a "local gitignore" or ignore files locally without committing the ignore rule. Create a `.gitignore.local` file at repo root and wire it via `git config core.excludesFile`, not `.git/info/exclude`.
This skill should be used when the user asks to "dedup the docs", "prune the corpus", "remove duplicate/redundant paragraphs", "reduce duplication across files", "these files repeat the same information", "consolidate repeated content", "the corpus duplicates topics", "map topics across files", or wants to find and remove duplicated prose across a set of text files (plain prose, markdown, SKILL.md, references, commands, specs).
This skill should be used when the user runs "/prx", "/prx <pr-url>", or "/prx post" — to collect the user's review comments against a diff and post them as an inline GitHub PR review. Trigger on "collect my PR comments", "start collecting comments", "post my comments to the PR", "send the review comments".
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Manage spec writing, implementation, and bug fixing.
| name | inline-review-todos |
| description | Place PR/code-review comments as inline TODO markers in the file each comment is on, at its line, not in a centralized list. Use when asked to "write TODOs for PR comments", capture review feedback as TODOs, or turn review threads into actionable in-file notes. |
| user-invocable | false |
Write each review comment as an inline marker in the file it is on, at the commented line.
TODO[PR]: <comment text> (@author). As an HTML comment (<!-- TODO[PR]: … -->) when the marker must not show in rendered output.A marker in a generated file (a render, compiled doc, codegen output) is wiped on regeneration.