skills.rest
app-vitals
app-vitalsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

marketplace-dev

Enforce semantic-release versioning and schema-consistent structure for Shipwright plugin updates.

9|2|Updated Jun 6, 2026
Search Tags:#versioning#hooks#plugin#marketplace#frontmatter#semantic-release#shipwright
One-click install
npx skills add https://github.com/app-vitals/shipwright --skill marketplace-dev-app-vitals
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: marketplace-dev
Source: https://github.com/app-vitals/shipwright/tree/main/.claude/skills/marketplace-dev
Command: npx skills add https://github.com/app-vitals/shipwright --skill marketplace-dev-app-vitals

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It keeps Shipwright plugin changes consistent, release-safe, and aligned with the repository's automated versioning rules. Use it when updating plugin behavior, documentation, or marketplace metadata so changes do not drift across files.

Core Features & Use Cases

  • Enforces semantic-release ownership of version numbers and prevents manual bumps.
  • Guides edits to commands, skills, agents, hooks, and plugin metadata with the correct repository conventions.
  • Helps you sync descriptions, follow frontmatter schemas, and update TESTING.md when plugin behavior changes.
  • Useful for version bumps, new commands, hook additions, README edits, and pull request reviews touching the shipwright plugin.

Quick Start

Use the marketplace-dev skill when you are preparing any Shipwright plugin change, then verify versioning, structure, and documentation against the repo conventions before you edit files.

Frequently Asked Questions about marketplace-dev

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

FAQPage Schema
How do I prevent version drift when updating Shipwright plugin commands and hooks?▼

Preventing version drift in Shipwright plugins requires semantic-release ownership of version numbers, conventional commits, and synchronized descriptions across all release-sensitive files including plugin.json and marketplace metadata.

Do I need semantic-release to manage version bumps for Shipwright plugin updates?▼

Yes, semantic-release must own version numbers for Shipwright plugin updates to prevent manual bumps and ensure release-safe changes across commands, skills, agents, hooks, and plugin metadata.

What files require synchronized descriptions when modifying Shipwright plugin behavior?▼

Synchronized descriptions are required across plugin.json, marketplace metadata, README content, TESTING.md, and frontmatter schemas when modifying Shipwright plugin behavior to maintain release-safe consistency.

Can I manually bump the version number in plugin.json for a Shipwright plugin pull request?▼

No, manual version bumps in plugin.json are prevented for Shipwright plugin pull requests because semantic-release owns versioning to enforce conventional commits and structural consistency across release-sensitive files.

What is the best way to keep frontmatter schema consistent across Shipwright plugin skills and agents?▼

Keeping frontmatter schema consistent across Shipwright plugin skills and agents requires applying repository conventions that enforce schema-consistent frontmatter and synchronized descriptions during plugin updates.

When should I update TESTING.md while making Shipwright plugin changes?▼

You should update TESTING.md whenever Shipwright plugin behavior changes, ensuring documentation stays synchronized with commands, hooks, and skills while maintaining release-safe versioning and conventional commit standards.

Related Skills

Explore More Software Engineering Skills→
mcj-codermcj-coder
1

branching-strategy-and-conventions

Configure Git branching strategies, Conventional Commits, and merge rules.

Community
Advanced
try-workstry-works
95

conventions-check

Validate pull request titles, descriptions, and scope against repository conventions.

Community
Basic
LiorCohenLiorCohen
39

docs-standards

Maintain SDD plugin documentation with frontmatter-driven metadata and markdown structure.

Community
Intermediate
drgaciwdrgaciw

changelog-automation

Generate changelogs and release notes from Conventional Commits in CI/CD pipelines.

Community
Intermediate