skills.rest
shawn-sandy
shawn-sandyCOMMUNITY
Explore all skills by this author →
Website𝕏@shawnsandyGitHub

release-check

Audit plugin release paperwork before opening a marketplace PR.

Updated Apr 21, 2026
Search Tags:#pull request#claude code#release#quality gate#plugin marketplace#paperwork audit
One-click install
npx skills add https://github.com/shawn-sandy/agentic-acss-plugins --skill release-check-shawn-sandy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-check
Source: https://github.com/shawn-sandy/agentic-acss-plugins/tree/main/.agents/skills/release-check
Command: npx skills add https://github.com/shawn-sandy/agentic-acss-plugins --skill release-check-shawn-sandy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you catch missing or inconsistent release paperwork before you open a PR, reducing back-and-forth with reviewers.

Core Features & Use Cases

  • Release paperwork audit: checks a plugin’s release materials against the expectations for the marketplace workflow.
  • Pre-PR quality gate: supports a smoother merge by validating release details early.
  • Usage in release flows: intended to be superseded by the newer release-plugin <plugin-name> --check command.

Quick Start

Run /release-plugin <plugin-name> --check to audit the release paperwork for that plugin before opening a PR.

Frequently Asked Questions about release-check

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

FAQPage Schema
How do I audit plugin release paperwork before opening a pull request?▼

To validate release paperwork before a pull request, run the pre-PR audit check with your plugin name. This quality gate reviews the plugin's release materials against marketplace workflow expectations to catch missing or inconsistent submission details early.

What is a pre-PR quality gate for a Claude Code plugin marketplace?▼

A pre-PR quality gate for a Claude Code plugin marketplace is a validation step that audits release paperwork prior to merging. It checks a plugin's release materials against marketplace expectations to prevent incomplete or inconsistent release submissions.

Do I need a plugin name to run a release paperwork audit?▼

Yes, you need to specify a plugin name as an argument to run the release paperwork audit. The validation workflow requires this argument to check the specific plugin's release checklist and materials against marketplace standards.

Does the release-plugin check command supersede this paperwork audit workflow?▼

Yes, the release-plugin check command is intended to supersede this paperwork audit workflow. The merged-superseded check workflow aligns with this newer command, which serves as the primary method for auditing release details before opening a PR.

Why does my Claude Code plugin PR get rejected for incomplete release paperwork?▼

Your plugin PR may get rejected for incomplete release paperwork because the submission materials do not align with marketplace workflow expectations. Running a pre-PR audit helps catch these missing or inconsistent release details before submitting your pull request.

Related Skills

Explore More Product & Management Skills→
GoBeromsuGoBeromsu
2

obsidian-publish

Submit Obsidian plugins to the community releases process with automated PRs.

Community
Advanced
xashggxashgg
1

commit

Automate the commit, pull request, and merge cycle with quality gate checks.

Community
Intermediate
adityaarsharmaadityaarsharma
2

orbit-plugin-check

Execute the official WordPress.org plugin-check tool and interpret severity levels.

Community
Intermediate
rmarino550rmarino550

ship

Automate software releases with branch detection, merging, testing, and pull request creation.

Community
Advanced