publish-artifactlisted

# Publish Artifact Publish an rp1 artifact (markdown under `.rp1/work/`; frontmatter optional) as a PR or issue comment without committing the artifact file to the repo. Re-running updates the same comment in place. **The artifact file is never modified by this skill** — it is read-only on the local side, write-only on the GitHub side. > ### ⚠️ Always dry-run first on a real PR or issue > > The skill writes to a real GitHub PR/issue comment by default. Before publishing to a PR/issue you care about (especially one with active reviewers), run with `"dry_run": true` first. A dry-run still resolves the target, validates, and runs the safety gates — it only skips the GitHub write — then returns the projected `data.comment_body` plus the `data.action` (`post` or `patch`) the real run would take. Once the projection looks right, re-run without `dry_run` to post. ## When to invoke - User explicitly runs `/rp1-dev:publish-artifact <path> [target]`. - User has just produced an rp1 artifact and asks how to share it on a PR or issue without committing it. - User asks to "summarize an rp1 investigation report into a PR or issue comment." ## When NOT to invoke - The file is not an rp1 work artifact at all (not under `.rp1/work/` and unrelated to rp1). This skill publishes rp1 artifacts; frontmatter is optional, but the file should be an rp1 work product. - The user wants to keep the artifact in the repo. This skill is for the *don't commit it* case. ## Gather the inputs | Field |