skills.rest
edruder
edruderCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

persist-rp1-artifact

Publish rp1 markdown artifacts as idempotent GitHub PR comments.

Updated May 20, 2026
Search Tags:#pull request#github#yaml frontmatter#artifact publishing#rp1#idempotent comments#review workflows
One-click install
npx skills add https://github.com/edruder/persist-rp1-artifact --skill persist-rp1-artifact
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: persist-rp1-artifact
Source: https://github.com/edruder/persist-rp1-artifact/tree/main/skills/persist-rp1-artifact
Command: npx skills add https://github.com/edruder/persist-rp1-artifact --skill persist-rp1-artifact

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Persist-rp1-artifact takes long-form rp1 markdown artifacts generated under .rp1/work/ and publishes them as idempotent GitHub PR comments, so reviewers can see the reasoning without cluttering the repository.

Core Features & Use Cases

  • Idempotent PR comment updates: Uses an HTML marker containing rp1_doc_id to update the same comment on re-runs instead of spamming new ones.
  • Deterministic projection format: Renders a structured header table plus the artifact’s Executive Summary verbatim, with the remainder of the artifact inside a collapsible details block.
  • Safety-first workflow: Supports --dry-run for preview and guardrails like refusing to publish when rp1_doc_id is missing.
  • Practical for review workflows: Use it right after rp1 agents (bug-investigator, feature-architect, code-auditor, etc.) produce artifacts you want reviewers to read in-context on the PR.

Quick Start

Run /persist-rp1-artifact path/to/.rp1/work/<your_artifact>.md --dry-run first, then re-run without --dry-run to post or update the PR comment.

Frequently Asked Questions about persist-rp1-artifact

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish markdown artifacts as idempotent GitHub PR comments?▼

To publish markdown artifacts as idempotent GitHub PR comments, parse the YAML frontmatter for rp1_doc_id and use an HTML marker to update existing comments on re-runs instead of creating duplicates, keeping the repository clean.

What is the best way to share rp1 review workflows without committing analysis files?▼

The best way to share rp1 review workflows without committing files is to publish artifacts as structured GitHub PR comments featuring an Executive Summary and a collapsible details block for the full report.

How do I project YAML frontmatter into a GitHub PR comment template?▼

Project YAML frontmatter into a GitHub PR comment by parsing rp1_doc_id, producer, and artifact fields, then deterministically rendering a structured header table and the artifact content into the comment template format.

Can I preview a PR comment before posting using a dry run?▼

Yes, you can preview a PR comment before posting by running the command with the --dry-run flag to verify the projected output format and check for missing rp1_doc_id markers safely.

Does posting PR comments require the gh command line tool?▼

Yes, posting PR comments requires the gh command line tool to resolve the target pull request and execute the POST or PATCH operations needed to publish or update the comment.

What happens when duplicate rp1_doc_id markers are found on a pull request?▼

When duplicate rp1_doc_id markers are found on a pull request, the workflow safely handles the edge case during the POST or PATCH operation to prevent unintended comment spam or data corruption.

Related Skills

Explore More Software Engineering Skills→
MiniMax-AIMiniMax-AI
2.9k

skill-creator

Generate Skill Units with YAML frontmatter, Markdown body, and bundled resources.

Official
Intermediate
Gorillaa-ai-orgGorillaa-ai-org

pr-description

Generate GitHub PR descriptions with Summary and Fixes sections from commits and diffs.

Official
Intermediate
sequenziasequenzia
2

bug-killer

Automate hypothesis-driven debugging with triage-based routing and agent coordination.

Community
Advanced
yusaduymazyusaduymaz

gsd-pr-branch

Filter planning-only commits from a pull-request branch.

Community
Advanced