publish

Publish collie-harness plugin releases with validation, testing, changelog, and git tagging.

3|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/lkv1988/collie-harness --skill publish-lkv1988
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/lkv1988/collie-harness/tree/main/.claude/skills/publish
Command: npx skills add https://github.com/lkv1988/collie-harness --skill publish-lkv1988

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually preparing a release for collie-harness involves multiple validation steps, testing, changelog updates, and git tagging, which is error‑prone and time‑consuming.

Core Features & Use Cases

  • Automated Checklist: Runs plugin validation, unit tests, reference scans, and entry‑point audits in parallel.
  • Version Management: Reads the current version, bumps it if needed, and updates marketplace metadata.
  • Changelog Generation: Creates a structured changelog entry from recent commits.
  • Git Tagging & Publishing: Tags the new version and pushes both the commit and tag to the repository. Use it when you need to release a new version of collie-harness quickly and reliably.

Quick Start

Ask the publish skill to release the latest version of collie‑harness.

Frequently Asked Questions about publish

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

FAQPage Schema
How do I automate git tagging and changelog generation for plugin releases?

Automating git tagging and changelog generation for plugin releases is done by running validation, bumping versions, creating structured changelogs from recent commits, and pushing git tags automatically.

What steps are needed to publish a new plugin version with validation and testing?

To publish a new plugin version, the process runs plugin validation, unit tests, reference scans, and entry-point audits in parallel, then updates marketplace metadata and pushes the release.

Does automated release validation work with git workflows for continuous integration?

Automated release validation works with git workflows by executing parallel checks, generating changelog entries from recent commits, and pushing both the commit and the version tag to the repository.

What's the best way to manage version bumping and marketplace metadata updates?

Managing version bumping and marketplace metadata updates is handled automatically by reading the current version, incrementing it if needed, and updating the metadata before tagging and pushing the release.

Can I run unit tests and entry-point audits in parallel before pushing a git tag?

Yes, you can run unit tests and entry-point audits in parallel before pushing a git tag, as the release process executes an automated checklist of validation steps simultaneously to ensure reliability.