release-skills
Release Baoyu Skills Safely
Manual releases can miss changelog, version, and tag steps. This skill guides a repeatable release workflow for baoyu-skills with bilingual changelogs and local git tagging.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "release-skills" from https://skillstore.io/skills/jimliu-release-skills.md and its manifest at https://skillstore.io/api/skills/jimliu-release-skills/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "release-skills". User asks for a dry run before release.
Expected outcome:
The assistant reports the last tag, proposed version, changelog preview, README impact, and files that would change. No files are modified.
Using "release-skills". User asks to create a patch release.
Expected outcome:
The assistant updates release notes and metadata, creates one local release commit, creates the version tag, and reminds the user to publish manually.
Using "release-skills". User asks for a major release after removing a skill.
Expected outcome:
The assistant highlights the breaking change, asks for confirmation, updates migration notes when needed, and prepares the local major release.
Security Audit
SafeThe static findings are false positives caused by Markdown inline code, fenced examples, and fixed git release commands. No evidence found of prompt injection, credential access, network exfiltration, or arbitrary command construction.
Risk Factors
⚙️ External commands (45)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/jimliu-release-skills/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/jimliu-release-skills?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/jimliu-release-skills?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/jimliu-release-skills/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/jimliu-release-skills.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
jimliu. (2026). release-skills security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/jimliu-release-skills/audits/6BibTeX citation
@techreport{jimliu-jimliu-release-skills-2026,
author = {jimliu},
title = {release-skills security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/jimliu-release-skills/audits/6},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "release-skills security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
- name: "jimliu"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/jimliu-release-skills/audits/6"
identifiers:
- type: other
value: "skillstore:jimliu-release-skills:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prepare a Local Release
A maintainer can update release files, create a commit, and tag the version before manual publishing.
Maintain Bilingual Changelogs
A documentation owner can keep English and Chinese changelog entries aligned for each release.
Preview Release Impact
A developer can run dry-run mode to review version, changelog, README, and file changes first.
Try These Prompts
Use release-skills with --dry-run and show the proposed version, changelog entries, and files that would change.
Run the release-skills workflow for a patch release. Update changelogs, bump marketplace metadata, commit the release, and create the tag.
Use release-skills --minor after reviewing changes since the last tag. Update README files if the new skill changes usage.
Use release-skills --major. Identify breaking changes, update migration notes if needed, sync English and Chinese docs, and create the local tag.
Best Practices
- Run dry-run mode before creating a real release.
- Review generated English and Chinese changelog entries before committing.
- Push commits and tags manually after verifying the local release.
Avoid
- Using the workflow outside the baoyu-skills repository.
- Skipping README review when new skills or usage changes are included.
- Treating the post-release push reminder as automatic publishing.