persist-rp1-artifact
A Claude Code skill that publishes rp1 artifacts — investigation reports, design docs, audits, security analyses — as idempotent GitHub PR comments, so reviewers see the reasoning behind a change without the intermediate analysis files cluttering the repo.
The problem this solves
rp1 agents (bug-investigator, feature-architect, code-auditor, etc.) produce long-form markdown artifacts under .rp1/work/. These artifacts are valuable during review — they capture the "why" behind a PR — but their value decays after merge: the code becomes the source of truth, and the intermediate report rots.
Two bad alternatives the team had been living with:
- Commit the artifact to the repo. Bloats
git log and file tree with analysis that has no long-term home. (Real example — a 397-line investigation report was force-added to a 3-line PR.)
- Discard the artifact. Reviewers lose the reasoning; future maintainers can't reconstruct the "why."
persist-rp1-artifact is the third option: publish the artifact as a PR comment that lives where reviewers actually look, while the original file stays gitignored under .rp1/work/. Re-running the skill on an edited artifact updates the same comment in place (no spam, GitHub's "edited" badge surfaces the change).
What it looks like
The skill projects an rp1 artifact into a structured PR comment:
- A header table with frontmatter fields (producer, artifact type, doc ID, source path)
- The artifact's Executive Summary section, verbatim, at the top
- The rest of the artifact tucked inside a
<details> collapsible block (shown expanded in the screenshot; collapsed by default in real comments)
- A hidden HTML marker (
<!-- rp1-artifact: <uuid> -->) on line 1 for idempotent re-runs
The screenshot above is generated from a fully synthetic artifact about a fictional Redis-to-Postgres migration — no real-world content, just the structural format you can expect.
Is this the right tool?
This skill is purpose-built for rp1 artifacts — markdown files under .rp1/work/ with rp1's frontmatter format (producer, artifact, rp1_doc_id, etc.). If your situation is different, there are simpler options:
- Posting CI output (test reports, coverage, lint findings) as a sticky PR comment from a workflow? Use
marocchino/sticky-pull-request-comment, mshick/add-pr-comment, or one of the other GitHub Actions in that family. They run in CI, are well-maintained, and don't require rp1.
- Posting a generic markdown file from your laptop? A one-liner does it:
gh api -X POST repos/<owner>/<repo>/issues/<pr>/comments -F body=@file.md. No skill needed.
- Posting inline review findings (per-line code suggestions on a PR)? Use rp1's
/pr-review — it already composes with the pr-comment-poster and pr-comment-deduplicator agents for that workflow.
This skill earns its keep specifically when (a) you're using rp1, (b) an rp1 agent has produced an artifact with valid frontmatter, and (c) you want the artifact to live in the PR conversation instead of the repo.
Prerequisites
gh CLI installed and authenticated (gh auth status must succeed)- Python 3 on
PATH (any 3.x; stdlib only, no PyYAML required)
- An rp1 artifact under
.rp1/work/ with valid frontmatter (must include rp1_doc_id)
Installation
As a Claude Code plugin (recommended)
Claude Code installs plugins from marketplaces — repos containing a .claude-plugin/marketplace.json manifest. This repo is its own single-plugin marketplace, so installation is a two-step command:
/plugin marketplace add edruder/persist-rp1-artifact
/plugin install persist-rp1-artifact
The first command registers the repo as a known marketplace, keyed under the manifest's name (persist-rp1-artifact). The second installs the plugin from it. After installing, the /persist-rp1-artifact slash-command becomes available (may require a session restart).
Note on naming. Only the add command takes the GitHub path; subsequent /plugin marketplace operations (update, remove, etc.) take the marketplace name — persist-rp1-artifact, not edruder/persist-rp1-artifact. See the Updating section below.
Updating
When a new plugin version ships, refresh the cached marketplace and reinstall:
/plugin marketplace update persist-rp1-artifact
/plugin install persist-rp1-artifact
update pulls the latest main of this repo into Claude Code's marketplace cache. install then re-registers the plugin from the refreshed manifest. Without the update step, Claude Code reads its stale local cache and won't see new versions.
