sharing-pr-agent-artifacts

Uploads agent-generated specs and plans to the streamlit.wiki for PR sharing.

45.7k|4.4k|Updated Aug 24, 2019
One-click install
npx skills add https://github.com/streamlit/streamlit --skill sharing-pr-agent-artifacts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharing-pr-agent-artifacts
Source: https://github.com/streamlit/streamlit/tree/main/.claude/skills/sharing-pr-agent-artifacts
Command: npx skills add https://github.com/streamlit/streamlit --skill sharing-pr-agent-artifacts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agent-generated artifacts like implementation plans, specs, and design explorations are useful for PR reviewers but don't belong in the main repository. This Skill publishes them to the public streamlit.wiki repository and links them in PR comments so reviewers can access the context behind a change.

Core Features & Use Cases

  • Artifact Publishing: Copies specs, plans, diagrams, and research notes into a per-PR directory in the streamlit.wiki repo and pushes to the master branch.
  • Safety Filtering: Excludes credentials, secrets, build artifacts, large binaries, and files already tracked in the main repo before uploading to the public wiki.
  • PR Comment Integration: Posts a summary comment on the pull request with public links to each uploaded document via the agent_wiki_explorer URL pattern.
  • Use Case: After an agent drafts an implementation plan for PR #12345, run this Skill to upload the plan to the wiki and automatically comment on the PR with a shareable link for reviewers.

Quick Start

Upload the implementation plan and exploration notes for the current PR to the streamlit wiki and post the links as a PR comment.

Frequently Asked Questions about sharing-pr-agent-artifacts

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

FAQPage Schema
How do I share agent-generated implementation plans on a GitHub pull request?

Upload the plan files to the streamlit.wiki repository under pull-requests/<pr-number>, push to master, then post a PR comment with links using the agent_wiki_explorer URL pattern. This keeps artifacts out of the main repo while remaining accessible to reviewers.

What files should I upload to the streamlit wiki for a PR?

Upload specs, implementation plans, design docs, architecture diagrams, and research notes relevant to the PR. Exclude files already tracked in the main repo, credentials, secrets, test artifacts, debug logs, build outputs, and binaries over 10MB.

Can I push agent artifacts to a branch other than master on the wiki repo?

No, the streamlit.wiki repository uses master as its default branch and all pushes must go there. Never create feature branches or use force push; resolve conflicts with git pull --rebase instead.

What happens if the wiki push fails due to conflicts?

Run git pull --rebase origin master, resolve any conflicts manually, continue the rebase, and push again. The workflow explicitly forbids using --force to avoid overwriting others' contributions.

Is it safe to upload agent artifacts to the streamlit wiki?

The wiki is a public repository, so only non-sensitive technical and product planning documents should be uploaded. The Skill filters out credentials, tokens, API keys, and confidential information before publishing.