release

Ships JobScan plugin versions through version bumps, preflight gates, changelogs, PRs, and release notes.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/MarioLuppino/JobScanPlugin --skill release-marioluppino
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/MarioLuppino/JobScanPlugin/tree/main/.claude/skills/release
Command: npx skills add https://github.com/MarioLuppino/JobScanPlugin --skill release-marioluppino

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Releasing a new version of the JobScan plugin involves many error-prone manual steps — bumping the version string, running validation gates, writing the changelog, opening a pull request, and drafting release notes — and skipping any one of them means users never receive the update. This Skill walks through the entire release workflow in the repository's established house style so nothing is missed or done inconsistently. ## Core Features & Use Cases - Release gating: Runs a preflight script that validates plugin and marketplace manifests, checks the 44-question documentation invariant, runs triage unit tests, and confirms the version in plugin.json matches a CHANGELOG section. - Version and changelog management: Bumps the single version string in plugin.json following semantic versioning rules and writes a Keep a Changelog entry covering only user-facing plugin changes. - PR and release notes drafting: Opens a pull request via the GitHub MCP tools and produces release notes in the documented house style, with a public body and a private supporting-information block separated by a cut line. - Use Case: After merging fixes to the JobScan plugin, ask to ship version 0.5.0 — the Skill verifies there is something worth releasing, runs all gates, writes the changelog entry, opens the PR, and hands over the tag name, release notes file, and pre-filled release URL for the two browser-only steps. ## Quick Start Ask the assistant to ship version 0.5.0 of the JobScan plugin and open a pull request for it.

Frequently Asked Questions about release

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

FAQPage Schema
How do I release a new version of the JobScan plugin?▼

Run the release skill with a target version like 0.5.0. It verifies there are shippable plugin changes, bumps the version in plugin.json, runs the preflight gates, writes the CHANGELOG entry, commits, pushes, and opens a pull request.

How do I open a pull request for the JobScanPlugin repository?▼

Ask for a PR and the skill runs Steps 0 through 5 only: it validates the changes, commits, pushes the branch, and calls the GitHub MCP create_pull_request tool against MarioLuppino/JobScanPlugin with base main.

Why can't the release tag be created from the session?▼

The session git proxy refuses tag pushes and ref deletions with HTTP 403, and the GitHub MCP server exposes read-only release tools. Tag creation and publishing the release page must be done in the browser.

What checks run before a JobScan release is pushed?▼

The preflight.sh script runs both plugin validators, the 44-question documentation invariant, triage unit tests, syntax checks on all pipeline scripts, load checks on paths.mjs and doctor.mjs, and a version-to-changelog consistency check.

Do changes under .claude/ get their own release?▼

No. The marketplace installs only ./plugins/jobscan, so maintainer tooling under .claude/ reaches no user. If nothing under plugins/ changed, there is no version to cut and the skill stops.